SendPulse chatbots MCP server
MCP Server for SendPulse Chatbots
An MCP server for SendPulse chatbots: account info, dialogs and sending messages across WhatsApp, Telegram, Instagram and other channels
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Can send messages to messenger contacts on the bot's behalf
- The x-sp-id and x-sp-secret headers or the OAuth token grant access to all of the account's bots
Install
Manual install
npm install && npm run build && npm startInstalls, builds and starts the local HTTP server on port 3000.
This is third-party code. Review the repository files before installing.
What it does
The server runs as an Express HTTP service and gives an agent three general tools: SendPulse account info with plan and counters, a list of connected chatbots, and a list of dialogs across all channels with pagination and sorting. A separate universal send_message tool sends a text message to a contact on a chosen channel, supporting WhatsApp, Telegram, Instagram, Messenger, LiveChat and Viber. Authentication is flexible: you can pass an application ID and secret in headers and the server obtains and caches an OAuth token itself, or pass a ready token directly via the Authorization header or the initialize request body.
Who it is for. For people running a SendPulse chatbot across multiple messengers who want to read dialogs and send messages through an agent.
Good fit when
- You want a summary of dialogs across all connected bot channels in one place
- You want to send a message to a contact on a specific channel without opening the SendPulse dashboard
- You want SendPulse account and plan information
Not a fit when
- You do not have a SendPulse account with connected chatbots
- You want to test the server locally with an external AI client: this needs a public tunnel like ngrok, which exposes the server to the internet
Example request
Show recent dialogs in my SendPulse chatbots and send a reply to a contact on WhatsAppLimitations
The project has a single author, is very small, with no ready npm package, and installs from source by building the TypeScript. Only sending a plain text message is available; there is no support for templates, attachments or buttons. The README's ngrok test setup exposes the local server to the internet with no default authorization.
How to disable. Stop the Node.js server process and remove the entry from your MCP client config.
MCP
- Transport
- http
- Authentication
- OAuth
Security check
- Can send messages to messenger contacts on the bot's behalf
- The x-sp-id and x-sp-secret headers or the OAuth token grant access to all of the account's bots
README in short
The English README describes three general tools and the universal send_message tool with a channel parameter, two authentication methods, installation and building on Node.js and Express, running the local HTTP server, and a test setup exposing it via ngrok for external AI clients like the OpenAI sandbox.
FAQ
Which channels does message sending support?
WhatsApp, Telegram, Instagram, Messenger, LiveChat and Viber, chosen via the channel parameter of the send_message tool.
Can I pass a ready OAuth token instead of an ID and secret?
Yes, a token can be passed directly via the Authorization header or in the initialize request body.
Related
Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent
Yandex Kit skills for store management
kit-skills
Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex
YouGile MCP by Indalo
YouGile MCP
Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit
Bitrix24 portal MCP server
MCP-сервер портала Битрикс24
Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail