← Back to directory
T

Telegram API MCP Server

Community
Ultimate Telegram Bot API MCP server — full v9.6 coverage, meta-mode, rate limiting, circuit breaker.
GitHub source repository ↗
★ 28 Stars Category · Other Popular Source revision 5220b1ee91dc
51FMRS · D

This server offers a comprehensive, type-safe wrapper over the Telegram Bot API with useful engineering for AI use, but it is community-maintained and may lag behind the latest API versions.

Reliability
8/20
Security and permissions
11/20
Maintenance
8/20
Documentation
11/20
Setup experience
13/20
Read the FMRS scoring method →

telegram-api-mcp is a TypeScript-only MCP server that provides all 169 methods of the Telegram Bot API (Bot API v9.6; v10.2 per the manifest). It includes Zod parameter validation, token masking, tool annotations, response truncation, and resilience features like async-mutex token-bucket rate limiting (defaults: 30 requests/sec global and 20 messages/min per group, aligning with Telegram's official limits) and a 3-state circuit breaker (closed/open/half-open). It supports a meta-mode (TELEGRAM_META_MODE=true) that replaces the 169 individual tools with just two tools, telegram_find and telegram_call, to save ~99% of context tokens. It has only two runtime dependencies (@modelcontextprotocol/sdk and zod). The server communicates with clients via stdio. It is compatible with clients such as Claude Desktop, as per the README installation instructions, running through npx.

Tools

telegram_find
Search available Telegram methods by keyword or category.
telegram_call
Call any Telegram Bot API method by name with JSON params.
sendMessage
sendPhoto
sendVideo
sendAudio
sendDocument
sendMediaGroup
sendPoll
sendDice
sendChatAction
forwardMessage
copyMessage
editMessageText
deleteMessage
getMe
getChat
banChatMember
unbanChatMember
restrictChatMember
promoteChatMember
getFile
getUpdates
setWebhook
answerCallbackQuery
sendInvoice
createChatInviteLink
setChatTitle
sendLocation
sendContact

Setup

  1. Obtain a bot token from @BotFather. 2. In an MCP-capable client (e.g., Claude Desktop), add an MCP server with the configuration: command: 'npx', args: ['telegram-api-mcp'], env: { TELEGRAM_BOT_TOKEN: 'your_token' }. 3. Alternatively, set the environment variable in your shell and run npx telegram-api-mcp locally with an MCP client that supports stdio.
claude_desktop_config.json
{
  "mcpServers": {
    "telegram": {
      "command": "npx",
      "args": [
        "telegram-api-mcp"
      ],
      "env": {
        "TELEGRAM_BOT_TOKEN": "your_token_from_botfather"
      }
    }
  }
}

Fit and risk

Best for

  • LLM-driven Telegram bot development where natural-language prompts trigger Bot API calls.
  • Integrations requiring a comprehensive, validated set of Telegram Bot API methods.
  • Longer AI conversations where meta-mode reduces context token consumption.
  • Projects needing built-in rate limiting and fault tolerance in Bot API calls.

Not for

  • Users not working with Telegram or without Telegram bot needs.
  • Users needing SSE or HTTP transport, as this server supports only stdio.
  • Those wanting an officially maintained MCP server; this is a community implementation.
  • Edge-case use cases that require no external dependencies and full official support.

Required permissions

  • Full access to the Telegram Bot API tied to the provided token.
  • Ability to send and receive messages, files, and media in chats, groups, and channels where the bot is a member.
  • The server communicates only with `api.telegram.org`; no other external network calls are made.
  • The token is masked and never exposed in responses or error messages.

Risks and side effects

  • Token leakage could lead to misuse of the bot account.
  • Potential security risks if file uploads are exposed in untrusted environments.
  • Rate limiting and circuit breaker behaviors may interact unusually under load.
  • The server's code and content may contain bugs, with no official support.

Troubleshooting

  1. Check that `TELEGRAM_BOT_TOKEN` is correctly set in the environment.
  2. Verify that your Telegram bot token is valid and the bot is initialized.
  3. Ensure your client uses the latest version of `telegram-api-mcp` via npx.
  4. For message-sending errors, check rate-limit configurations and chat ID correctness.

Use cases

Send Telegram messages, audio, photos, videos, documents, and media groups from within an MCP client.
Manage chats, groups, forum topics, and member permissions directly.
Implement Telegram bot operations without manual REST calls in the client.
Create polls, quizzes, invoices, and gifts in Telegram.

Supported clients

Claude DesktopFull support