messages_sendTextLABSCO 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
Follow the published steps — tar -xzf telegram-mcp-*.tar.gz
USE CASES
01
Getting a message out without switching apps
Send the text to a chat by ID or username, replying to a specific message if you need to.
02
Asking someone a question and continuing when they answer
Send, then wait on that chat until a reply lands or the timeout runs out.
03
Finding what someone said about this weeks ago
Search messages rather than scrolling back through a chat.
04
Catching up after being away
Read recent messages across all chats in one call.
05
Summarising a long thread
Pull the chat's history and work from it.
06
Setting the emoji status on an account or channel
List what is available, check what is set, then change it.
11 tools
Listed in project docs. Your client may show a different list.
messages_getHistorymessages_searchmessages_getRecentwait_for_replystatus_getCurrentstatus_setEmojistatus_listAvailablestatus_listCollectiblesdialogs_listdialogs_getInfoBEFORE YOU INSTALL
What to know first
Tools you get
11 tools named in the project's documentation.
Requires
- API_ID in your environment
- API_HASH in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
Download the archive for your platform from https://github.com/zhigang1992/telegram-mcp/releases — telegram-mcp-darwin-arm64.tar.gz, telegram-mcp-darwin-x64.tar.gz, telegram-mcp-linux-x64.tar.gz or telegram-mcp-win-x64.exe.zip
TERMINAL
tar -xzf telegram-mcp-*.tar.gz
chmod +x telegram-mcpGet your Telegram API credentials (API ID and API hash) from https://my.telegram.org
TERMINAL
export API_ID=<YOUR_API_ID>
export API_HASH=<YOUR_API_HASH>
./telegram-mcpEnter your phone number and the verification code Telegram sends you. Note the Storage path it prints (for example /Users/<YOUR_USERNAME>/telegram-mcp/bot-data/session) — that is TELEGRAM_STORAGE_PATH in the client configuration.
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"telegram": {
"command": "<YOUR_PATH_TO_TELEGRAM_MCP>",
"env": {
"API_ID": "<YOUR_API_ID>",
"API_HASH": "<YOUR_API_HASH>",
"TELEGRAM_STORAGE_PATH": "<YOUR_ABSOLUTE_PATH>/from/initial/setup"
}
}
}
}
