ChatbotX MCP
ChatbotX MCP server: contacts, conversations, flows, broadcasts and automation in WhatsApp, Instagram and other channels
- 1,111 ★ on the repository
- Last commit
Broad access
Why this level
- The agent can send messages and broadcasts to customers on behalf of the business, including channels such as WhatsApp and Instagram
- The token opens contacts and conversations of the whole workspace and `call_tool` can invoke any API operation, including deletion
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/chatbotxDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent can send messages and broadcasts to customers on behalf of the business, including channels such as WhatsApp and Instagram
- The token opens contacts and conversations of the whole workspace and `call_tool` can invoke any API operation, including deletion
This is third-party code. Review the repository files before installing.
What it does
ChatbotX is an open chat-marketing platform, an alternative to ManyChat: one workspace for WhatsApp, TikTok, Facebook, Instagram, Telegram, email and web chat. The MCP server gives an agent access to the workspace: CRM contacts, flows, sequences, broadcasts and AI automation. The tools are not described by hand. At startup the server reads the platform's OpenAPI spec and registers one tool per operation marked as available by default. The public API has about 350 operations, so the agent sees a curated set plus three helper tools: `search_tools` finds the right operation across the whole API, `call_tool` runs it by name, and `get_guide` returns instructions for working safely with approvals, flows, contacts and pipelines. A client connects remotely with OAuth 2.1 or locally over stdio with a workspace token.
Who it is for. Marketers and small shop owners who run customers through ChatbotX messaging and want to manage broadcasts and contacts through an agent.
Good fit when
- You need to find CRM contacts with a given tag and prepare a broadcast for them
- A WhatsApp bot scenario has to be reviewed and adjusted without opening the visual flow builder
- The agent sorts incoming conversations and hands complex ones to a human operator
- A Shopify or WooCommerce store wants to reconcile its sales funnel with ChatbotX data
Not a fit when
- You have no ChatbotX workspace: the server manages that and nothing else
- You need a one-off mass send to a list: a bulk send from an agent without review can easily reach the wrong recipients
- You need an exact answer about one API operation: calling it directly is simpler
Example request
Find contacts tagged win-back and show a draft broadcast for them, without sendingMCP
- Transport
- http, sse, stdio
- Authentication
- OAuth
Environment variables
CHATBOTX_API_URL- API origin including the `/api` prefix, needed by the local stdio server
Limitations
The tool set is built from the OpenAPI spec and refreshed in the background about every five minutes, so the list can change without a restart. The `search_tools` catalog is entirely in English: the client has to translate the request into an action plus resource itself. Only workspace owners and super admins can authorize the server remotely, and a token acts on the workspace picked at consent. To switch workspaces, disconnect and connect again. Channels such as WhatsApp need their own credentials from Meta.
How to disable. Disconnect the server in the client, for example `claude mcp remove chatbotx`, and revoke the grants under Settings, Integrations, ChatbotX MCP in the dashboard.
FAQ
What is the URL of the remote ChatbotX server?
For Streamable HTTP it is https://app.chatbotx.io/mcp/messages, for legacy SSE https://app.chatbotx.io/mcp/sse. The URL is the same for every account and the workspace is picked on the consent screen.
Why does the agent not see every API operation?
The public API has about 350 operations and the full list would overload the context. The tool list holds a curated set, and the agent finds the rest with `search_tools` and runs it with `call_tool`.
Can it work without OAuth?
Yes, workspace tokens remain for stdio and existing connections. In the local server the API address is set with `CHATBOTX_API_URL`, including the `/api` prefix.
Can the platform be installed on my own server?
Yes, the project is open source. For self-hosting there is a separate chatbotx-docker-compose repository that runs prebuilt images with `docker compose up`.
What is get_guide?
A helper tool that returns safety instructions for approvals, flows, handing a conversation to an operator, contacts and pipelines. It is called before working flows involving those entities.
Discussion
No questions or reviews yet.
Related
MCP serversSendPulse 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
SendPulse MCP server for WhatsApp and SMS
SendPulse MCP Server
An MCP server for SendPulse WhatsApp bots and SMS: contacts, button messages, flows, triggers and live chat
Official Chatway MCP server: the agent triages live chat conversations, replies to customers and searches the knowledge base
Open-source CRM for small teams with MCP: contacts, deals and tasks open to Claude and other agents, with reply drafts left to you
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
Bitrix24 MCP by Bit2Beat
Bitrix24 MCP Server
Bitrix24 MCP server over an inbound webhook: CRM, tasks, disk, calendar, chat, business processes and config migration between portals
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| ChatbotX (this card) | yes | OAuth | 1,111 | |
| SendPulse chatbots MCP server | no | OAuth | 0 | a server for SendPulse chatbots with a fixed operation set, rather than for the open ChatbotX platform that can be self-hosted |
| WhatsApp MCP Server | no | not required | 6,866 | a server for a personal WhatsApp account, with no CRM, flows or platform broadcasts |
README in short
The text opens with a headline about an agentic chat-marketing platform built for OpenClaw, Hermes and Claude and a comparison with ManyChat, Chatfuel and Wati. Next come the TypeScript and Next.js stack, local infrastructure through Docker Compose and a monorepo map where `apps/mcp-server` holds the MCP part.