mcp-telegram-agent
Related Servers
Alternatives to mcp-telegram-agent
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.1737 PyPIMIT
- AlicenseAqualityCmaintenanceEnables AI assistants to interact with Telegram via the Bot API, including sending messages, media, polls, and managing chats and updates.16MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with the Telegram Bot API, allowing them to send messages, forward messages, get bot information, and receive updates.11 npm3MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with Telegram through 50+ tools for chats, messages, contacts, users, groups, and channels, with per-topic isolation and a reactive inbox for multi-agent use.MIT
- 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 gradedqualityBmaintenanceEnables AI agents to work with Telegram through explicitly selected user accounts and bots, supporting search, reading, sending, and message management with consent-based access.27 PyPI1Apache 2.0
TDQS
Scored across 13 tools
Each tool maps to a distinct Telegram content type (text, poll, location, contact, dice, album), so selection is mostly unambiguous. The only soft overlap is between send_local_document ('any local file') and the typed senders send_local_photo/video/audio, which an agent could plausibly confuse for a file that is also an image.
Nearly all tools follow a clean send_<object> snake_case pattern (send_text_message, send_poll, send_location), with edit_message_text and delete_message matching the same verb_noun convention. The send_local_* prefix groups file-based senders predictably, and the mode-based send_local_audio_or_voice is a readable, intentional deviation.
13 tools sit squarely in the well-scoped range for a messaging bot surface. Each tool earns its place by covering a distinct Telegram message type rather than duplicating functionality.
Outbound messaging is thoroughly covered: text, all media types, albums, polls, locations, contacts, dice, plus message edit and delete for lifecycle management. Obvious gaps remain around inbound/read operations (fetching or reading chat history), forwarding, and pinning, which would limit an agent working interactively with a conversation.