Skip to main content
Glama
boltholds

Telegram MCP Bridge

by boltholds
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Telegram MCP Bridge

No user-submitted related servers found.

    Related Servers

    • my-tg-mcp

      kiaquila
      F
      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 Readonly

      mshykhov
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search and analyze a Telegram account as a read-only knowledge source, allowing chat discovery, message search, history reading, contact inspection, and media download without exposing any mutating Telegram tools.
      13
      Apache 2.0

    • telegram-mcp

      sigman78
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets any MCP client list, read, and search chats in the user's own Telegram account through a read-only server, without sending, editing, or deleting messages.
      55 npm
      1
      MIT

    • telegram-mcp

      Shaan-alpha
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with a user's Telegram account: list chats, read history, search, and send messages through Telegram's MTProto API.
      2
      MIT

    • telegram-mcp

      iamkw0n
      F
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server for personal Telegram accounts, exposing chat folders, chats, and recent messages via MTProto.
      -
    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

    B3.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: listing chats, getting chat info, retrieving messages, getting message context with surrounding messages, and searching. No overlap in functionality.

    Naming Consistency5/5

    All tools follow the consistent pattern 'telegram_verb_noun', with verbs like get, list, search used predictably.

    Tool Count4/5

    5 tools is appropriate for a focused read-only Telegram bridge, covering core operations without being excessive or insufficient.

    Completeness3/5

    The tool set covers reading and searching but lacks send, delete, or chat management operations, which are notable gaps for a Telegram bridge if write capabilities are expected.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources