Skip to main content
Glama
Sign In
Telegram Browser MCP

Telegram Browser MCP

by mishkidreams
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Telegram Browser MCP

No user-submitted related servers found.

    Related Servers

    • tgread

      demian-overflow
      A
      license
      A
      quality
      C
      maintenance
      Enables reading Telegram channels, groups, and direct messages through an MCP interface, with enforced read-only access so the agent cannot write to them.
      15
      MIT

    • TeleMCP

      charlesmmorais
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search and act on Telegram conversations, groups, channels, files, and links, with semantic search, AI-powered knowledge extraction, human-in-the-loop approvals, and PostgreSQL/pgvector persistence.
      Apache 2.0

    • tg-mcp

      Mobiss11
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to access and search Telegram conversations, including transcribed voice messages and OCR'd images, and to draft messages that require user approval before sending.
      15
      2
      MIT

    • tg-account-mcp

      Mesteriis
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to work with Telegram through explicitly selected user accounts and bots, supporting search, reading, sending, and message management with consent-based access.
      27 PyPI
      1
      Apache 2.0

    • telegram-mcp

      SHTIKOV
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to read Telegram chat history and search messages only within an explicit fail-closed allowlist, with no write, edit, or delete operations.
      MIT

    • Telegram MCP Readonly

      mshykhov
      A
      license
      Not graded
      quality
      B
      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
    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

    A4.1/5.0

    Scored across 10 tools

    Disambiguation4/5

    Tools have mostly distinct purposes: listing grants, resolving public chats, bulk collection, paginated reads, native search, context, exact message, comments, and attachments. There is minor overlap between collect_messages and search_messages/get_history because all retrieve messages, but the descriptions clarify different scopes (cross-chat/time vs single-chat search/pagination).

    Naming Consistency5/5

    All tool names use a consistent snake_case verb_noun pattern, predominantly get_* for read operations, with list_, collect_, resolve_, and search_ used appropriately. No mixing of camelCase or vague verb styles.

    Tool Count5/5

    Ten tools is well within the ideal range and each tool targets a distinct operation in the read-only Telegram observation workflow. The set feels deliberately scoped without redundant or filler tools.

    Completeness4/5

    The surface covers read-only browsing comprehensively: allowed chat discovery, public chat resolution, message collection, recent/history/search reads, context, exact messages, comments, and attachments. Minor gaps exist (e.g., no chat/topic enumeration or write/send operations), but these are outside the apparent read-only purpose and can be worked around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources