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 MCP Server

      Muhammadyunusxon
      A
      license
      Not graded
      quality
      A
      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
      B
      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.
      39 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

    • tgx

      mal4i6ka
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to operate a Telegram account through the same commands as the terminal client: messaging, chat management, voice transcription, calls, stickers, and privacy settings.
      1
      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

    A4/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: send, send_file, and forward are differentiated by payload type and behavior; list_chats, get_chat, history, and search cover different levels of querying. No obvious overlaps or ambiguities.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (send_file, list_chats, mark_read, download_media), but 'whoami' and 'history' deviate as standalone nouns. Overall the naming is consistent and predictable, with minor exceptions.

    Tool Count5/5

    13 tools is within the typical 3-15 range and feels well-scoped for a messaging client. Each tool addresses a distinct part of the workflow without unnecessary bloat.

    Completeness4/5

    The core messaging lifecycle is covered: retrieving (list, get, history, search), sending (send, send_file, forward), mutating (edit, delete, mark_read), and identity (whoami). Some advanced features like pinning or archiving are absent, but the essential operations are complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources