Skip to main content
Glama
EyalWerber

telegram-mcp

by EyalWerber
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to telegram-mcp

No user-submitted related servers found.

    Related Servers

    • telegram-mcp-server

      Schimmilab
      A
      license
      A
      quality
      B
      maintenance
      Enables reading chats, messages, and media and sending messages/files via a Telegram user account (MTProto/Telethon), supporting group history and media that bots cannot access.
      8
      MIT

    • telegram-mcp

      vkruglikov
      A
      license
      A
      quality
      B
      maintenance
      Enables use of a personal Telegram account within MCP clients for reading and sending messages, searching chats, and managing media, all running locally.
      16
      7 npm
      MIT

    • telegram-user-mcp

      alexmakeev
      A
      license
      Not graded
      quality
      B
      maintenance
      Integrates Telegram user account with MCP, exposing operations like reading and sending messages, managing chats, and more via stdio or SSE transport.
      Apache 2.0

    • telegram-mcp

      bssth
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to operate a Telegram account as a userbot, providing tools for reading and sending messages, searching chats and contacts, managing media, and performing other account actions via MTProto with a locally encrypted session.
      28
      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.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: get_latest_image retrieves a previously posted photo, while wait_for_next_image blocks for a new one. The use cases do not overlap in an ambiguous way.

    Naming Consistency4/5

    Both names follow a verb-noun structure and clearly communicate function. The slight mix of 'get_' and 'wait_for_' is a minor deviation but still predictable.

    Tool Count3/5

    Two tools is at the low end of a reasonable scope for a narrow image-receiving server. They cover the core need without bloat, but the server feels rather thin.

    Completeness4/5

    The pair covers the two key workflows: retrieving a previous screenshot and waiting for a new one. Missing features like explicit image search or sending could be useful, but they are not essential for the server's obvious intent.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources