An MCP server that enables communication with users through Telegram. This server provides a tool to ask questions to users and receive their
An MCP server that enables communication with users through Telegram. This server provides a tool to ask questions to users and receive their responses via a Telegram bot. The mcp communicator (telegram) mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 4 defined tools rather than through you.
An MCP server that enables communication with users through Telegram. This server provides tools to interact with users via a Telegram bot, including asking questions, sending notifications, sharing files, and creating project archives.
The server ships on npm as mcptelegram, 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.
Everything the assistant can do here goes through one of these:
ask_user — Asks a question to the user via Telegram and waits for their responsenotify_user — Sends a notification message to the user via Telegram (no response required)send_file — Input Schema: json { "type": "object", "properties": { "filePath": { "type": "string", "description": "The path to the file to send" } }, "required"zip_project — Creates a zip file of a project directory (respecting .gitignore patterns) and sends it to the user via TelegramYou will need 2 environment variables: TELEGRAM_TOKEN, CHAT_ID. 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.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Communicator (Telegram)'s toolset — ask_user, notify_user, send_file and 1 more — is a fair guide to whether it matches your workflow. It is maintained by qpd-v; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Communicator (Telegram)'s own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| ask_user | Asks a question to the user via Telegram and waits for their response. |
| notify_user | Sends a notification message to the user via Telegram (no response required). |
| send_file | Input Schema: json { "type": "object", "properties": { "filePath": { "type": "string", "description": "The path to the file to send" } }, "required": ["filePath"] } |
| zip_project | Creates a zip file of a project directory (respecting .gitignore patterns) and sends it to the user via Telegram. |
{
"mcpServers": {
"communicator-telegram": {
"command": "npx",
"args": ["-y", "mcptelegram"],
"env": {
"TELEGRAM_TOKEN": "your-value",
"CHAT_ID": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| TELEGRAM_TOKEN | Credential the server authenticates with. | Yes |
| CHAT_ID | 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.