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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_chat_statsC | Get statistics for a specific Telegram chat |
| get_mediaA | Get the photo or file attached to one message. A JPEG, PNG, WebP or GIF image comes back as an image you can look at, scaled to at most 1568 pixels on its longest side, after a JSON text block with the message's message_id, date, sender, text (the caption) and reply_to_msg_id, and the file's media_key, kind, file_name, mime_type, size_bytes, image_returned, width, height and scaled. Any other file returns only that JSON text block, with a note saying why the file is not included. |
| get_messagesA | Get messages from a Telegram chat, newest first. Page with offset, or with the keyset cursor: pass the date and id of the last message you received as before_date and before_id to get the older ones (constant time on huge chats). after_id returns messages newer than an id. Dates are naive UTC. |
| get_messages_by_dateA | Get every message of a Telegram chat sent on one calendar day, oldest first. The day is taken in the given timezone (default UTC); the archive stores dates in UTC. Walks the chat with the keyset cursor, so it is cheap even on chats with hundreds of thousands of messages. |
| get_pinned_messagesC | Get pinned messages from a Telegram chat |
| get_topicsC | Get topics (forum threads) from a Telegram chat |
| list_chatsA | List archived Telegram chats, most recent first. Use this first: each chat's ref is the chat_id the other tools take. Each row also carries id (the numeric Telegram chat id), type, accounts (the archive account ids holding the chat), and its title or name. The answer is {chats, total, limit, offset, has_more}; page with offset while has_more is true. |
| list_foldersA | List all Telegram chat folders |
| 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 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.