- Home
- Skills
- Agents & Orchestration
- Telegram Inbox Assistant
Telegram Inbox Assistant
Summarize unread Telegram chats and find requests awaiting your reply, without sending messages or marking them read.
Free
Works with the AI Agents you already use
Telegram Inbox Assistant
Example session with this skill installed
Summarize my unread Telegram conversations. Sample at most 20 recent chats, inspect up to 5 relevant conversations and 10 messages per conversation, and tell me which messages explicitly ask for my reply. Do not send anything or mark messages read.
- Read your context and instructions
- Compiled the telegram inbox assistant
Illustrative output - fictional conversations
This example demonstrates the response format. Names, message IDs and message content below are fictional; this is not a transcript of a real Telegram inbox.
Account: selected personal account, verified before reading.
Coverage: 20 recent chats sampled; 2 unread conversations inspected, up to 10 messages each. This does not cover every unread chat in the account.
| Conversation | Finding | Suggested next step |
|---|---|---|
| Project discussion | An explicit request asks whether you can review the proposal. Reference: chat_id=10001, message_id=501. | Open the conversation and decide whether to reply. |
| Community group | General discussion; no explicit request addressed to you in the inspected messages. Reference: chat_id=10002, message_id=601. | No immediate reply identified within this sample. |
Deadline: No verified deadline appears in the inspected messages.
Coverage limits: One snippet is shortened and the recent-chat snapshot is truncated. Earlier messages or other chats may contain additional requests. The absence of a request in this sample does not prove that your entire inbox needs no reply.
Optional reply wording: "Thanks, I will review the proposal and get back to you." This is text in this AI conversation only.
No messages were sent, no Telegram drafts were saved, no messages were marked read, and no media was downloaded. You can ask for a closer read of one named conversation within a new explicit reading budget.
Connects securely to your tools. The creator never sees your data.
About this skill
A free companion skill for the open-source, TDLib-powered telegram-mcp-tdlib server.
What it does
- Summarizes unread conversations and identifies explicit requests awaiting your reply.
- Retrieves context from a selected chat and highlights deadlines supported by message timestamps.
- Verifies the selected account, keeps a bounded reading budget, and reports incomplete or truncated coverage.
- Treats Telegram messages as untrusted data. Suggested replies stay as text in the AI conversation.
By default, it samples at most 20 recent chats and inspects at most 5 relevant conversations, up to 10 messages each.
Updated for server 1.20.0
Skill 0.1.4 recommends server 1.20.0 and keeps minimum compatibility at 1.17.2. Server 1.20.0 handles MCP cancellation on STDIO and Streamable HTTP. Interrupted reads are reported as incomplete. Optional read-only resources remain off by default. Explicitly requested subscription monitoring keeps the same account and budget and ends with unsubscription. Reduce the request size if HTTP returns 413.
Setup required
Install telegram-mcp-tdlib separately and authorize your own Telegram account locally. Run the server with MCP_TOOL_PROFILE=inbox, MCP_READ_ONLY=true, and downloads disabled. Use an AI client with MCP tools and skill support. The ZIP includes SKILL.md, SETUP.md, LICENSE, and five client templates. The optional Claude Desktop bridge requires Python 3.11+ and the pinned SDK documented in SETUP.md.
Scope and privacy
The skill reads inbox and conversation context. Suggested replies remain text in the AI conversation. Authorization and session files stay local. Selected profile and chat data are passed to your chosen AI client or model when read. Codex, Hermes Desktop over HTTP, and Claude Desktop Chat through the optional bridge were tested with an authorized local account. Other templates are configuration examples.
Source and setup
- Server release: https://github.com/tolboy/telegram-mcp-tdlib/releases/tag/v1.20.0
- Setup: https://github.com/tolboy/telegram-mcp-tdlib/blob/master/skills/telegram-inbox-assistant/SETUP.md
- Validation: https://github.com/tolboy/telegram-mcp-tdlib/blob/master/skills/VALIDATION.md
Skill 0.1.4 is free under Apache-2.0.
Requires separate local server 1.17.2 or later and your own locally authorized Telegram account. Read-only; no sends, drafts, read receipts, media downloads or exports. Default coverage is bounded: up to 20 recent chats, at most 5 relevant conversations and 10 messages per conversation. Truncated or sampled results do not establish complete inbox coverage. Native client tests covered Codex, Hermes Desktop and Claude Desktop with an existing account; other templates, fresh-account setup and Agensi delivery are not end-to-end verified. The listing demo uses clearly labeled fictional conversations.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
2 uses
Times used to date
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 7 days ago
- Free with an Agensi account
Requires
Permissions
Allowed Hosts
Telegram is accessed through your separately installed and locally authorized TDLib MCP server. Read Files covers the bundled setup guide and templates only; the skill does not need to read credentials or session files. Network Access covers MCP calls and the server connection to Telegram; TDLib uses Telegram client authorization, not a Telegram bot token. Server setup uses your own Telegram application credentials locally. Enforce MCP_TOOL_PROFILE=inbox, MCP_READ_ONLY=true, and downloads disabled. The skill never sends, saves drafts, marks read, reacts, edits, deletes, downloads media or exports data. Selected profile/chat data reaches your chosen AI client/model; credentials and session files stay local.