Telegram Search MCP
Related Servers
Alternatives to Telegram Search MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to search and retrieve from your local macOS iMessage history using hybrid retrieval with context expansion, all processed locally without sending data off-device.-
- AlicenseNot gradedqualityBmaintenanceEnables reading Telegram chats and searching messages through natural language, connecting to MCP clients like Claude Code, Codex, and Cursor.27 npm1MIT
- AlicenseAqualityAmaintenanceEnables searching Telegram messages and chats, retrieving recent messages, and extracting text from attached documents (PDF, TXT, MD, CSV) using your personal Telegram account.4Apache 2.0
- AlicenseAqualityDmaintenanceEnables reading and searching Telegram channel/group/DM messages from Claude Code using MTProto for full message history access.547 npmMIT
- AlicenseBqualityCmaintenanceLets coding agents browse a personal Telegram account locally, retrieving per-chat text history and conversations or outgoing messages by date via QR login, read-only unless message sending is explicitly enabled. API credentials from Telegram are required, and access can be restricted to specific numeric chat IDs.3MIT
- AlicenseAqualityCmaintenanceEnables full-text search of macOS iMessages including link preview metadata. Works as an MCP server for Claude Desktop to search your messages locally.1MIT
TDQS
Scored across 15 tools
Tools target distinct resources and actions (global search, per-chat search, public search, history, context, thread, media, voice, drafts), but the three search tools and two media retrieval tools require close reading to distinguish. Detailed descriptions clarify scope, keeping ambiguity limited.
All tools use a consistent telegram_ prefix with a predictable verb_noun pattern (get_, list_, search_, download_, transcribe_). The few mixed verbs are semantically appropriate and no chaotic style appears.
15 tools sits within the well-scoped 3–15 range for a feature-rich Telegram search client. Each tool addresses a distinct capability such as search, history, context, media, voice, drafts, scheduled messages, or public-search consent.
Coverage is strong for a read-only search MCP: global and per-chat search, history, threads, context, media retrieval, voice listing/transcription, drafts, and scheduled messages are all present. Minor gaps like global media-type search or user/chat metadata lookup remain, but core workflows are well served.