Telegram Slack MCP

Telegram Slack MCP runs locally from a Node.js package published to the npm registry: telegram-slack-mcp version 0.5.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y telegram-slack-mcp@0.5.1. It reads these environment variables: TELEGRAM_API_ID, TELEGRAM_API_HASH (secret), TELEGRAM_ALLOW_SEND, SLACK_USER_TOKENS (secret), SLACK_ALLOW_SEND and CHAT_MCP_DATA_DIR; set them in the client's configuration for this server. Required arguments: server.

Telegram Slack MCP runs locally from a Python package published to PyPI: telegram-slack-mcp version 0.2.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx telegram-slack-mcp.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "telegram-slack-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "telegram-slack-mcp@0.5.1"
      ],
      "env": {
        "TELEGRAM_API_ID": "<value>",
        "TELEGRAM_API_HASH": "<secret>",
        "TELEGRAM_ALLOW_SEND": "<value>",
        "SLACK_USER_TOKENS": "<secret>",
        "SLACK_ALLOW_SEND": "<value>",
        "CHAT_MCP_DATA_DIR": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect