Skip to main content
Glama
FantomaSkaRus1

telegram-bot-mcp

by FantomaSkaRus1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to telegram-bot-mcp

No user-submitted related servers found.

    Related Servers

    • Telegram Bot MCP

      pixellover1433
      F
      license
      Not graded
      quality
      A
      maintenance
      Exposes Telegram Bot API operations as MCP tools, enabling managing messages, chats, and forum topics via a FastMCP server.
      -

    • telegram-api-mcp

      timoncool
      A
      license
      C
      quality
      C
      maintenance
      Ultimate MCP server for Telegram Bot API — 169 methods, full v9.6 coverage, meta-mode, rate limiting, and circuit breaker, enabling AI to control Telegram bots with natural language.
      100
      28
      MIT

    • telegram-bot-mcp

      Eweol
      A
      license
      A
      quality
      D
      maintenance
      Exposes the Telegram Bot API as tools for MCP clients, enabling sending messages, photos, polls, and more via a Telegram bot.
      11
      MIT

    • mcp-telegram

      Moreti2002
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that lets an LLM send messages, photos, and documents to Telegram through a bot. Provides four tools: get_me, send_message, send_photo, and send_document.
      4
      MIT

    • Better Telegram MCP

      n24q02m
      A
      license
      Not graded
      quality
      A
      maintenance
      Production-grade MCP server for Telegram with dual-mode Bot API and MTProto. 6 composite tools covering messages, chats, media, contacts management with 3-tier token optimization.
      11
      Apache 2.0

    • mcp-telegram

      pauloFroes
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that wraps the Telegram Bot API into semantic tools for LLM agents, supporting multi-bot management for sending and receiving messages. It enables agents to send text, photos, and documents, as well as fetch recent updates from multiple configured Telegram bots.
      -
    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/5.0

    Scored across 100 tools

    Disambiguation3/5

    While many tools are distinct (send_photo vs send_document), there is notable overlap in message editing and business message editing (edit_message vs edit_business_message_text) and sending (send_message vs send_business_message). Some tools like get_my_short_description and set_my_short_description are clear, but the number of similar send_* and edit_* variants may cause an agent to pick the wrong one without careful reading.

    Naming Consistency4/5

    The naming is predominantly verb_noun (send_message, get_chat_info, edit_message), which is consistent. Minor deviations exist: 'log_out' vs 'logout', 'get_me' vs 'get_my_commands', and plural/singular variations (delete_messages vs delete_message) are understandable. Overall pattern is predictable.

    Tool Count2/5

    With 100 tools, the server is extremely heavy, far exceeding the typical 3-15 well-scoped tools. Most are direct wrappers of the Telegram Bot API, leading to a very large surface that may overwhelm agents. While each tool is simple, the sheer count makes it hard to navigate and select the right one.

    Completeness5/5

    The tool set covers the full Telegram Bot API lifecycle: sending all media types, editing, deleting, chat management (ban, restrict, invite links), bot configuration (set_my_*), and updates (get_updates). It is comprehensive, with no obvious missing core operations such as getting updates or deleting messages, which are all present.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources