Skip to main content
Glama
OrrBin

Telegram MCP Server

by OrrBin

Related Servers

Alternatives to Telegram MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables an MCP client to operate a personal Telegram account directly: read chats, send messages, interact with bots, schedule broadcasts, and research YouTube, Reddit, and Instagram.
      -
    • 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
    • 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
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables a trusted MCP assistant to access a personal Telegram account for finding existing chats and contacts, reading bounded history, preparing immutable message previews, and deliberately sending or replying only to explicitly authorized messages.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables users to interact with their own Telegram account through MTProto, supporting chat listing, message reading and searching, sending messages, and fetching contacts via MCP tools.
      -
    • A
      license
      C
      quality
      D
      maintenance
      Connects AI tools to Telegram via MCP, enabling reading chats, sending messages, managing groups, and more using your own account.
      54
      24 PyPI
      5
      MIT

    TDQS

    B3.2/5.0

    Scored across 18 tools

    Disambiguation2/5

    Multiple tools have unclear boundaries, particularly around files/media: get_file_info vs get_media_info, get_media_content vs download_file, and send_media vs send_document are easily confused. The descriptions do not clearly differentiate these tools, which could lead an agent to select the wrong one.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., search_chats, send_message, get_chat_info). This makes the naming predictable and easy to learn, with no mixed styles or arbitrary deviations.

    Tool Count4/5

    The server has 18 tools, slightly above the typical well-scoped range of 3-15. However, given the breadth of Telegram's API and the need to cover messaging, media, search, and chat management, the count is reasonable and not excessive.

    Completeness4/5

    The tool set covers the core Telegram operations: sending messages/media, retrieving messages, searching, editing/deleting/forwarding, and chat/user info. Minor gaps exist, such as no direct 'get message by ID' or chat management operations like leaving a chat, but agents can generally accomplish tasks with the provided tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues