tgread
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TGREAD_LOG | No | Set to DEBUG to enable debug logging on stderr while keeping stdout pure MCP protocol. | |
| TGREAD_TOOLS | No | Comma-separated allowlist of tools to expose to the agent. If unset, all fifteen tools are available. Unknown names cause a fatal error at startup. | |
| TGREAD_STATE_DIR | No | Directory for state files (config.env, tgread.session, etc.). Defaults to ~/.local/state/tgread. | ~/.local/state/tgread |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_chatsA | List the Telegram chats, channels and groups this account can see, newest activity first. Use it to find the id or @username to pass to the other tools. Read-only. |
| read_chatA | Read recent messages from one channel, group or conversation, returned oldest-first. Accepts a @username, a t.me link, or a numeric id from list_chats. Read-only: reading here does not mark anything as read. |
| search_messagesA | Full-text search over message history. With |
| chat_infoA | Metadata for one chat: kind, member count, description, verification flags. Useful for judging whether a channel is what it claims to be. Read-only. |
| whoamiA | The Telegram account this server is signed in as. Read-only. |
| search_public_chatsA | Search Telegram's public directory by name — finds channels and groups the account has never joined. Results are split into ones already known to this account and strangers. Read-only; does not join anything. |
| list_foldersA | The account's chat folders (Telegram 'dialog filters') and their sizes. Read-only. |
| list_contactsA | The account's saved contacts, optionally filtered by name. Read-only. |
| get_messagesA | Fetch specific messages by id, or the conversation around one — use |
| read_threadA | The replies under one post — a channel item's comment section, or a reply chain in a group. Only posts with a linked discussion group have one. Read-only. |
| list_pinnedB | Pinned messages in a chat — usually its rules, links or announcements. Read-only. |
| list_mediaA | Messages in a chat filtered by attachment kind, using Telegram's own server-side index. Returns metadata and captions only — there is no download tool. Read-only. |
| list_membersA | Participants of a group or channel, searchable, with their roles. Broadcast channels hide this from non-admins — |
| get_reactionsA | Who reacted to a message, and with which emoji. Read-only — it adds no reaction. |
| common_chatsA | Groups and channels the account shares with a given user. Read-only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Each tool targets a distinct read operation or resource: chat metadata, message lists, specific message fetches, threads, media, members, reactions, contacts, folders, and shared chats. Even the message-related tools (read_chat, get_messages, read_thread) are clearly separated by scope and purpose.
The vast majority of tools follow a clear verb_noun pattern (list_*, get_*, read_*, search_*), with three exceptions: chat_info, whoami, and common_chats. These deviations are minor and still readable, but they prevent a perfect consistency score.
At 15 tools, the server sits at the upper edge of the well-scoped range, and every tool earns its place for a read-only Telegram interface. The count is substantial but not bloated, with each tool covering a distinct aspect of the domain.
The read surface is remarkably comprehensive: chat enumeration, message retrieval, search, threads, pinned messages, media, members, reactions, contacts, folders, public directory search, and account info are all present. The only excluded capability, media downloading, is explicitly documented as out of scope, so there are no hidden gaps.