NotifyHub - Unified Notification MCP Server

NotifyHub - Unified Notification MCP Server viene eseguito in locale a partire da un’immagine container in un registro OCI come Docker Hub o GitHub Container Registry: ghcr.io/gabrielbbaldez/notify-hub:1.1.0. Comunica via MCP su stdio, quindi il client lo avvia come programma e dialoga con esso tramite standard input e standard output. Richiede Docker o un altro runtime di container OCI; si avvia con docker run - il comando abituale è docker run -i --rm -e NOTIFY_CHANNELS_EMAIL_HOST -e NOTIFY_CHANNELS_EMAIL_PORT -e NOTIFY_CHANNELS_EMAIL_USERNAME -e NOTIFY_CHANNELS_EMAIL_PASSWORD -e NOTIFY_CHANNELS_EMAIL_FROM -e NOTIFY_CHANNELS_SMS_ACCOUNTSID -e NOTIFY_CHANNELS_SMS_AUTHTOKEN -e NOTIFY_CHANNELS_SMS_FROMNUMBER -e NOTIFY_CHANNELS_SLACK_WEBHOOKURL -e NOTIFY_CHANNELS_TELEGRAM_BOTTOKEN -e NOTIFY_CHANNELS_TELEGRAM_CHATID -e NOTIFY_CHANNELS_DISCORD_WEBHOOKURL -e NOTIFY_CHANNELS_TEAMS_WEBHOOKURL -e NOTIFY_CHANNELS_GOOGLECHAT_WEBHOOKURL -e NOTIFY_CHANNELS_TWITTER_APIKEY -e NOTIFY_CHANNELS_TWITTER_APISECRET -e NOTIFY_CHANNELS_TWITTER_ACCESSTOKEN -e NOTIFY_CHANNELS_TWITTER_ACCESSTOKENSECRET -e NOTIFY_CHANNELS_LINKEDIN_ACCESSTOKEN -e NOTIFY_CHANNELS_LINKEDIN_ORGANIZATIONID ghcr.io/gabrielbbaldez/notify-hub:1.1.0. Legge queste variabili d’ambiente: NOTIFY_CHANNELS_EMAIL_HOST, NOTIFY_CHANNELS_EMAIL_PORT, NOTIFY_CHANNELS_EMAIL_USERNAME (segreto), NOTIFY_CHANNELS_EMAIL_PASSWORD (segreto), NOTIFY_CHANNELS_EMAIL_FROM, NOTIFY_CHANNELS_SMS_ACCOUNTSID (segreto), NOTIFY_CHANNELS_SMS_AUTHTOKEN (segreto), NOTIFY_CHANNELS_SMS_FROMNUMBER, NOTIFY_CHANNELS_SLACK_WEBHOOKURL (segreto), NOTIFY_CHANNELS_TELEGRAM_BOTTOKEN (segreto), NOTIFY_CHANNELS_TELEGRAM_CHATID, NOTIFY_CHANNELS_DISCORD_WEBHOOKURL (segreto), NOTIFY_CHANNELS_TEAMS_WEBHOOKURL (segreto), NOTIFY_CHANNELS_GOOGLECHAT_WEBHOOKURL (segreto), NOTIFY_CHANNELS_TWITTER_APIKEY (segreto), NOTIFY_CHANNELS_TWITTER_APISECRET (segreto), NOTIFY_CHANNELS_TWITTER_ACCESSTOKEN (segreto), NOTIFY_CHANNELS_TWITTER_ACCESSTOKENSECRET (segreto), NOTIFY_CHANNELS_LINKEDIN_ACCESSTOKEN (segreto) e NOTIFY_CHANNELS_LINKEDIN_ORGANIZATIONID; vanno impostate nella configurazione del client per questo server.

Nel formato JSON mcpServers, letto da molti client MCP desktop e per editor di codice, la voce si presenta così (segnaposto tra parentesi angolari):

