Skip to main content
Glama
antonio-castellon

io.github.antonio-castellon/mcp-telegram-bridge

by antonio-castellon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to io.github.antonio-castellon/mcp-telegram-bridge

No user-submitted related servers found.

    Related Servers

    • telegram-bot

      Evr1kys
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to read allowlisted Telegram chats and send messages as a bot, with access control, local secrets, and duplicate send protection.
      1
      MIT

    • telegram-mcp-bridge

      ph4ntom-rev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients like Codex or ChatGPT to securely receive, acknowledge, and send Telegram messages with durable delivery guarantees and idempotency.
      MIT

    • 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
      -

    • 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
    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

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct Telegram API endpoint: identity, chat info, sending messages, editing buttons, answering callbacks, and fetching updates. The only minor ambiguity is between send_message and edit_reply_markup since both handle buttons, but their purposes (new vs. existing message) are clearly different.

    Naming Consistency5/5

    All tools follow a consistent 'telegram_' prefix followed by a verb_noun pattern (e.g., get_me, get_chat, send_message). The naming is predictable and consistent across the entire set.

    Tool Count5/5

    With 6 tools, the server covers the essential operations for a Telegram bridge without unnecessary bloat. Each tool serves a clear purpose in the core workflow of a bot, making the count well-scoped.

    Completeness3/5

    The server covers identity, chat info, sending, editing, callback answers, and updates. However, it lacks common operations like deleting messages or sending media/files. Also, the update loop relies heavily on the agent, and there is no method to manage webhooks, but the core messaging loop is covered.

    Resources