Skip to main content
Glama
alexeyleshchenko

Telegram MCP Server

by alexeyleshchenko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Telegram MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-telegram

      Prgebish
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects AI assistants to your real Telegram account via User API (MTProto). Features default-deny ACL with per-chat permissions, message search, file sending, forwarding, media downloads, and rate limiting.
      3
      MIT

    • tg-mcp

      draiqw
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that gives AI agents full access to a personal Telegram account via MTProto, enabling chat reading, history search, messaging, media handling, and automations.
      79
      MIT

    • tg-mcp

      MyrikLD
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes a Telegram user account over HTTP, enabling message sending, dialog listing, history retrieval, and message search via tools like send_message and list_dialogs.
      -

    • mcp-telegram

      beautyfree
      A
      license
      B
      quality
      D
      maintenance
      A Telegram MCP server that connects agents to a real Telegram user account via MTProto, enabling reading, searching, sending, moderating, and managing Telegram chats through natural language or automated tool calls.
      100
      90 npm
      29
      MIT
    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

    A4.4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct action: finding chats, reading/searching messages in one chat, searching globally, sending, editing, and fetching chat info. The two send tools are clearly separated by target (chat_id vs phone), and global search vs per-chat search is explicitly scoped.

    Naming Consistency4/5

    Tool names mostly follow a clean verb_noun pattern in snake_case (get_messages, send_message, edit_message, get_chat_info). Minor deviations like search_messages_globally and send_message_to_phone add modifiers, but the pattern remains predictable and readable.

    Tool Count5/5

    Eight tools is a well-scoped size for a Telegram MCP server. Each tool covers a meaningful capability without unnecessary fragmentation, and the low-level invoke_mtproto tool rounds out the surface without bloating it.

    Completeness4/5

    Core workflows are covered: finding chats, reading/searching messages, sending, editing, and getting chat info. Obvious gaps like message deletion or marking messages read are not wrapped, but invoke_mtproto provides an escape hatch, so agents are not entirely blocked.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources