tg-recall-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TG_RECALL_HOME | No | Override the home directory for configuration and data. Precedence: --home, TG_RECALL_HOME, then system defaults. | |
| TG_RECALL_PROFILE | No | Override the active profile. Precedence: --profile, TG_RECALL_PROFILE, configured active profile, then default. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Find messages in the owner's allowed Telegram chats: hits ('>') with sender, time, context around them and tg:// citations, in one call. |
| readA | Read messages in order. No args: new since your last read (first: last 24h), newest per chat. chats: latest. since/until: a whole period. refs: around citations (before/after, full=true). |
| statsB | Counts instead of messages: volume per day/week/month (with query: hits per period), top senders, topics, chats. For when/how much/who questions over long periods. |
| exportB | Write a whole period/topic (full text, read's format) to a local file and return its path, size and token estimate. For bulk analysis: read the file with your own file tools in chunks. |
| chatsC | List allowed chats: id, title, message count, last activity, sync age. |
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 5 tools
Each tool has a largely distinct purpose: search queries messages, read retrieves messages in order, stats aggregates counts, export writes to a file, and chats lists available chats. The only mild overlap is that search and read both return message content, and export can cover similar bulk-retrieval ground as read, but the descriptions make the intended use cases clear.
All five names are single lowercase words with no separators, which is a consistent and predictable style. However, they mix verbs (search, read, export) and nouns (stats, chats) rather than following a single verb_noun or uniform category convention, which is a minor deviation.
Five tools is well within the appropriate 3-15 range for a Telegram message-recall server. Each tool maps to a distinct capability (query, ordered read, aggregation, bulk export, chat listing) and none feels redundant.
The read-only recall domain is well covered: search for targeted retrieval, read for chronological access, stats for aggregation, export for bulk analysis, and chats for scope discovery. A minor gap is the lack of an explicit sync/refresh or per-message lookup tool, though chats' sync age and read's since/until partially mitigate this.