telegram-api-mcp
Related Servers
Alternatives to telegram-api-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceFull-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.10022 npm7MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that enables interaction with the Telegram Bot API, allowing users to send messages, retrieve updates, and access chat information through natural language.-
- AlicenseAqualityCmaintenanceMCP server that exposes a Telegram bot, enabling sending messages and retrieving updates through natural language.31MIT
- FlicenseAqualityDmaintenanceAn 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.523 npm8-
- FlicenseNot gradedqualityDmaintenanceAn 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.-
- AlicenseNot gradedqualityDmaintenanceAn 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 npmMIT
TDQS
Scored across 173 tools
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.
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.
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.
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.