secure-telegram-mcp
Related Servers
Alternatives to secure-telegram-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to control a personal Telegram account for sending/reading messages, media, group management, and more via the MTProto API.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to operate a Telegram account through the same commands as the terminal client: messaging, chat management, voice transcription, calls, stickers, and privacy settings.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to scoped, permissioned access to Telegram chats with per-chat read/write levels and human approval for sending messages.2MIT
- 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.50 PyPI1Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to access and manage your real Telegram account, including chats, messages, media, contacts, groups, and administrative actions via MTProto.1395 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI clients to securely authenticate with a Telegram account via QR code and read or manage chats, messages, media, polls, contacts, and group administration through 50+ tools.58 npm1MIT
This server cannot be deployed
TDQS
Scored across 18 tools
Each tool maps to a distinct Telegram operation and resource; the few potentially confusable pairs are explicitly delineated (get_media_info vs download_media = metadata vs bytes; prepare_media vs send_media = two-phase staging vs delivery; get_pinned_messages vs get_messages = filtered vs stream). Descriptions consistently state scope, prerequisites, and when to prefer the sibling tool, so an agent can select reliably.
Uniform snake_case verb_noun pattern throughout (get_messages, send_message, list_topics, edit_message, delete_message, forward_message, mark_read, save_draft, prepare_media). Verb choice is semantically predictable (get/list/search/send/edit/delete/forward/mark), with no camelCase or stylistic mixing.
18 tools is on the heavier side of the ideal band, but each corresponds to a real Telegram capability rather than a redundant variant. The two-phase media pair (prepare_media + send_media) adds surface area that is justified by the security model of never accepting raw paths twice.
Coverage is strong across read/send/media/topics/participants/moderation/drafts/read-receipts, including full message lifecycle (send, edit, delete, forward, react). Notable gaps: there is get_pinned_messages but no pin/unpin_message, no single-message fetch by id, and draft clearing is explicitly deferred, though agents can work around all of these.