Skip to main content
Glama
stufently

telegram-ai-cli-mcp

by stufently
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to telegram-ai-cli-mcp

No user-submitted related servers found.

    Related Servers

    • Telegram MCP Bridge

      boltholds
      A
      license
      B
      quality
      D
      maintenance
      Provides read-only access to a user's Telegram account via MTProto, enabling chat listing, message retrieval, search, and context fetching.
      5
      MIT

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

    • better-tg-cli MCP server

      TheVilfer
      A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server exposes a Telegram client that runs on the user's own account, enabling AI agents to read, search, send, and manage messages, press bot buttons, and work with chats, groups, and channels from the terminal. It is read-only by default, with writes requiring explicit human approval and every action logged for safety.
      1,373 npm
      3
      MIT

    • tlgrm

      ali-commits
      A
      license
      Not graded
      quality
      C
      maintenance
      Drives a personal Telegram account from the terminal or via MCP, enabling AI assistants to list chats, send/edit messages, fetch history, manage groups, and more with tiered read/write/destructive permissions.
      1
      MIT

    • telegram-user-mcp

      22syn
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that connects to Telegram as your real user account and exposes read-only tools to read and search messages, list chats and folders, inspect group info, and download media.
      16 npm
      MIT

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

    Disambiguation4/5

    The server includes explicit 'do not use' notes that sharply distinguish most read surfaces, but pairs such as telegram_chats vs telegram_inbox and telegram_search vs telegram_archive_search can still be confused at a glance. With 21 tools, the risk of misselection remains slightly above minimal despite the strong descriptive guidance.

    Naming Consistency4/5

    All tools share the predictable telegram_ prefix, and most follow an entity_action or entity pattern. The suffixes mix pure nouns (chats, inbox, drafts) with verb phrases (chat_read, archive_sync) and standalone verbs (watch, search), but the deviations are minor and still readable.

    Tool Count3/5

    21 tools is above the typical 3-15 sweet spot and feels heavy for a single server interface. While many tools serve distinct read, archive, media, or account purposes, some consolidation could reduce surface area without losing functionality.

    Completeness2/5

    The read, archive, media, and account-inspection surface is broad, but there are no Telegram write actions such as sending messages, joining/leaving chats, reacting, marking read, or managing folders. Descriptions even reference telegram_plan_* tools that are absent from the provided tool list, creating significant agent dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources