Telegram Communicator▌

by qpd-v
Enable real-time, secure chat via telegram bots. Telegram Communicator supports asynchronous messaging & private telegra
Enables real-time communication with Telegram users via bots, supporting asynchronous messaging and secure chat interactions.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / AI assistants needing human approval or input
- / Automated workflows requiring user confirmation
- / Remote notifications and file sharing
- / Interactive debugging and troubleshooting
capabilities
- / Send messages and notifications via Telegram bot
- / Ask questions and wait for user responses
- / Share files through Telegram chat
- / Create and send project zip archives
- / Track message threads with reply-based system
what it does
Enables Claude to send messages, ask questions, and share files with users through Telegram bots. Supports real-time two-way communication during conversations.
about
Telegram Communicator is a community-built MCP server published by qpd-v that provides AI assistants with tools and capabilities via the Model Context Protocol. Enable real-time, secure chat via telegram bots. Telegram Communicator supports asynchronous messaging & private telegra It is categorized under communication.
how to install
You can install Telegram Communicator in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
Telegram Communicator is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
MCP Communicator (Telegram)
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.
Installation
Via npm (global)
npm install -g mcp-communicator-telegram
Via npx (on-demand)
npx mcptelegram
To get your Telegram chat ID:
npx mcptelegram-chatid
Features
- Ask questions to users through Telegram
- Send notifications to users (no response required)
- Send files to users via Telegram
- Create and send project zip files (respecting .gitignore)
- Receive responses asynchronously (waits indefinitely for response)
- Support for reply-based message tracking
- Secure chat ID validation
- Error handling and logging
Prerequisites
- Node.js (v14 or higher)
- A Telegram bot token (obtained from @BotFather)
- Your Telegram chat ID (can be obtained using the included utility)
Installation
- Clone the repository:
git clone https://github.com/qpd-v/mcp-communicator-telegram.git
cd mcp-communicator-telegram
- Install dependencies:
npm install
-
Create a Telegram bot:
- Open Telegram and search for @BotFather
- Send
/newbotand follow the instructions - Save the bot token you receive
-
Get your chat ID:
- Copy
.env.exampleto.env - Add your bot token to the
.envfile:TELEGRAM_TOKEN=your_bot_token_here - Run the chat ID utility:
npm run build node build/get-chat-id.js - Send any message to your bot
- Copy the chat ID that appears in the console
- Add the chat ID to your
.envfile:TELEGRAM_TOKEN=your_bot_token_here CHAT_ID=your_chat_id_here
- Copy
Configuration
Add the server to your MCP settings file (usually located at %APPDATA%\Code\User\globalStorageooveterinaryinc.roo-cline\settings\cline_mcp_settings.json on Windows):
{
"mcpServers": {
"mcp-communicator-telegram": {
"command": "node",
"args": ["path/to/mcp-communicator-telegram/build/index.js"],
"env": {
"TELEGRAM_TOKEN": "your_bot_token_here",
"CHAT_ID": "your_chat_id_here"
}
}
}
}
Available Tools
ask_user
Asks a question to the user via Telegram and waits for their response.
Input Schema:
{
"type": "object",
"properties": {
"question": {
"type": "string",
"description": "The question to ask the user"
}
},
"required": ["question"]
}
Example usage:
const response = await use_mcp_tool({
server_name: "mcp-communicator-telegram",
tool_name: "ask_user",
arguments: {
question: "What is your favorite color?"
}
});
notify_user
Sends a notification message to the user via Telegram (no response required).
Input Schema:
{
"type": "object",
"properties": {
"message": {
"type": "string",
"description": "The message to send to the user"
}
},
"required": ["message"]
}
Example usage:
await use_mcp_tool({
server_name: "mcp-communicator-telegram",
tool_name: "notify_user",
arguments: {
message: "Task completed successfully!"
}
});
send_file
Sends a file to the user via Telegram.
Input Schema:
{
"type": "object",
"properties": {
"filePath": {
"type": "string",
"description": "The path to the file to send"
}
},
"required": ["filePath"]
}
Example usage:
await use_mcp_tool({
server_name: "mcp-communicator-telegram",
tool_name: "send_file",
arguments: {
filePath: "path/to/file.txt"
}
});
zip_project
Creates a zip file of a project directory (respecting .gitignore patterns) and sends it to the user via Telegram.
Input Schema:
{
"type": "object",
"properties": {
"directory": {
"type": "string",
"description": "Directory to zip (defaults to current working directory)"
}
},
"required": []
}
Example usage with default directory (current working directory):
await use_mcp_tool({
server_name: "mcp-communicator-telegram",
tool_name: "zip_project",
arguments: {}
});
Example usage with specific directory:
await use_mcp_tool({
server_name: "mcp-communicator-telegram",
tool_name: "zip_project",
arguments: {
directory: "/path/to/your/project"
}
});
Features:
- Creates a zip file named
[project-name]-project.zipbased on the directory name - Can zip any specified directory or the current working directory
- Respects .gitignore patterns
- Maintains correct file paths in the archive
- Automatically cleans up the zip file after sending
- Handles files up to 2GB in size
Development
Build the project:
npm run build
Run in development mode:
npm run dev
Watch for changes:
npm run watch
Clean build directory:
npm run clean
Security
- The server only responds to messages from the configured chat ID
- Environment variables are used for sensitive configuration
- Message IDs are used to track question/answer pairs
- The bot ignores messages without proper context
License
ISC
Author
qpd-v
Version
0.2.1 # Major version bump for new features: notify_user, send_file, and zip_project tools
FAQ
- What is the Telegram Communicator MCP server?
- Telegram Communicator is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Telegram Communicator?
- This profile displays 43 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★43 reviews- ★★★★★Yuki Ramirez· Dec 24, 2024
Telegram Communicator is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
- ★★★★★Ganesh Mohane· Dec 20, 2024
Useful MCP listing: Telegram Communicator is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Anaya Garcia· Dec 20, 2024
We wired Telegram Communicator into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Shikha Mishra· Dec 16, 2024
Telegram Communicator is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Hiroshi Jain· Dec 16, 2024
According to our notes, Telegram Communicator benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Ishan Nasser· Dec 16, 2024
Strong directory entry: Telegram Communicator surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Evelyn Flores· Nov 15, 2024
I recommend Telegram Communicator for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Sakshi Patil· Nov 11, 2024
Telegram Communicator reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Li Jackson· Nov 11, 2024
We evaluated Telegram Communicator against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Yusuf Wang· Nov 7, 2024
Telegram Communicator has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
showing 1-10 of 43