A dead-simple MCP server with one job: send AI agent progress back to you on Telegram — text, images, or files.
Telegram Notify MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A dead-simple MCP server with one job: send AI agent progress back to you on Telegram — text, images, or files.
Once Telegram Notify MCP is connected, these are the calls the assistant has available:
send_message — The send_message tool exposed by this serversend_photo — The send_photo tool exposed by this serversend_document — The send_document tool exposed by this serverThe server ships on npm as @parthj/telegram-notify-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.
You will need 2 environment variables: TELEGRAM_BOT_TOKEN, TELEGRAM_USERNAME. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
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 Notify MCP's toolset — send_message, send_photo, send_document — is a fair guide to whether it matches your workflow. It is maintained by parthjadhav; 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_photo | The send_photo tool exposed by this server. |
| send_document | The send_document tool exposed by this server. |
{
"mcpServers": {
"telegram-notify": {
"command": "npx",
"args": ["-y", "@parthj/telegram-notify-mcp"],
"env": {
"TELEGRAM_BOT_TOKEN": "your-value",
"TELEGRAM_USERNAME": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| TELEGRAM_BOT_TOKEN | Credential the server authenticates with. | Yes |
| TELEGRAM_USERNAME | Configuration value read at startup. | Optional |
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.