ChatPush MCP Server
OfficialEnables sending Telegram messages through ChatPush via personal Telegram account (tdlib) or Telegram Bot, including text, files, bulk sends, scheduling, cascade routing, delivery status tracking, deletion of delivered messages, and webhook subscriptions for incoming messages and statuses.
Enables sending WhatsApp messages and files through ChatPush, including bulk mailings, scheduling, cascade routing with other channels, delivery status tracking, deletion of delivered messages, and linking WhatsApp accounts via QR/auth link.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ChatPush MCP Serversend WhatsApp to +7 916 555-01-23 saying order is ready"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ChatPush MCP Server
Official MCP server for ChatPush — send WhatsApp, Telegram, SMS, VK/OK and MAX messages, files and bulk mailings from AI agents.
It runs in two modes from the same codebase:
Mode | Transport | Who it is for | Token |
Remote | Streamable HTTP, hosted at | Yandex and other platforms that connect to a URL; users with no local Node.js | Each caller sends their own token in the |
Local | stdio, | Claude Desktop, Claude Code, Cursor, VS Code |
|
Tools
Tool | Description |
| Full account info: balance, dispatch routing, sender names, subscription, WhatsApp/Telegram session status |
| Balance, customer ID, dispatch routing channels and registered sender names |
| UTM tags used to track dispatches |
| Send a text via WhatsApp, Telegram (tdlib), Telegram Bot, SMS, VK/OK or MAX — with cascade, scheduling, priority and reply-to |
| Send the same message to many phone numbers at once |
| Send a document, image, audio or video from a local path, URL or base64 (up to 100 MB) |
| Status and details of a delivery, explained in plain words |
| Delete a delivered WhatsApp/Telegram message on all recipient devices |
| Country, operator and normalized format of a phone number |
| Subscribe your backend to incoming messages, delivery statuses and login events |
| Rename a contact in the ChatPush web messenger |
| Link to the QR page that connects WhatsApp or a personal Telegram account |
| Multi-account: create and inspect sub-clients, each with its own token |
Related MCP server: Twilio SMS MCP Server
Get a token
Sign up at chatpush.ru and copy the API token from the dashboard. To send through WhatsApp or Telegram, connect the messenger in the dashboard first — or call get_messenger_auth_link and scan the QR code.
Remote mode (hosted)
The hosted server exposes one MCP endpoint:
POST https://mcp.chatpush.ru/mcp
Authorization: Bearer <ChatPush API token>Transport: Streamable HTTP (MCP protocol 2025-06-18), JSON responses enabled.
Stateless: a fresh server instance per request, so it scales horizontally behind any proxy.
No credentials on the server: the token is read from the request header and used only for that request. Nothing is stored or logged.
GET /healthzreturns{"status":"ok",...}without a token, for load-balancer checks.
Connecting from a client that supports remote MCP servers:
{
"url": "https://mcp.chatpush.ru/mcp",
"headers": { "Authorization": "Bearer your_token_here" }
}Deployment
docker build -t chatpush-mcp-server .
docker run -p 3000:3000 -e CHATPUSH_ALLOWED_HOSTS=mcp.chatpush.ru chatpush-mcp-serverWithout Docker: npm ci && npm run build && npm run start:http.
Put TLS in front (nginx, Traefik, a cloud load balancer) and point mcp.chatpush.ru at it. The service needs no database, no disk and no secrets.
Variable | Default | Description |
|
| Port to listen on |
|
| Interface to bind |
|
| Path of the MCP endpoint |
|
| ChatPush API host |
| — | Comma-separated |
|
| Value for |
|
|
|
Local mode (stdio)
Requires Node.js 20 or newer.
Claude Desktop
Settings → Developer → Edit Config (claude_desktop_config.json):
{
"mcpServers": {
"chatpush": {
"command": "npx",
"args": ["-y", "chatpush-mcp-server"],
"env": { "CHATPUSH_TOKEN": "your_token_here" }
}
}
}Claude Code
claude mcp add chatpush --env CHATPUSH_TOKEN=your_token_here -- npx -y chatpush-mcp-serverCursor
Add the same mcpServers block to ~/.cursor/mcp.json.
VS Code
.vscode/mcp.json — VS Code asks for the token and keeps it out of the file:
{
"inputs": [
{ "type": "promptString", "id": "chatpush_token", "description": "ChatPush token", "password": true }
],
"servers": {
"chatpush": {
"type": "stdio",
"command": "npx",
"args": ["-y", "chatpush-mcp-server"],
"env": { "CHATPUSH_TOKEN": "${input:chatpush_token}" }
}
}
}Channels
dispatch_routing is an ordered list of channels. ChatPush tries them one by one and moves to the next only if delivery through the previous one fails. Without it, the default routing from your dashboard is used.
Value | Channel | Recipient |
|
| |
| Personal Telegram account |
|
| Telegram Bot |
|
| SMS |
|
| VK / OK notifications |
|
| MAX messenger |
|
Usage examples
Say | Tool |
"Send a WhatsApp message to +7 999 123-45-67: your order has shipped." |
|
"Try WhatsApp first, then SMS: your code is 4821." |
|
"Remind 79991234567 tomorrow at 09:00 UTC about the appointment." |
|
"Send invoice.pdf to 79991234567." |
|
"Was message 94396942 delivered?" |
|
"Connect my WhatsApp." |
|
"Create a sub-client called Acme." |
|
"Rename the contact 79991234567 to Ivan from Acme." |
|
Behaviour
Parameters go in the URL query string, as the ChatPush API expects;
send_fileuploads the file asmultipart/form-data.Incompatible parameters (a Telegram
usernamewithout thetdlibchannel,scheduled_atin the past) are rejected before any request is sent.HTTP 429 is retried up to 3 times with exponential backoff, honouring
Retry-After; 5xx twice — except for requests that send messages, so nothing is sent twice.Requests time out after 30 seconds.
Errors come back as readable tool errors, e.g.
Invalid ChatPush token. Check your CHATPUSH_TOKEN.All logs go to stderr; stdout carries the MCP protocol in stdio mode.
Development
npm install
cp .env.example .env # put your token in .env
npm run build
npm run dev # stdio
npm run dev:http # remote, http://localhost:3000/mcpScript | What it does |
| Versions in sync across |
| Build the Claude Desktop extension into |
| Open the MCP Inspector against the local server |
License
This server cannot be deployed
Maintenance
Related MCP Connectors
Email, WhatsApp and Telegram for AI agents: send, campaigns, automations, contacts, agent inboxes.
Send and schedule SMS and WhatsApp messages, manage contacts and templates, and track delivery.
- WSENDEROAuthio.wsender
Manage WhatsApp, Telegram and MAX mailings: audiences, drafts, moderation and sending.
WhatsApp for AI agents — your own number or the official Cloud API: messages, media, templates.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to send WhatsApp messages, templates, and retrieve media through the WhatsApp Cloud API. Provides webhook handling and seamless integration with Meta's WhatsApp Business platform.23-
- AlicenseCqualityDmaintenanceEnables AI agents to send, receive, schedule, and manage SMS and MMS messages using the Twilio Programmable Messaging API. It provides comprehensive tools for handling bulk messaging, conversation threads, and real-time inbox monitoring through a secure, production-grade architecture.161MIT

SendAPI MCP Serverofficial
AlicenseAqualityDmaintenanceEnables any MCP-compatible AI agent to send WhatsApp messages, SMS, OTP codes, and email through a single REST API.18MIT
jetapi-mcp-serverofficial
AlicenseAqualityAmaintenanceOfficial JetAPI MCP server for sending WhatsApp, Telegram (personal account or bot), SMS, VK/OK and MAX messages and files from AI agents. Supports channel cascades, scheduling, bulk mailings, delivery status tracking, phone number lookup and webhook management.1458 npmMIT