Skip to main content
Glama
jgalea

telegram-mcp

by jgalea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to telegram-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-telegram

      StepanCEO
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants like Claude to read, search, and send messages through your personal Telegram account via MCP tools.
      MIT

    • telegram-mcp

      naim30
      F
      license
      Not graded
      quality
      C
      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.
      33 npm
      -

    • tgmcp

      OEvortex
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with Telegram accounts through MCP, supporting messaging, contacts, groups, media, and admin functions.
      4
      Apache 2.0

    • capy-tg-mcp

      smolnikov-k
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with a personal Telegram account via MCP, offering tools for reading and searching chats, summarizing unread messages, sending and editing messages, handling files and voice transcripts, and managing groups and channels, with read-only mode by default.
      Apache 2.0
    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

    C2.6/5.0

    Scored across 54 tools

    Disambiguation2/5

    Several tools have unclear boundaries, especially message retrieval: read_messages, get_new_messages, and today_messages all return messages with different scoping, while search_messages and search_regex overlap and export_chat/export_cached_messages are near-duplicates. download_media/download_chat_media and get_dialogs_stats/list_chats add further ambiguity.

    Naming Consistency4/5

    The vast majority of tools follow a clean verb_noun snake_case pattern, such as send_message, create_channel, get_participants, and set_chat_title. A few tools like chat_analytics, message_timeline, and today_messages break the verb-first convention, and the use of both 'dialogs' and 'chats' is inconsistent.

    Tool Count1/5

    54 tools is far beyond the well-scoped 3-15 range and lands in the 50+ extreme category. The surface feels bloated with overlapping retrieval, export, and analytics tools that could be consolidated.

    Completeness4/5

    Core Telegram workflows are well covered: messaging, scheduling, reactions, media, chat/group/channel lifecycle, participant management, contacts, admin logs, and local analytics. Gaps like forum-topic creation, scheduled-message deletion, and contact write operations are workaround-able rather than fatal.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources