Skip to main content
Glama
antonio-castellon

mcp-telegram-bridge

by antonio-castellon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to 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

    • teleloom

      starsinc1708
      A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server enables agents to connect to Telegram accounts and bots to search chats, review unread messages, build sourced digests, inspect media and documents, and prepare or execute confirmed actions with scoped permissions.
      1
      MIT

    • Telegram MCP

      Anonymouse8882
      F
      license
      B
      quality
      D
      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.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: fetching chat metadata, bot identity, polling updates, acknowledging callbacks, editing inline markup, and sending messages. There is no overlap in purpose, and an agent can select the right tool unambiguously from the descriptions.

    Naming Consistency5/5

    All tools follow a consistent telegram_verb_noun pattern (get_chat, get_me, get_updates, answer_callback, edit_reply_markup, send_message). Verb choices are predictable and readable.

    Tool Count5/5

    Six tools is well-scoped for a Telegram bridge, covering the core send/receive/callback loop without bloat. Every tool earns its place in the minimal agent workflow.

    Completeness4/5

    The surface covers the essential bridge lifecycle: polling updates, sending messages, acknowledging callbacks, editing markup, and fetching chat/bot metadata. Minor gaps exist for non-text message sending or message editing/deletion, but agents can work around these for the core bridge purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources