telegram-archive-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELEGRAM_ARCHIVE_URL | Yes | Telegram Archive URL |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_chat_statsC | Get statistics for a specific Telegram chat |
| get_messagesC | Get messages from a Telegram chat with pagination |
| get_messages_by_dateB | Get messages from a Telegram chat on a specific date |
| get_pinned_messagesC | Get pinned messages from a Telegram chat |
| get_topicsC | Get topics (forum threads) from a Telegram chat |
| refresh_statsA | Force recalculation of global telegram-archive statistics |
| search_messagesC | Search messages in a Telegram chat by keyword |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Chat folders | List of Telegram chat folders |
| Chat list | List of all archived chats with basic info |
| Global backup statistics | Chat count, message count, media count, total size |
| Health check | Health status of the telegram-archive instance |
TDQS
Scored across 7 tools
The message retrieval tools (get_messages, get_messages_by_date, get_pinned_messages, search_messages) have distinct filtering purposes that agents can distinguish, though there's slight overlap between general pagination and date-specific retrieval. get_chat_stats and refresh_stats are clearly differentiated by scope (specific chat vs global).
Most tools follow a consistent snake_case verb_noun pattern with 'get_' prefix (get_messages, get_topics), but refresh_stats breaks this convention by using 'refresh' instead of 'get' or 'update'. search_messages appropriately uses 'search' to distinguish from retrieval operations.
Seven tools is well-suited for a focused archive access server. Each tool serves a distinct retrieval pattern (pagination, date filter, search, pinned, topics, stats) without bloat. The count supports the core read-only archive workflow effectively.
The surface covers essential read operations for message archives including filtering, search, and statistics. Minor gaps include the absence of a list_chats discovery tool (assuming chat IDs are known) and no media/file download capability, though these may be out of scope for a text-focused archive.