Skip to main content
Glama
timoncool

telegram-api-mcp

by timoncool

Related Servers

Alternatives to telegram-api-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      22 npm
      7
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables interaction with the Telegram Bot API, allowing users to send messages, retrieve updates, and access chat information through natural language.
      -
    • A
      license
      A
      quality
      C
      maintenance
      MCP server that exposes a Telegram bot, enabling sending messages and retrieving updates through natural language.
      3
      1
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      An MCP server for interacting with Telegram bots and channels using the Telegraf library. It allows AI agents to send messages, manage channels, forward content, and intelligently respond to Telegram conversations.
      5
      23 npm
      8
      -
    • 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.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for sending and receiving Telegram messages via a bot, enabling AI assistants to interact directly through Telegram by sending messages, reading recent messages, and sending photos.
      22 npm
      MIT

    TDQS

    C2.9/5.0

    Scored across 173 tools

    Disambiguation4/5

    Tools map to distinct Telegram API actions and are mostly separable by resource and verb. Singular/plural variants like forward_message vs forward_messages and custom helpers like get_file vs download_file create minor overlap, but descriptions clarify their intended use.

    Naming Consistency4/5

    The dominant pattern is consistent snake_case verb_noun naming (get_, set_, send_, edit_, delete_, create_, etc.). A few standalone verbs like close, get_me, and log_out break the pattern slightly but are still predictable.

    Tool Count2/5

    At 173 tools, the server is dramatically over-scoped for typical MCP use. Even though Telegram's API is broad, this many tools creates a heavy selection burden and far exceeds the recommended 3-15 tool range.

    Completeness5/5

    The tool surface covers nearly every major Telegram Bot API area: messages, media, chat administration, stickers, payments, business accounts, stories, gifts, forums, invites, webhooks, inline mode, and bot configuration. There are no obvious dead ends in the core workflows.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive