send_document
Send a document or file to the configured Telegram user. Accepts a URL or local file path.
LABSCO SUMMARY
A long-running agent gets a way to reach you that does not depend on the console still being open.
The recipient is fixed by configuration, so nothing here can address an arbitrary user — where a message goes is decided at install time rather than per call. All three tools take a parse mode, which is the difference between a readable status update and a wall of characters. Photos and documents accept a local path as readily as a URL, so a file produced during a run can go out without being hosted somewhere first.
What it is
A one-way notification channel to a single Telegram user set at configuration time.
What you get
- A text message with the parse mode you choose.
- A photo from a URL or a local file path, with a caption.
- A document or file from a URL or a local path, with a caption.
Requirements
A Telegram bot with its token in TELEGRAM_BOT_TOKEN, and the recipient's username in TELEGRAM_USERNAME.
Setup effort
One command plus a key — npx @parthj/telegram-notify-mcp, then supply credentials
USE CASES
01
Being told when a long run has finished
A completion notice reaches a phone rather than a terminal nobody is watching, formatted so the important line stands out.
02
Getting the file itself rather than word of it
A chart or a report produced during the run travels straight out from its local path, with a caption explaining what it is.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
send_message
Send a text message to the configured Telegram user
send_photo
Send a photo to the configured Telegram user. Accepts a URL or local file path.
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected. All three send outward (text, image or file); none read messages or manage chats. Nothing works until you send /start to your own bot.
Requires
- npx on PATH
- TELEGRAM_BOT_TOKEN in your environment
- TELEGRAM_USERNAME in your environment
Where it runs
All 4 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @parthj/telegram-notify-mcpMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add telegram -e TELEGRAM_BOT_TOKEN=<YOUR_TELEGRAM_BOT_TOKEN> -e TELEGRAM_USERNAME=<YOUR_TELEGRAM_USERNAME> -- npx @parthj/telegram-notify-mcpClaude Desktop, Cursor, Windsurf
JSON
{
"mcpServers": {
"telegram": {
"command": "npx",
"args": [
"-y",
"@parthj/telegram-notify-mcp"
],
"env": {
"TELEGRAM_BOT_TOKEN": "<YOUR_TELEGRAM_BOT_TOKEN>",
"TELEGRAM_USERNAME": "<YOUR_TELEGRAM_USERNAME>"
}
}
}
}
