Summary
A Telegram account an agent can hold a conversation on.
The wait-for-reply tool is what separates this from a notifier. An agent can send a message, stop, and resume when the human answers, instead of polling or giving up mid-task.
What it is
An MCP server for Telegram built on mtcute. It connects as your account rather than as a bot, so it reaches the same chats, dialogs and history you see in the app.
What you get
- Text messages sent to any chat, optionally as a reply to a specific message
- Message history read from a chat
- Recent messages across all chats
- Search across messages
- A wait that blocks until a reply lands in a chat, with a timeout
- Emoji status read, listed and set for accounts and channels
Requirements
Telegram API credentials — an app ID and its hash — registered at my.telegram.org, plus a one-time interactive login by phone number and verification code. The absolute session path printed during that setup has to be handed back to the server through its environment, or it starts without the authenticated session.
Setup effort
One command plus a key — npx -y @zhigang1992/telegram-mcp, then supply credentials