telegram-notify runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 8 Nov 2026.
Send-only Telegram notifications to one fixed chat. No polling, no recipient override, 2 tools.
What the code does
We read the source, 6 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const API = 'https://api.telegram.org';
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add telegram-notify-mcp -e 'TELEGRAM_BOT_TOKEN=<TELEGRAM_BOT_TOKEN>' -e 'TELEGRAM_CHAT_ID=<TELEGRAM_CHAT_ID>' -- npx -y @yybd/telegram-notify-mcp{
"mcpServers": {
"telegram-notify-mcp": {
"command": "npx",
"args": [
"-y",
"@yybd/telegram-notify-mcp"
],
"env": {
"TELEGRAM_BOT_TOKEN": "<TELEGRAM_BOT_TOKEN>",
"TELEGRAM_CHAT_ID": "<TELEGRAM_CHAT_ID>"
}
}
}
}[mcp_servers.telegram-notify-mcp]
command = "npx"
args = ["-y", "@yybd/telegram-notify-mcp"]
env = { TELEGRAM_BOT_TOKEN = "<TELEGRAM_BOT_TOKEN>", TELEGRAM_CHAT_ID = "<TELEGRAM_CHAT_ID>" }{
"mcpServers": {
"telegram-notify-mcp": {
"command": "npx",
"args": [
"-y",
"@yybd/telegram-notify-mcp"
],
"env": {
"TELEGRAM_BOT_TOKEN": "<TELEGRAM_BOT_TOKEN>",
"TELEGRAM_CHAT_ID": "<TELEGRAM_CHAT_ID>"
}
}
}
}{
"servers": {
"telegram-notify-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@yybd/telegram-notify-mcp"
],
"env": {
"TELEGRAM_BOT_TOKEN": "<TELEGRAM_BOT_TOKEN>",
"TELEGRAM_CHAT_ID": "<TELEGRAM_CHAT_ID>"
}
}
}
}Put your own values in place of
<TELEGRAM_BOT_TOKEN> (Bot token from @BotFather (or run `telegram-notify-mcp setup` to save it to a file instead)), <TELEGRAM_CHAT_ID> (The one chat that receives every message; tools cannot change it).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
TELEGRAM_NOTIFY_FILES_DIR (Folder notify_file may send from. Unset means file sending is off).
Alternatives to telegram-notify
same job, measured the same waySend Telegram notifications from AI agents — text, photos, and documents.
Project memory, tasks and Telegram notifications for your coding agent. Chip account required.
Let your AI agent notify you by email, Slack, Discord, or webhook. One tool: send_notification.
Send email, push, Slack, Discord, Telegram and webhook notifications and manage templates with Ray.
Telegram MCP server: each AI client gets its own key, scoped to chosen chats. Read-only by default.
Send and verify one-time passcodes over SMS, WhatsApp and Telegram.
Find, price and book Twin Falls rooms with email verification. Sign at check-in; no online payment.
Local MCP tools for server-readable agent inboxes and sending to owner-approved recipients.
telegram-notify — questions
Answers built from our own checks of this server.