Skip to main content
Glama
draiqw

telegram-mcp

by draiqw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to telegram-mcp

No user-submitted related servers found.

    Related Servers

    • telegram-mcp

      vkruglikov
      A
      license
      A
      quality
      B
      maintenance
      Enables use of a personal Telegram account within MCP clients for reading and sending messages, searching chats, and managing media, all running locally.
      16
      9 npm
      MIT

    • Telegram MCP Server

      OrrBin
      A
      license
      B
      quality
      D
      maintenance
      Enables full access to your personal Telegram account via MCP, allowing reading, sending, and searching messages, managing chats, and retrieving user information through natural language commands.
      18
      54 npm
      4
      MIT

    • my-tg-mcp

      kiaquila
      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.
      -

    • docker-telethon-plus

      psyb0t
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes a Telegram user account via MCP, enabling AI agents to send, read, and manage messages, chats, and media using full MTProto access through Telethon. It wraps Telethon behind a JSON HTTP API and MCP endpoint, allowing agents to interact with Telegram as the authenticated user.
      3
      Do What The F*ck You Want To Public

    • telegram-mcp

      naim30
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to control a real Telegram user account via MTProto, allowing message sending, chat reading/searching, and message management through MCP tools.
      39 npm
      -

    • Telegram MCP

      Anonymouse8882
      F
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to interact with Telegram user accounts, providing tools for messaging, contacts, groups, channels, and media management through the Telegram API.
      85
      3
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 70 tools

    Disambiguation3/5

    Many tools overlap in purpose (e.g., tg_notify/tg_mute/tg_alert for notifications; tg_history/tg_message/tg_export/tg_unread for reading messages), and the large number of tools makes selection harder. Detailed descriptions help, but an agent could easily pick the wrong tool when multiple cover similar actions.

    Naming Consistency2/5

    All tools share the tg_ prefix, but beyond that the naming is erratic: bare verbs (tg_send), bare nouns (tg_contacts), verb_noun (tg_send_file), and noun_verb (tg_chat_edit) are mixed without a clear convention. The inconsistent action-object order makes patterns unpredictable.

    Tool Count1/5

    With 70 tools, this server is extremely heavy. Even for a comprehensive Telegram client, 70 is far beyond the typical well-scoped range (3-15) and likely to overwhelm agents, increasing selection errors and processing costs.

    Completeness5/5

    The tool surface is remarkably comprehensive, covering messaging, media, scheduling, folders, admin, accounts, stories, bots, search, translation, and moderation. It supports nearly every Telegram workflow an agent might need, with only minor gaps like profile editing.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources