mcp-server-telegram-bot
Related Servers
Alternatives to mcp-server-telegram-bot
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to send and receive messages, media, and files on Telegram, and manage chats via a bot token.1736 PyPIMIT
- AlicenseBqualityDmaintenanceEnables AI agents to send notifications and media (text, photos, documents, videos) via a Telegram bot.4197 npm4Do What The F*ck You Want To Public
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to work with Telegram through explicitly selected user accounts and bots, supporting search, reading, sending, and message management with consent-based access.120 PyPIApache 2.0
- AlicenseAqualityCmaintenanceEnables AI assistants to interact with Telegram via the Bot API, including sending messages, media, polls, and managing chats and updates.16MIT
- AlicenseNot gradedqualityCmaintenanceEnables an LLM to send text messages, documents, photos, videos, and audio to a fixed Telegram recipient via a Telegram bot, with no incoming-message tools or polling.246 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with the Telegram Bot API, allowing them to send messages, forward messages, get bot information, and receive updates.13 npm3MIT
TDQS
Scored across 9 tools
Each send_* tool is distinguished by payload type (text, document, photo), and the add/remove pairs are clearly scoped to chats vs directories. The only mild overlap is between list_access and get_updates, both of which surface chat ids, but the descriptions clarify their distinct purposes (config listing vs. reading incoming messages).
All nine tools follow a clean verb_noun pattern (send_message, get_updates, list_access, add_chat, remove_dir, etc.) with consistent snake_case throughout. No mixed conventions or vague one-word verbs.
Nine tools is well within the ideal range and each one earns its place: three send variants, one read tool, and a complete add/remove/list triad for both chats and directories. Nothing feels redundant or padding.
Core lifecycle is covered: send text/files, read incoming messages, and manage allowed chats/directories at runtime. Minor gaps exist (no message edit/delete, no reply/threading, no audio/video send), but agents can accomplish the primary workflows without dead ends.