Skip to main content
Glama
Eweol

telegram-bot-mcp

by Eweol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

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-mcp-kit

      QuocTang
      A
      license
      A
      quality
      D
      maintenance
      Exposes the Telegram Bot API as tools for Claude Code or any MCP client, enabling message sending, chat management, file handling, and bot information retrieval.
      20
      1
      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

    • telegram-bot-mcp

      FantomaSkaRus1
      A
      license
      B
      quality
      C
      maintenance
      Full-featured Telegram Bot API server for MCP (Model Context Protocol). 174 tools covering the entire Bot API — messages, chats, stickers, payments, forums, stories, and more.
      100
      35 npm
      7
      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.5/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct action or resource: chat operations (get_chat, get_chat_member_count, list_chats), message sending by type (send_message, send_photo, send_document, send_location, send_poll), and message editing/deletion (edit_message_text, delete_message). The send_* tools are clearly differentiated by content type, and get_me is a distinct bot-info operation.

    Naming Consistency4/5

    The naming follows a mostly consistent verb_object pattern: get_chat, send_message, send_photo, delete_message, list_chats, edit_message_text, get_me, get_chat_member_count. The only slight deviation is get_chat_member_count (three-word object) and get_me (pronoun instead of noun), but these are minor and not confusing.

    Tool Count5/5

    At 11 tools, the server is well-scoped for a Telegram bot MCP. Each tool covers a common, distinct Telegram operation without bloat. There is no overlap, redundancy, or superfluous tools.

    Completeness4/5

    The tool set covers core Telegram operations well: sending (all message types), editing, deletion, chat discovery, and bot info. Minor gaps include no ability to send stickers/video/audio, no pin/unpin message, no forward_message, and no reply-to support beyond basic sending, but these are edge operations not essential for most bot workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources