M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionTelegram API MCP ServerUltimate Telegram Bot API MCP server — full v9.6 coverage, meta-mode, rate limiting, circuit breaker.Telegram MCP ServerTelegram MCP server powered by Telethon to let MCP clients read chats, manage groups, and send/modify messages, media, contacts, and settings.
FMRS51 / 100 · D70 / 100 · B
Reliability8 / 209 / 20
Security and permissions11 / 2016 / 20
Maintenance8 / 2014 / 20
Documentation11 / 2017 / 20
Setup experience13 / 2014 / 20
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.
  • Developers who want to integrate Telegram into MCP clients like Claude
  • Automation scenarios that need to manage multiple Telegram accounts
  • Building custom Telegram bots or workflows
  • Scenarios that require secure file operation path restrictions
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.
  • Use cases requiring official Bot API features (this server uses a user client)
  • Non-technical users who want a fully managed solution
  • Multiple processes using the same session without lock management
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.
  • Requires Telegram API ID and API Hash
  • Requires the user's Telegram session string (equivalent to account access)
  • Can send messages, media, contacts, and settings to any allowed chat
  • Can create or modify groups, channels, and chat settings
  • Can access and operate on the user's media files and contacts
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.
  • Session string leakage could lead to account compromise
  • Sending messages may raise privacy or security concerns
  • Prompt injection: Telegram content may be maliciously crafted, so precautions are needed
  • Risk of using unofficial PyPI package name; avoid pip install telegram-mcp
  • Concurrent clients using the same session may cause AuthKeyDuplicatedError
Supported clientsClaude DesktopClaude Desktop, Cursor, Claude Code, Codex
Tools3076