Skip to main content
Glama
Sign In
Telegram MCP

Telegram MCP

by aminkh17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Telegram MCP

No user-submitted related servers found.

    Related Servers

    • 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

      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

    • NetGram

      dm1tryG
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to scoped, permissioned access to Telegram chats with per-chat read/write levels and human approval for sending messages.
      1
      MIT

    • tgmcp

      lum1nxus
      A
      license
      Not graded
      quality
      B
      maintenance
      A read-only server that lets any MCP client or model list, search, and read your own Telegram chats, including chat details, forum topics, message history, and surrounding context. It never sends, edits, or deletes anything, and stores your Telegram credentials encrypted at rest.
      MIT

    • Telegram Browser MCP

      mishkidreams
      A
      license
      A
      quality
      C
      maintenance
      Enables agents to perform read-only access to explicitly permitted chats on Telegram Web, including history, native search, post comments, photos and files, multi-chat context collection, and persistent local conversation history via a dedicated browser profile without Telegram API registration.
      10
      MIT
    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 12 tools

    Disambiguation5/5

    Each tool has a distinct purpose: authentication steps are sequential and clearly separated, chat tools cover discovery/listing/details, and message tools cover listing, searching, fetching one, and sending. There is little risk of confusing one tool for another.

    Naming Consistency5/5

    All tool names use consistent snake_case with clear verb_noun or auth_* prefixes. The pattern is predictable across authentication, chat, and message operations.

    Tool Count5/5

    Twelve tools is well-scoped for a Telegram MCP server, covering authentication, chat discovery, message reading, search, and sending without excessive surface area.

    Completeness4/5

    The server covers the core lifecycle: login/logout/status, chat discovery and allowlist inspection, message reading/searching, and sending. Minor gaps exist around message editing/deletion, replies, and media, but core workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources