Skip to main content
Glama
salto-agancy

Telegram MCP

by salto-agancy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Telegram MCP

No user-submitted related servers found.

    Related Servers

    • telegram-mcp

      expremiental
      F
      license
      A
      quality
      B
      maintenance
      Read-only MCP server for self-hosted Telegram access via Telethon. Enables reading messages, chats, and media but disallows any write operations.
      10
      -

    • my-tg-mcp

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

    • telegram-mcp

      nskondratev
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only Telegram MCP server that only exposes a user-defined allowlist of chats, providing tools to list chats, fetch messages, search, and get context while stripping untrusted text and with no write capabilities.
      MIT

    • Telegram MCP Server

      tolboy
      A
      license
      Not graded
      quality
      A
      maintenance
      A safe-by-default MCP server for real Telegram accounts powered by TDLib, enabling AI agents to read and act on your account with read-only mode and human approval for destructive actions.
      5
      Apache 2.0

    • codex-telegram

      briejhxh
      A
      license
      A
      quality
      C
      maintenance
      Enables local, privacy-first control of a personal Telegram account through MCP, using TDLib to read chats, send and reply to messages, search, transfer files, and interact with approved inline buttons.
      20
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools are clearly scoped by resource and action (read, send, search, media, chat info). The main overlap is among send_message, send_rich_message, and send_message_to_phone, but their descriptions draw useful boundaries. search_messages_globally and get_messages search also overlap slightly, though scope differences clarify use.

    Naming Consistency4/5

    Names are consistently snake_case and mostly follow verb_noun order, e.g., get_messages, send_message, edit_message, find_chats. Minor deviations exist, such as search_messages_globally and send_message_to_phone, but the pattern remains predictable.

    Tool Count5/5

    Ten tools is a well-scoped set for a Telegram MCP server. Each tool covers a distinct capability without excessive fragmentation. The count supports both core messaging and specialized media/link handling.

    Completeness3/5

    The surface covers reading, sending, editing, searching, chat discovery, info, and media access. However, common Telegram lifecycle operations like deleting, forwarding, pinning, and reacting to messages are missing. These gaps are notable but not crippling for basic agent workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources