MCP server for sending notifications via Telegram Bot API
Connect Telegram Notifier MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for sending notifications via Telegram Bot API. The telegram notifier mcp mcp server is what makes that connection.
An MCP server that lets an LLM send messages and files to a user via a Telegram bot, and read incoming messages. No external HTTP or Telegram libraries — just the native fetch API and the official MCP SDK.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
send_message — The send_message tool exposed by this serversend_document — The send_document tool exposed by this serversend_photo — The send_photo tool exposed by this serversend_video — The send_video tool exposed by this serversend_audio — The send_audio tool exposed by this serverget_updates — Check for new messages sent to the bot. Only returns messages received since the last checkConfiguration is passed through the environment: TELEGRAM_BOT_TOKEN, TELEGRAM_CHAT_ID, YOUR_BOT_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as telegram-notifier-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Telegram Notifier MCP's toolset — send_message, send_document, send_photo and 3 more — is a fair guide to whether it matches your workflow. It is maintained by adeshatole; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| send_message | The send_message tool exposed by this server. |
| send_document | The send_document tool exposed by this server. |
| send_photo | The send_photo tool exposed by this server. |
| send_video | The send_video tool exposed by this server. |
| send_audio | The send_audio tool exposed by this server. |
| get_updates | Check for new messages sent to the bot. Only returns messages received since the last check. |
{
"mcpServers": {
"telegram-notifier": {
"command": "npx",
"args": ["telegram-notifier-mcp"],
"env": {
"TELEGRAM_BOT_TOKEN": "your-bot-token-here",
"TELEGRAM_CHAT_ID": "your-chat-id-here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| TELEGRAM_BOT_TOKEN | Credential the server authenticates with. | Yes |
| TELEGRAM_CHAT_ID | Configuration value read at startup. | Optional |
| YOUR_BOT_TOKEN | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.