Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect ActiveCampaign to Claude Code

Make Claude update contacts, tag, and enroll automations in ActiveCampaign. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect ActiveCampaign to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect ActiveCampaign, you add a ActiveCampaign MCP server: a small hosted service that exposes ActiveCampaign's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own ActiveCampaign account. No API keys pasted into config files.

claude mcp add --transport http activecampaign https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in ActiveCampaign once connected?

Full read-write ActiveCampaign access lets Claude update contact fields, add or remove tags, manage list subscriptions, enroll people into automations, and prepare campaigns from a brief, then act once you approve. The list hygiene and segmentation that used to mean manual clicking happen where your contacts already live.

  • Update a contact's fields and custom field values
  • Add or remove tags to segment contacts
  • Subscribe or unsubscribe a contact from a specific list
  • Enroll a contact into an automation, or remove them from one
  • Draft a campaign from a brief for your review before it sends
  • Find every contact matching a query and propose a batched tag update

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same ActiveCampaign access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the ActiveCampaign API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when ActiveCampaign changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build ActiveCampaign connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same ActiveCampaign connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own ActiveCampaign account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on ActiveCampaign's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to ActiveCampaign?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the ActiveCampaign account it signs in with. Revoking access is one click in ActiveCampaign.

More on the ActiveCampaign connector

ActiveCampaign connector for claude.aiMailchimp + Claude CodeKlaviyo + Claude CodeMarketo + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us