Telegram MCP — Next Generation
Related Servers
Alternatives to Telegram MCP — Next Generation
- AlicenseBqualityCmaintenanceEnables MCP clients to operate a Telegram account as a userbot, providing tools for reading and sending messages, searching chats and contacts, managing media, and performing other account actions via MTProto with a locally encrypted session.28MIT
Related Servers
- FlicenseBqualityCmaintenanceEnables MCP clients to interact with Telegram user accounts, providing tools for messaging, contacts, groups, channels, and media management through the Telegram API.853-
- AlicenseAqualityCmaintenanceEnables local, privacy-first control of a personal Telegram account through MCP, using TDLib to read chats, send and reply to messages, search, transfer files, and interact with approved inline buttons.20MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to drive a real Telegram account, exposing chats, messages, media, secret chats, admin rights, invite links, Mini Apps, and multi-account routing as callable tools.1GPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with Telegram accounts through MCP, supporting messaging, contacts, groups, media, and admin functions.4Apache 2.0
- FlicenseAqualityCmaintenanceMCP server that gives MCP clients access to a personal Telegram account. It can read chats, search messages, download media, and send messages or files while keeping credentials local.7-
- FlicenseBqualityBmaintenanceProvides full access to a personal Telegram account via MTProto, enabling MCP clients to read chats, send messages, manage media, and more.70-
TDQS
Scored across 35 tools
Tools span distinct resources but several near-duplicate retrieval operations (get_chats/list_chats/get_chat/get_full_chat, get_messages/list_messages/get_history) rely on cross-references to disambiguate. The descriptions help, but an agent could still misselect among message-fetching and chat-listing tools.
Almost entirely consistent snake_case verb_noun pattern (list_, get_, search_, sync_), with only minor exceptions like cache_health and get_me. The naming is highly predictable and readable.
35 tools is well above the 15-tool ideal for an MCP surface. Many retrieval variants could be consolidated, making the set heavy and harder to navigate.
The surface is overwhelmingly read-only: no send_message, send_media, edit/delete, pin/unpin, download_media, set_bot_commands, or set_privacy_settings, despite descriptions referencing several of these missing tools. Core write and lifecycle operations for Telegram are absent.