Skip to main content
Glama
beautyfree

mcp-telegram

by beautyfree
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-telegram

No user-submitted related servers found.

    Related Servers

    • tg-mcp

      draiqw
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that gives AI agents full access to a personal Telegram account via MTProto, enabling chat reading, history search, messaging, media handling, and automations.
      79
      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.
      25 npm
      -

    • MCP Telegram Bot Server

      M00N77
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that gives LLMs access to Telegram Bot API, enabling them to read recent messages and reply to users via persistent local storage and MCP tools.
      -

    • telegram-mcp

      zhigang1992
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables interaction with Telegram to send, read, and search messages across chats and dialogs. It supports waiting for incoming messages and retrieving conversation history through natural language commands.
      4 npm
      3
      MIT

    • tgmcp

      watzon
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that automates a single Telegram user account via the Telegram user API, enabling chat listing, reading/sending messages, searching, and additional actions through natural language.
      12 npm
      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

    B3.4/5.0

    Scored across 111 tools

    Disambiguation4/5

    Each tool targets a distinct resource and action, with specific names like send_story vs send_file. Some overlap exists between similar admin tools (ban_user vs restrict_user vs kick_participant), but descriptions clarify the differences. Overall, the boundaries are clear.

    Naming Consistency5/5

    All tools use snake_case with a consistent verb_noun pattern (list, send, get, create, delete, edit, toggle). There are no mixed conventions or camelCase. Some verbs like 'get' vs 'list' are used interchangeably, but the pattern is uniform.

    Tool Count1/5

    111 tools is far beyond the 15-tool sweet spot and in the extreme range. Even for a comprehensive Telegram client, this is an overwhelming surface that likely requires heavy filtering to be usable.

    Completeness5/5

    The tool set covers nearly every major Telegram feature: messaging, media, stories, admin, channels, folders, contacts, privacy, stickers, and more. The raw invoke_mtproto fallback fills any gaps, making the surface effectively complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources