Skip to main content
Glama
thenavidm

telegram-mcp-cli

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to telegram-mcp-cli

No user-submitted related servers found.

    Related Servers

    • Telegram User MCP

      oladikezz
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to directly control a personal Telegram account via MTProto, providing access to chats, messages, search, and account management features.
      MIT

    • Telegram MCP Server

      Muhammadyunusxon
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control a personal Telegram account for sending/reading messages, media, group management, and more via the MTProto API.
      MIT

    • telegram-plugin

      kartollikaa
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to read your own Telegram account via MTProto, including listing chats, searching and reading message history, resolving chats, and downloading attachments, with sending available only when explicitly enabled.
      MIT

    • telegram-mcp

      naim30
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to control a real Telegram user account via MTProto, allowing message sending, chat reading/searching, and message management through MCP tools.
      15 npm
      -

    • telegram-mcp

      AnubhavChaturvedi-GitHub
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives an AI assistant full control of a real Telegram user account over MTProto, enabling it to read chats, search history, send and manage messages, and dynamically create new tools as needed.
      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.6/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: send is for text, send_file for files, and read-side tools like list_chats, get_chat, history, and search differ by scope. Minor overlap exists between send/send_file and history/search, but the descriptions resolve it well.

    Naming Consistency3/5

    Names mix bare verbs (send, edit, delete, forward, resolve), verb_noun forms (download_media, send_file, list_chats, get_chat, mark_read), and a noun/whoami. All are lowercase and readable, but there is no single consistent pattern.

    Tool Count5/5

    13 tools is well within the ideal range and each maps to a distinct Telegram operation. The set feels scoped and no tool appears to be filler.

    Completeness4/5

    Core messaging lifecycle is covered: identity, resolution, reading, sending, editing, deleting, forwarding, media, and read marking. Minor gaps remain for reply threading, chat/group management, or contact operations, but core agent workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources