Skip to main content
Glama
Telegram Context MCP

Telegram Context MCP

by egor-fedorov

Related Servers

Alternatives to Telegram Context MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP access to a personal Telegram account. Allows querying chats, reading and searching messages via Streamable HTTP.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Lets 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 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Gives 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.
      11
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • F
      license
      B
      quality
      B
      maintenance
      Provides full access to a personal Telegram account via MTProto, enabling MCP clients to read chats, send messages, manage media, and more.
      70
      -
    • A
      license
      B
      quality
      B
      maintenance
      Enables 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.
      18
      2
      MIT

    TDQS

    A3.8/5.0

    Scored across 23 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data