{
  "mcpServers": {
    "notify-hub": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "NOTIFY_CHANNELS_EMAIL_HOST",
        "-e",
        "NOTIFY_CHANNELS_EMAIL_PORT",
        "-e",
        "NOTIFY_CHANNELS_EMAIL_USERNAME",
        "-e",
        "NOTIFY_CHANNELS_EMAIL_PASSWORD",
        "-e",
        "NOTIFY_CHANNELS_EMAIL_FROM",
        "-e",
        "NOTIFY_CHANNELS_SMS_ACCOUNTSID",
        "-e",
        "NOTIFY_CHANNELS_SMS_AUTHTOKEN",
        "-e",
        "NOTIFY_CHANNELS_SMS_FROMNUMBER",
        "-e",
        "NOTIFY_CHANNELS_SLACK_WEBHOOKURL",
        "-e",
        "NOTIFY_CHANNELS_TELEGRAM_BOTTOKEN",
        "-e",
        "NOTIFY_CHANNELS_TELEGRAM_CHATID",
        "-e",
        "NOTIFY_CHANNELS_DISCORD_WEBHOOKURL",
        "-e",
        "NOTIFY_CHANNELS_TEAMS_WEBHOOKURL",
        "-e",
        "NOTIFY_CHANNELS_GOOGLECHAT_WEBHOOKURL",
        "-e",
        "NOTIFY_CHANNELS_TWITTER_APIKEY",
        "-e",
        "NOTIFY_CHANNELS_TWITTER_APISECRET",
        "-e",
        "NOTIFY_CHANNELS_TWITTER_ACCESSTOKEN",
        "-e",
        "NOTIFY_CHANNELS_TWITTER_ACCESSTOKENSECRET",
        "-e",
        "NOTIFY_CHANNELS_LINKEDIN_ACCESSTOKEN",
        "-e",
        "NOTIFY_CHANNELS_LINKEDIN_ORGANIZATIONID",
        "ghcr.io/gabrielbbaldez/notify-hub:1.1.0"
      ],
      "env": {
        "NOTIFY_CHANNELS_EMAIL_HOST": "<valore>",
        "NOTIFY_CHANNELS_EMAIL_PORT": "<valore>",
        "NOTIFY_CHANNELS_EMAIL_USERNAME": "<segreto>",
        "NOTIFY_CHANNELS_EMAIL_PASSWORD": "<segreto>",
        "NOTIFY_CHANNELS_EMAIL_FROM": "<valore>",
        "NOTIFY_CHANNELS_SMS_ACCOUNTSID": "<segreto>",
        "NOTIFY_CHANNELS_SMS_AUTHTOKEN": "<segreto>",
        "NOTIFY_CHANNELS_SMS_FROMNUMBER": "<valore>",
        "NOTIFY_CHANNELS_SLACK_WEBHOOKURL": "<segreto>",
        "NOTIFY_CHANNELS_TELEGRAM_BOTTOKEN": "<segreto>",
        "NOTIFY_CHANNELS_TELEGRAM_CHATID": "<valore>",
        "NOTIFY_CHANNELS_DISCORD_WEBHOOKURL": "<segreto>",
        "NOTIFY_CHANNELS_TEAMS_WEBHOOKURL": "<segreto>",
        "NOTIFY_CHANNELS_GOOGLECHAT_WEBHOOKURL": "<segreto>",
        "NOTIFY_CHANNELS_TWITTER_APIKEY": "<segreto>",
        "NOTIFY_CHANNELS_TWITTER_APISECRET": "<segreto>",
        "NOTIFY_CHANNELS_TWITTER_ACCESSTOKEN": "<segreto>",
        "NOTIFY_CHANNELS_TWITTER_ACCESSTOKENSECRET": "<segreto>",
        "NOTIFY_CHANNELS_LINKEDIN_ACCESSTOKEN": "<segreto>",
        "NOTIFY_CHANNELS_LINKEDIN_ORGANIZATIONID": "<valore>"
      }
    }
  }
}

Ricavato dalla voce del registro, non testato qui. Cosa fa il server, e a quali condizioni, lo stabilisce il suo editore; prima di concedergli l’accesso ai propri account o file conviene consultarne il repository o il sito web. Come aggiungere un server MCP a un assistente · Prima di collegare un server