Telegram Context MCP
Related Servers
Alternatives to Telegram Context MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceRead-only MCP access to a personal Telegram account. Allows querying chats, reading and searching messages via Streamable HTTP.-
- AlicenseNot gradedqualityCmaintenanceLets any MCP client list, read, and search chats in the user's own Telegram account through a read-only server, without sending, editing, or deleting messages.58 npm1MIT
- AlicenseAqualityBmaintenanceGives MCP clients controlled access to a Telegram user account, letting them search and read messages, inspect chats, and fetch media, with sending or editing messages available only after explicit opt-in. It runs self-hosted over FastMCP and Telethon with strict read-only defaults, OAuth or bearer authentication, and an outbound-only Cloudflare Tunnel.11MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to read and search Telegram chats, fetch media, export messages, inspect channel analytics, build a local index, and prepare confirmed replies, sends, reactions, joins, and callback button presses across multiple accounts through one daemon.MIT
- FlicenseBqualityBmaintenanceProvides full access to a personal Telegram account via MTProto, enabling MCP clients to read chats, send messages, manage media, and more.70-
- AlicenseBqualityBmaintenanceEnables MCP clients to read and search personal Telegram chats, manage messages and chats, clean up spam or deleted-account conversations, and adjust privacy and login settings through Telegram’s official MTProto API. Destructive actions preview by default and require confirmation before execution.182MIT
TDQS
Scored across 23 tools
Most tools have clearly distinct resource/action targets, and the verbose descriptions explicitly cross-reference overlapping tools such as get_context vs. get_thread and get_changes vs. get_watch_changes. However, the read surface contains several similar-sounding operations (get_history, export_history, search_messages, get_messages) that could still cause occasional misselection.
All tool names use snake_case with a predictable verb_noun structure, such as get_chat, list_chats, search_messages, create_watch, and download_attachment. Specialized names like ack_watch_changes and extract_attachment_text remain consistent with the same convention.
At 23 tools, the server is in the borderline-heavy range. The broad Telegram context domain justifies many specialized operations, but the count is large enough that some tools feel adjacent rather than essential.
The surface covers chat discovery, message retrieval, search, history export, threads, albums, pinned messages, topics, watches, and attachment handling, which is comprehensive for a read-oriented context server. Minor gaps remain around direct user/member lookup and richer media operations, but core workflows are covered.