ActiveCampaign

ohneben's ActiveCampaign MCP

License & checks

MCP registries

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.

Why you'll want this

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:

How it compares

There are a few ways to reach ActiveCampaign from an AI assistant today. Here's how this server stacks up against the alternatives:

✅ = 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.

What you can do

Once it's connected, ask your assistant things like:

• "Find the contact jane@example.com and show her tags, lists and recent activity."
• "Create a deal for Acme Corp worth $12,000 in the 'Sales' pipeline, stage 'Qualified'."
• "List contacts added this month who opened the last campaign but haven't been tagged 'engaged'."
• "Add the tag 'webinar-2026' to every contact on list 5."
• "Show total ecommerce revenue and the top 10 orders from last week."
• "Create a segment of customers in Germany and count how many match."
• "Draft an SMS broadcast to the 'VIP' list — but don't send it until I confirm."

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.

How it works

Claude / Cursor / any MCP client  ──MCP──►  this server  ──HTTPS──►  ActiveCampaign API (your account)

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.

Requirements

• An ActiveCampaign account with API access — your API URL and API token from Settings → Developer. See Get your API credentials.
• Docker (Docker Desktop on macOS/Windows) for the quick start below — or Node.js ≥ 18 to run from source.

Quick start (Docker)

1. Add your credentials. Copy the example config and fill it in:

cp .env.example .env

edit .env → set ACTIVECAMPAIGN_API_URL and ACTIVECAMPAIGN_API_TOKEN

→ set MCP_AUTH_TOKEN to a long random string if reachable beyond localhost

2. Start the server:

docker compose up -d --build

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:

curl -s http://localhost:8765/health

→ {"status":"ok","server":"activecampaign-mcp","tools":325}

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:

  {

"mcpServers": { "activecampaign": { "command": "npx", "args": [ "mcp-remote", "http://localhost:8765/mcp", "--header", "Authorization: Bearer YOUR_MCP_AUTH_TOKEN" ] } } }

(Drop the --header line if you left MCP_AUTH_TOKEN empty.)

• Claude Code — one command:

  claude mcp add --transport http activecampaign http://localhost:8765/mcp

• Claude Cowork — shares Claude Code's MCP config, so the command above makes the tools available there too.

Prefer a prebuilt image?

Every push to main publishes a ready-to-run image to the GitHub Container Registry, so you can skip the local build entirely:

docker run -d --name activecampaign-mcp -p 127.0.0.1:8765:8765 --env-file .env \

ghcr.io/ohneben/activecampaign-mcp:latest

Get your API credentials

1. Log in to ActiveCampaign and open Settings → Developer.
2. Copy your API URL → ACTIVECAMPAIGN_API_URL. It looks like https://your-account.api-us1.com/api/3. Use the exact URL shown — not all accounts are on api-us1, and custom domains differ.
3. Copy your API Key → ACTIVECAMPAIGN_API_TOKEN.

Put both in .env. The server injects the token on every request, so your assistant never sees it.

Configuration

Everything is set in .env (copied from .env.example):

| ACTIVECAMPAIGN_READ_ONLY | — | false | Expose only 🟢 read-only to