MCP server
by qpd-v
Enable real-time, secure chat via telegram bots. Telegram Communicator supports asynchronous messaging & private telegra
Enables Claude to send messages, ask questions, and share files with users through Telegram bots. Supports real-time two-way communication during conversations.
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.
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.
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.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Telegram Communicator is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Useful MCP listing: Telegram Communicator is the kind of server we cite when onboarding engineers to host + tool permissions.
We wired Telegram Communicator into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Telegram Communicator is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
According to our notes, Telegram Communicator benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Strong directory entry: Telegram Communicator surfaces stars and publisher context so we could sanity-check maintenance before adopting.
I recommend Telegram Communicator for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Telegram Communicator reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We evaluated Telegram Communicator against two servers with overlapping tools; this profile had the clearer scope statement.
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
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.
npm install -g mcp-communicator-telegram
npx mcptelegram
To get your Telegram chat ID:
npx mcptelegram-chatid
git clone https://github.com/qpd-v/mcp-communicator-telegram.git
cd mcp-communicator-telegram
npm install
Create a Telegram bot:
/newbot and follow the instructionsGet your chat ID:
.env.example to .env.env file:
TELEGRAM_TOKEN=your_bot_token_here
npm run build
node build/get-chat-id.js
.env file:
TELEGRAM_TOKEN=your_bot_token_here
CHAT_ID=your_chat_id_here
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"
}
}
}
}
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?"
}
});
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!"
}
});
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"
}
});
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:
[project-name]-project.zip based on the directory nameBuild the project:
npm run build
Run in development mode:
npm run dev
Watch for changes:
npm run watch
Clean build directory:
npm run clean
ISC
qpd-v
0.2.1 # Major version bump for new features: notify_user, send_file, and zip_project tools
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.