Skip to content
Agents tracked: 502 Releases (7d): 762 Agent status: no reported issuesSince last limit reset: Claude 11d · Codex 9d For AI agents: Markdown Updated Nov 22, 2026

ChatbotX

by ChatbotXIO

run chat marketing from your AI assistant.

Commerce and paymentsOfficialRemote

GitHubWebsite

1. Made by

“The production endpoints are `https://app.chatbotx.io/mcp/messages` for Streamable HTTP and `https://app.chatbotx.io/mcp/sse` for legacy SSE”

The server lives in apps/mcp-server of the ChatbotXIO/ChatbotX monorepo, the product's own code, and the remote runs on app.chatbotx.io, the vendor's domain.

github.com/ChatbotXIO/ChatbotX/blob/d50c84a5cad67917cc294e5aebebb59f028a452c/apps/mcp-server/README.md

Checked against its repository at one commit, on Nov 10, 2026. Tap a verdict to see its source.How we checkedReport an error

What ChatbotX does

ChatbotX is a chat marketing platform for WhatsApp, Messenger, Instagram, Telegram, email and more. This server lets your AI assistant find contacts, send messages, start automated chats and read campaign numbers in your ChatbotX workspace. Every change waits for your yes before it goes through.

What people use it for

Manage leads by just asking

Ask your assistant to find new leads, update their details, add tags or put them into a follow-up series, without opening the dashboard.

Route new chats to the right flow

Your assistant reads a conversation, works out what the customer wants and starts the matching automated chat, or hands it to a person on your team.

Build and check chat flows

Draft a new automated chat in your code editor, check it against the official format, and publish it only when it passes.

Weekly campaign numbers

Get a short report on new contacts, blocked contacts, and how your broadcasts, flows and follow-up series performed.

Connect a self-hosted ChatbotX

If you run ChatbotX on your own server, your assistant starts the helper on your computer and talks to your own instance with a workspace token.

Clean up contacts before a campaign Idea

Before a big send, have your assistant list contacts without a key tag or field, and fix them one by one with your approval.

ChatbotX popularity

1,136
GitHub stars, ChatbotXIO/ChatbotX
0
public agent projects connect it
ChatbotX: GitHub starsChatbotXIO/ChatbotX 1,136

Tools it gives your agent (55)

What it sends and its license

Sends

Every tool call with its arguments (contact details, message text, flow drafts)

To app.chatbotx.io (or your own instance's API); each tool call. Opt out: self-host ChatbotX and point CHATBOTX_API_URL at your own instance.

Sends

Messages and flows to your customers

To WhatsApp, Messenger, Instagram, Telegram and the other connected channels; when contacts_send_message, contacts_send_flow or a broadcast runs. Opt out: use a read-only token.

The code is free to use, change and sell under the MIT license, except one enterprise folder under a commercial license. Using the hosted ChatbotX service is a separate paid or free plan.

In a paid app
With conditions

The server code is MIT; the apps/builder/src/enterprise folder of the same repo has a commercial license.

“Content outside of the above mentioned directories or restrictions above is available under the MIT license as defined below.” source

client-work
With conditions

Fine for client work with the MIT notice kept; the client needs their own ChatbotX workspace and plan.

“The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.” source

Is it alive

Latest version

1.8.1 in the registry, updated Nov 6, 2026

Last release

chatbotx-mcp 1.20.0 on npm, 2026-11-09; repo commit d50c84a on 2026-11-10

Remote endpoint
yes: an unauthenticated HEAD to https://app.chatbotx.io/mcp/messages answered 401 (sign-in required)

Alternatives

ChatbotX This page

1,136 starsRemote

com-relaticle-crm

Pick it if you want an open-source CRM for companies, people and deals without chat channels

Local

mcp

Pick it if the task is payments, invoices or customers in Stripe

2,072 starsRemote

All commerce and payments servers

Get started

Tell your AI assistant

“Connect the ChatbotX MCP server at https://app.chatbotx.io/mcp/messages, call capabilities_get and token_get first, and show me every CONFIRMATION_REQUIRED response before you repeat a call with _confirm.”

Connect it

claude mcp add chatbotx -t http -s user \
  "https://app.chatbotx.io/mcp/messages"

Claude Code and Cursor configs are from the server README (browser sign-in, no token); the Codex config is from the official docs page and uses a workspace token. CHATBOTX_API_KEY is only for the local (stdio) setup.

Mistakes to avoid

Put the workspace token in the connector URL (?workspace_token=...) for Claude Code or Cursor
Use https://app.chatbotx.io/mcp/messages with browser sign-in; keep tokens for the local stdio setup only

Tokens in URLs end up in logs and shell history; the hosted endpoint signs in through the browser.

Repeat a CONFIRMATION_REQUIRED call with _confirm true on your own
Show the proposed action and current state to the user and repeat only after a clear yes

The server does not stop a repeated call; the approval is the agent's job.

search_tools with a whole user request in another language
search_tools with one English action plus one resource, e.g. "add tag to contact"

The search ranks English tool names and descriptions and does not translate.

call_tool with every field wrapped in body, params or input
Pass the fields flat at the top level of arguments, as the tool's inputSchema declares them

The pre-flight check rejects wrapped arguments.

Drop the response of connections_create with provider api
Save secret.token from that response right away

The token is shown once and cannot be fetched again.

Questions

Do I have to paste a secret key into my assistant?

No for the hosted server. Claude Code, Cursor and ChatGPT sign in through the browser; a workspace token is only needed for the local or self-hosted setup.

Why does my assistant not see a delete tool?

Deletes and less common actions are left out of the default list. The assistant finds them with search_tools and runs them with call_tool.

Can I connect one assistant to two workspaces?

One connection acts on one workspace, chosen at sign-in. To switch, disconnect and connect again.

Which Node.js version does the local setup need?

Node.js 24 or newer.