topmcps
Browse MCPs
Telegram

Telegram

Send messages and read channel history from a Telegram bot in an agent.

Score 79(?)CommunityMIT1.1kVerified Top MCPs for Communication →
InstallView on GitHub

Quick answer

What it does

Connects to a Telegram bot identity and exposes send-message, get-updates, and chat-info tools to AI models.

Best for

  • Notification channels
  • Lightweight chatbots
  • Read-only group summarisation
  • Cross-platform alerts

Not for

  • Impersonating a real user account
  • High-volume marketing (use a marketing-specific platform)

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

    claude_desktop_config.json
    {
  "mcpServers": {
    "telegram": {
      "command": "npx",
      "args": [
        "-y",
        "telegram-mcp"
      ],
      "env": {
        "TELEGRAM_BOT_TOKEN": "${TELEGRAM_BOT_TOKEN}"
      }
    }
  }
}

    Paste under mcpServers. Fully quit and reopen Claude after editing.

    CLI or .mcp.json
    # export TELEGRAM_BOT_TOKEN=123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11
claude mcp add telegram -- npx -y telegram-mcp

    Run from your repo. Commit .mcp.json to share with your team.

    .cursor/mcp.json
    {
  "mcpServers": {
    "telegram": {
      "command": "npx",
      "args": [
        "-y",
        "telegram-mcp"
      ],
      "env": {
        "TELEGRAM_BOT_TOKEN": "${TELEGRAM_BOT_TOKEN}"
      }
    }
  }
}

    Global path: ~/.cursor/mcp.json. Reload window after editing.

    .vscode/mcp.json
    {
  "servers": {
    "telegram": {
      "command": "npx",
      "args": [
        "-y",
        "telegram-mcp"
      ],
      "env": {
        "TELEGRAM_BOT_TOKEN": "${TELEGRAM_BOT_TOKEN}"
      }
    }
  }
}

    VS Code uses the "servers" key (not "mcpServers").

    ~/.codeium/windsurf/mcp_config.json
    {
  "mcpServers": {
    "telegram": {
      "command": "npx",
      "args": [
        "-y",
        "telegram-mcp"
      ],
      "env": {
        "TELEGRAM_BOT_TOKEN": "${TELEGRAM_BOT_TOKEN}"
      }
    }
  }
}

    Open via Cascade → hammer icon → Configure.

    cline_mcp_settings.json
    {
  "mcpServers": {
    "telegram": {
      "command": "npx",
      "args": [
        "-y",
        "telegram-mcp"
      ],
      "env": {
        "TELEGRAM_BOT_TOKEN": "${TELEGRAM_BOT_TOKEN}"
      }
    }
  }
}

    Open via the Cline sidebar → MCP Servers → Edit.

    ~/.continue/config.json
    {
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "telegram-mcp"
          ],
          "env": {
            "TELEGRAM_BOT_TOKEN": "${TELEGRAM_BOT_TOKEN}"
          }
        }
      }
    ]
  }
}

    Continue uses modelContextProtocolServers with a transport block.

    ~/.codex/config.toml
    # ~/.codex/config.toml
[mcp_servers.telegram]
command = "npx"
args = [
  "-y",
  "telegram-mcp",
]
env = { TELEGRAM_BOT_TOKEN = "${TELEGRAM_BOT_TOKEN}" }

    Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

    ~/.config/zed/settings.json
    {
  "context_servers": {
    "telegram": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "telegram-mcp"
        ]
      },
      "env": {
        "TELEGRAM_BOT_TOKEN": "${TELEGRAM_BOT_TOKEN}"
      }
    }
  }
}

    Zed calls them "context_servers". Settings live-reload on save.

    ChatGPT → Apps directory

    Telegram doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

  2. 2

    Set required secrets

    Set TELEGRAM_BOT_TOKEN in your shell environment before launching your MCP client.

  3. 3

    Try a minimum working prompt

    Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Security & scope

Access scope
Network
Sandbox
Telegram bot token in env. Token grants the full bot identity; rotate via @BotFather if it leaks. The bot can only post in chats it has been added to.
Gotchas
  • Bot tokens, if leaked, give full bot identity — anyone can post as the bot. Treat like any API key.
  • Telegram rate-limits messages per chat (30/sec) and per bot (no fixed number but enforced).
  • Channel posts cannot be deleted past the configured retention window.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. communication work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-communication
Compare Telegram against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Telegram MCP vs [Slack MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/telegram
- top-mcps.com listing for Slack
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Telegram MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/telegram (fetch https://top-mcps.com/mcp/telegram.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (TELEGRAM_BOT_TOKEN) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

  1. Refreshed install snippets and fact sheet; verified for 2026.

  2. Initial directory listing.

More Communication MCPs

Other tools in the same category worth evaluating.

Slack logo — MCP server

Read and send Slack messages, manage channels and threads.

slack, messaging, communication, automation
10 minMedium
Discord

Read and post to Discord channels — community management for AI agents.

discord, chat, community, bot
10 minMedium
Microsoft Teams
Official

Read channel messages, post replies, and trigger meetings from MS Teams.

communication, microsoft, teams, m365
20 minMedium

Compared with Telegram

Side-by-side breakdowns for the choices people most often weigh against this MCP.

TelegramvsSlackTelegramvsDiscordTelegramvsMattermostTelegramvsTwilio

Exploring Top MCPs for Communication? See all Communication MCPs →