ChatPush MCP server
Commit Nov 2, 2026Enables AI agents to send WhatsApp, Telegram, SMS, VK/OK, and MAX messages, files, and bulk mailings.
Also known as ChatPush/mcp-chatpush
- Stars
- 0
- Tools
- 11
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 2, 2026
- License
- MIT
What is ChatPush MCP?
ChatPush enables AI agents to send WhatsApp, Telegram, SMS, VK/OK, and MAX messages, files, and bulk mailings. It exposes 11 tools, such as get_account, get_balance, get_utm_tags.
Summary generated from the project's README
About ChatPush MCP server
Sending messages across multiple communication channels from within an AI agent is what mcp-chatpush enables. Developers can use this server to dispatch text, files, and bulk mailings via WhatsApp, Telegram, SMS, VK/OK, and MAX. It supports complex messaging workflows including scheduled delivery, priority settings, and cascading through different channels if the first attempt fails.
Users can run this server in two distinct ways depending on their environment. For local development with Claude Desktop, Claude Code, Cursor, or VS Code, it operates via stdio using a CHATPUSH_TOKEN. For platforms like Yandex that require a URL connection, it provides a remote mode using streamable HTTP. In the remote setup, callers provide their own token in the Authorization header, ensuring the hosted instance remains stateless and secure.
The toolset includes functions to manage account balances, check delivery statuses, and handle file transfers up to 100 MB. It also allows for managing messenger connections through QR code links and organizing multi-account setups with sub-customers.
What you can do with it
- 1Automated multi-channel notificationsInstruct an AI to send a message via WhatsApp and fallback to SMS if it fails.
- 2Scheduled appointment remindersAsk the agent to schedule a specific message for a future date and time.
- 3File distribution via chatHave the AI send a document or image to a recipient using a local path or URL.
- 4Messenger account connectionGenerate a link to connect a personal WhatsApp or Telegram account via QR code.
- 5Bulk messaging campaignsCommand the agent to send a single message to a large list of phone numbers.
Written from the project's README. Every use case is checked against a quote from it.
ChatPush MCP tools 11
Detected from the READMEget_accountget_balanceget_utm_tagssend_messagesend_bulksend_fileget_delivery_statusdelete_deliveryget_phone_infoset_chat_client_nameget_messenger_auth_link
| get_account | — | |
| get_balance | — | |
| get_utm_tags | — | |
| send_message | — | |
| send_bulk | — | |
| send_file | — | |
| get_delivery_status | — | |
| delete_delivery | — | |
| get_phone_info | — | |
| set_chat_client_name | — | |
| get_messenger_auth_link | — |
Configuration
CHATPUSH_TOKEN
| Name | Description | |
|---|---|---|
| CHATPUSH_TOKEN | — |
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablechatpush/mcp-chatpush is public and reachablegithub.com/chatpush/mcp-chatpush ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-02github.com/chatpush/mcp-chatpush ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model11 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubChatPush 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 https://mcp.chatpush.ru/mcp |
Yandex and other platforms that connect to a URL; users with no local Node.js | Each caller sends their own token in the Authorization header |
| Local | stdio, npx -y chatpush-mcp-server |
Claude Desktop, Claude Code, Cursor, VS Code | CHATPUSH_TOKEN in the client config |
Tools
| Tool | Description |
|---|---|
get_account |
Full account info: balance, dispatch routing, sender names, subscription, WhatsApp/Telegram session status |
get_balance |
Balance, customer ID, dispatch routing channels and registered sender names |
get_utm_tags |
UTM tags used to track dispatches |
send_message |
Send a text via WhatsApp, Telegram (tdlib), Telegram Bot, SMS, VK/OK or MAX — with cascade, scheduling, priority and reply-to |
send_bulk |
Send the same message to many phone numbers at once |
send_file |
Send a document, image, audio or video from a local path, URL or base64 (up to 100 MB) |
get_delivery_status |
Status and details of a delivery, explained in plain words |
delete_delivery |
Delete a delivered WhatsApp/Telegram message on all recipient devices |
get_phone_info |
Country, operator and normalized format of a phone number |
create_webhook · get_webhook · list_webhooks · update_webhook · delete_webhook |
Subscribe your backend to incoming messages, delivery statuses and login events |
set_chat_client_name |
Rename a contact in the ChatPush web messenger |
get_messenger_auth_link |
Link to the QR page that connects WhatsApp or a personal Telegram account |
create_sub_customer · list_sub_customers · get_sub_customer |
Multi-account: create and inspect sub-clients, each with its own token |
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-server
Without 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 |
3000 |
Port to listen on |
HOST |
0.0.0.0 |
Interface to bind |
CHATPUSH_MCP_PATH |
/mcp |
Path of the MCP endpoint |
CHATPUSH_BASE_URL |
https://api.chatpush.ru |
ChatPush API host |
CHATPUSH_ALLOWED_HOSTS |
— | Comma-separated Host values to accept, e.g. mcp.chatpush.ru. Set it in production: it blocks DNS-rebinding attacks |
CHATPUSH_ALLOWED_ORIGIN |
* |
Value for Access-Control-Allow-Origin |
CHATPUSH_DEBUG |
0 |
1 logs every request to stderr |
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-server
Cursor
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 |
|---|---|---|
whatsapp |
phone or whatsapp_lid |
|
tdlib |
Personal Telegram account | phone, username or tdlib_user_id (negative ID = group chat) |
telegram |
Telegram Bot | phone |
sms |
SMS | phone |
notify |
VK / OK notifications | phone |
max |
MAX messenger | phone |
Usage examples
| Say | Tool |
|---|---|
| "Send a WhatsApp message to +7 999 123-45-67: your order has shipped." | send_message |
| "Try WhatsApp first, then SMS: your code is 4821." | send_message (cascade) |
| "Remind 79991234567 tomorrow at 09:00 UTC about the appointment." | send_message (scheduled) |
| "Send invoice.pdf to 79991234567." | send_file |
| "Was message 94396942 delivered?" | get_delivery_status |
| "Connect my WhatsApp." | get_messenger_auth_link |
| "Create a sub-client called Acme." | create_sub_customer |
| "Rename the contact 79991234567 to Ivan from Acme." | set_chat_client_name |
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/mcp
| Script | What it does |
|---|---|
npm run check |
Versions in sync across package.json / server.json / manifest.json and all 19 tools exposed |
npm run build:mcpb |
Build the Claude Desktop extension into build/chatpush-mcp-server.mcpb |
npm run inspector |
Open the MCP Inspector against the local server |
License
ChatPush MCP questions
What tools does ChatPush MCP provide?
It exposes 11 tools, including get_account, get_balance, get_utm_tags, send_message, send_bulk.
How do I connect my WhatsApp or Telegram account?
You can connect your messenger in the ChatPush dashboard or call the get_messenger_auth_link tool to scan a QR code.
Can I send files through the ChatPush MCP server?
Yes, you can send documents, images, audio, or video files up to 100 MB from a local path, URL, or base64.
What happens if a message fails to deliver via one channel?
You can use cascade routing to try multiple channels in order; the server moves to the next channel only if delivery through the previous one fails.