ActiveCampaign API: ~325 endpoints (v3, SMS, WhatsApp, Segments) as safety-categorized MCP tools.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
One-click editor setup isnβt available for this listing yet β we donβt have a confirmed install command, and weβd rather show nothing than point your editor at the wrong package or host. Follow the projectβs own setup instructions, linked above.
The most complete ActiveCampaign MCP server there is. Run your entire ActiveCampaign account in plain language from Claude, Cursor, or any other MCP client.
This Model Context Protocol server exposes the whole ActiveCampaign account API β ~325 tools β covering the v3 REST API plus the SMS, WhatsApp and async Segments APIs, generated straight from ActiveCampaign's own OpenAPI definitions. Every tool is safety-categorized (π’ read-only / π‘ write / π΄ destructive) so your assistant knows what an action does before it calls it. It runs over stdio (Claude Desktop and other local launchers) or Streamable HTTP (hosted in Docker), and ships with retries, client-side rate limiting tuned to ActiveCampaign's 5 req/s cap, and request timeouts so it holds up against a live account.
Some MCP servers just forward a slice of the API. This one is built to be safe to hand to an LLM, complete, and easy to run for real:
| What you get | Why it matters |
|---|---|
| ~325 tools β the full account API | Complete coverage of contacts, deals, accounts, lists, tags, custom fields & objects, ecommerce (deep data), campaigns, messages, automations, segments, webhooks, tasks, calendars, site/event tracking, SMS and WhatsApp β nothing hand-picked or left behind. Other servers stop at ~60. |
| Curated safety categories π’ / π‘ / π΄ | Not naive "GET = safe": contact sync is flagged as an upsert, a segment-match POST as a read-only query, tagging a contact as a link, and POST /sms/broadcasts as sends messages β so the model knows the real blast radius. |
Machine-readable MCP annotations (readOnlyHint, destructiveHint) | Hosts that honor annotations (Claude included) can auto-trust reads and demand confirmation before anything destructive. |
| Read-only mode & resource filtering | Expose only π’ read-only tools (ACTIVECAMPAIGN_READ_ONLY=true), or narrow to just the groups you use (ACTIVECAMPAIGN_INCLUDE_GROUPS=contacts,deals,lists). Tailor the surface per deployment. |
| Pagination made first-class | limit, offset, orders[β¦] and filters[β¦] are injected onto every list endpoint as typed inputs, so the assistant can page, sort and filter without guessing ActiveCampaign's bracket syntax. |
| Automatic retries with backoff | Transient 429 / 5xx responses are retried with jittered exponential backoff, honoring the server's Retry-After header. |
| Built-in rate limiting | Self-throttles under ActiveCampaign's 5 requests / second account cap so a burst of tool calls never trips a 429. |
| Response-size guard | Optionally cap huge list responses (ACTIVECAMPAIGN_MAX_RESPONSE_CHARS) so one call can't blow the model's context window. |
| GraphQL passthrough | A bonus tool for ActiveCampaign's Ecommerce GraphQL API when you want to shape exactly the fields you need in one round-trip. |
| Two transports: stdio and Streamable HTTP | Use it locally in Claude Desktop, or run one always-on server that any number of MCP clients reach over HTTP. |
| Docker + docker-compose, health check, auto-restart | Production-style deployment out of the box: docker compose up and it stays up. |
| Optional bearer-token auth on the HTTP endpoint | Put the server behind a shared secret the moment it's reachable beyond localhost. |
| Your token never reaches the model | The Api-Token lives in the server's environment and is injected on every request β the assistant only ever sees tool inputs and API responses. |
| Drop-in spec updates | ActiveCampaign ships newer OpenAPI JSON? Replace the file in spec/ and rebuild β new endpoints become new tools automatically, no code changes. |
There are a few ways to reach ActiveCampaign from an AI assistant today. Here's how this server stacks up against the alternatives:
| This server | Official AC remote MCP | HighLiuk mcp-server-activecampaign | mcp-activecampaign (PyPI) | CData MCP | |
|---|---|---|---|---|---|
| Approx. tools | ~325 | curated subset | 58 | ~65 | 3 (generic SQL) |
| Full v3 REST coverage | β | β | β core CRM | β broad CRM | β |
| SMS Β· WhatsApp Β· Segments | β | β | β | β | β |
| Ecommerce deep data + GraphQL | β | β | β | β | β |
| Reads and writes | β | β | β | β | β read-only |
| Self-hosted on your own infra | β | β vendor cloud | β | β | β |
| Connects directly to the AC API | β | β | β | β | β via JDBC driver |
stdio transport | β | β | β | β | β |
| Streamable-HTTP transport | β | β | β | β | β |
| Docker + compose + health check | β | n/a | β | β | β |
| Curated π’ / π‘ / π΄ safety categories | β | β | β partial | β | n/a |
readOnlyHint / destructiveHint | β | β | β | β | β |
| Read-only mode + group filtering | β | β | β | β | always read-only |
Rate limiting + auto-retry (429/5xx) | β | β | β | β | β |
| Language | TypeScript | β | TypeScript | Python | Java |
| License | MIT | proprietary | MIT | MIT | MIT |
β = yes Β· β = partial / not documented Β· β = no. Compiled from each project's public documentation; this is an unofficial project, not affiliated with ActiveCampaign or the projects listed. Tool counts are approximate and move as APIs evolve.
The short version: the official remote MCP is a great managed on-ramp but runs in ActiveCampaign's cloud on a curated slice of the API. The community servers are solid but top out around 60 tools of core CRM, stdio-only, without a deployment story. This one gives you the entire account API, both transports, a Docker deployment, and safety guardrails β self-hosted, on your token, MIT.
Once it's connected, ask your assistant things like:
Tools are generated automatically from ActiveCampaign's specs and grouped into π’ read-only, π‘ write and π΄ destructive β so a well-behaved host can treat each group differently.
The server parses the bundled OpenAPI definitions into MCP tools (resolving
$refs and guarding against recursive schemas), tags each with a curated safety
category, and injects your Api-Token header on every outgoing request. Your
token stays in the server's environment β the model never sees or handles it.
1. Add your credentials. Copy the example config and fill it in:
2. Start the server:
The bundled docker-compose.yml binds to 127.0.0.1:8765 only, so the server is
reachable from your machine but not the network.
3. Confirm it's running:
4. Connect your MCP client. The MCP endpoint is http://localhost:8765/mcp.
Claude Desktop β add a custom connector (Settings β Connectors) pointing
at the URL, or bridge it locally with
mcp-remote. Add this under
mcpServers in your config, then fully quit and reopen the app:
(Drop the --header line if you left MCP_AUTH_TOKEN empty.)
Claude Code β one command:
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/activecampaign-2)<a href="https://allmcps.com/mcp/activecampaign-2"><img src="https://allmcps.com/api/badge/activecampaign-2?style=directory" alt="ActiveCampaign on AllMCPs" /></a>