telegram-archive-mcp
Related Servers
Alternatives to telegram-archive-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceRead-only MCP server that exposes retrieval tools over a Telegram chat archive, including archive overview, full-text search with Russian morphology, aggregates, message retrieval, and local context. It lets LLM agents answer questions from chat history without syncing Telegram, downloading files, or modifying the index.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that connects to Telegram as your real user account and exposes read-only tools to read and search messages, list chats and folders, inspect group info, and download media.16 npmMIT
- AlicenseAqualityBmaintenanceAn MCP server that gives AI agents full access to a personal Telegram account via MTProto, enabling chat reading, history search, messaging, media handling, and automations.79MIT
- AlicenseNot gradedqualityAmaintenanceLets MCP clients like ChatGPT Web and Claude Web read, search, and reply to your personal Telegram chats through the official Telegram Business API, using a self-hosted SQLite archive without MTProto sessions.3Apache 2.0
- FlicenseNot gradedqualityBmaintenanceAn MCP server that connects to a Telegram group chat, persists messages to a local SQLite database, and exposes tools to search, retrieve, and send messages via SSE.-
- AlicenseAqualityAmaintenanceMCP server that acts as a gateway to Telegram, providing AI-optimized tools for messaging, search, and chat management via MTProto. Supports multi-user authentication with QR login and HTTP/stdio transports.82MIT
TDQS
Scored across 10 tools
Most tools target clearly distinct things (list_chats, get_media, get_topics, list_folders, search_messages). The trio get_messages, get_messages_by_date, and search_messages overlap in returning message lists, but descriptions distinguish them via pagination/cursor, day-scoping, and keyword semantics. get_chat_stats vs refresh_stats is also distinguishable (per-chat read vs global recompute).
Every tool follows a consistent snake_case verb_noun pattern (get_, list_, search_, refresh_). The verb choice matches the operation type throughout, with no style mixing.
Ten tools is well-scoped for a read/archive server covering chats, messages, media, topics, folders, and stats. Each tool earns its place with no obvious padding.
The surface covers the main read lifecycle for a Telegram archive: chats, paginated and date-scoped messages, search, media, pinned messages, topics, folders, and stats. Minor gaps like fetching a single message by id or listing archive accounts exist, but agents can work around them via get_messages.