에이전트 강화
게시자의 자체 명령입니다. PlugMCP 엔드포인트가 아닙니다.
Host a copy with our keys and logs.
docker run -i --rm ghcr.io/ohneben/activecampaign-mcp:1.1.1Claude Code에는 로컬 명령용 설치 링크가 없습니다. 아래 명령을 복사해 터미널에서 실행합니다.
MCP_TRANSPORT=<value> ACTIVECAMPAIGN_API_URL=<value> ACTIVECAMPAIGN_API_TOKEN=<secret> MCP_AUTH_TOKEN=<secret> claude mcp add io.github.ohneben-activecampaign-mcp -- docker run -i --rm ghcr.io/ohneben/activecampaign-mcp:1.1.1터미널에서 실행합니다.
{ "mcpServers": { "io.github.ohneben-activecampaign-mcp": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/ohneben/activecampaign-mcp:1.1.1" ], "env": { "MCP_TRANSPORT": "<value>", "ACTIVECAMPAIGN_API_URL": "<value>", "ACTIVECAMPAIGN_API_TOKEN": "<secret>", "MCP_AUTH_TOKEN": "<secret>" } } }}claude_desktop_config.json
원격 URL인가요, 내 컴퓨터에서 실행하는 명령인가요? 두 설치 방식의 차이
PlugMCP에서 실행
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
실행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:
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.
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.
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.
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.
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
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.ACTIVECAMPAIGN_API_TOKEN.Put both in .env. The server injects the token on every request, so your
assistant never sees it.
Everything is set in .env (copied from .env.example):
After changing .env, reload with docker compose up -d --force-recreate.
Run npm run list-tools (no credentials needed) to print the full catalog, the
per-category counts, and the list of resource-group keys you can filter on.
Each tool's description starts with one of these banners and carries the matching MCP annotations:
That's 162 read-only · 119 write · 44 destructive = 325 tools. Hosts that
respect annotations (Claude included) can require confirmation for
destructiveHint tools and trust readOnlyHint tools automatically. Prefer to
lock it down further? Set ACTIVECAMPAIGN_READ_ONLY=true to expose only the 162
read-only tools.
Prefer the classic stdio mode for Claude Desktop? Build it locally:
npm install
npm run build
Then point Claude Desktop at the compiled entrypoint in
claude_desktop_config.json:
{
"mcpServers": {
"activecampaign": {
"command": "node",
"args": ["/ABSOLUTE/PATH/ActiveCampaign-MCP/dist/index.js"],
"env": {
"MCP_TRANSPORT": "stdio",
"ACTIVECAMPAIGN_API_URL": "https://your-account.api-us1.com/api/3",
"ACTIVECAMPAIGN_API_TOKEN": "your-api-token"
}
}
}
}
The bundled files under spec/ are the source of truth for the tools:
To refresh against a newer API version, drop the updated OpenAPI JSON in place (or
point ACTIVECAMPAIGN_SPEC_DIR at a directory using the same filenames) and
rebuild. New paths become new tools automatically — no code changes needed.
npm install
npm run build # compile TypeScript → dist/
npm test # run the Vitest suite
npm run list-tools # print the categorized tool catalog (no credentials needed)
CI builds and tests every push across Node 20 and 22; pushes to main also
publish a Docker image to the GitHub Container Registry.
MCP_TRANSPORT=stdio (default) for local launchers;
MCP_TRANSPORT=http for the always-on Streamable-HTTP server the Docker image
runs.limit (max 100), offset,
orders ({"email":"ASC"}) and filters ({"name":"ecom"}). For very large
contact exports ActiveCampaign recommends orders={"id":"ASC"} + id_greater.ACTIVECAMPAIGN_MAX_REQUESTS
per ACTIVECAMPAIGN_RATE_WINDOW_MS (default 4 / 1 s) and retries any 429 it
still receives, honoring Retry-After.body argument; its schema is resolved
from the spec and shown to the model (e.g. create-contact expects
{"contact": {…}})..env, which is git-ignored. Never commit real
secrets. The token grants full account access — if it leaks, rotate it in
ActiveCampaign → Settings → Developer.MCP_AUTH_TOKEN and send it as an
Authorization: Bearer <token> header — ideally behind TLS.ACTIVECAMPAIGN_READ_ONLY=true mode.See SECURITY.md for the full policy and how to report a vulnerability.
An unofficial community integration for ActiveCampaign; not affiliated with or endorsed by ActiveCampaign. Built on the Model Context Protocol. Tools are generated from ActiveCampaign's public OpenAPI definitions. Licensed under the MIT License.
ActiveCampaign API: ~325 endpoints (v3, SMS, WhatsApp, Segments) as safety-categorized MCP tools.
{ "mcpServers": { "io.github.ohneben-activecampaign-mcp": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/ohneben/activecampaign-mcp:1.1.1" ], "env": { "MCP_TRANSPORT": "<value>", "ACTIVECAMPAIGN_API_URL": "<value>", "ACTIVECAMPAIGN_API_TOKEN": "<secret>", "MCP_AUTH_TOKEN": "<secret>" } } }}도구
아직 도구 목록이 없습니다. 원격 서버는 첫 상태 확인 후에 도구 목록이 생깁니다.
FAQ
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 stdio 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
게시자가 등록한 환경 변수: MCP_TRANSPORT, ACTIVECAMPAIGN_API_URL, ACTIVECAMPAIGN_API_TOKEN, MCP_AUTH_TOKEN.
ActiveCampaign은(는) stdio를 통해 로컬에서 실행됩니다.
마지막 확인: 2026-11-10. ActiveCampaign API: ~325 endpoints (v3, SMS, WhatsApp, Segments) as safety-categorized MCP tools.