If you use Keap, HighLevel, ActiveCampaign, or any other CRM with an API, the term MCP is going to start showing up more and more in conversations about AI. This post breaks down what it means and why it's worth paying attention to.

Start with what you already know: the API

Most CRM users have at least heard the term API, even if they've never written a line of code. An API — application programming interface — is what makes it possible to interact with a system programmatically rather than through its user interface. When you use Zapier or Make to connect Keap to a spreadsheet, or when PlusThis reaches into your CRM to apply a tag based on form behavior, that's all happening through the API.

The API has always supported actions like creating a contact, updating a field, applying a tag, pulling a list of records. Tools like Zapier made those actions accessible without requiring anyone to write the underlying code.

What an MCP adds

MCP stands for Model Context Protocol. It's an open source standard that lets AI models — Claude, ChatGPT, and others — use APIs directly. The result: instead of building a pre-configured trigger-action workflow in Zapier, you can open a conversation with Claude and say "find me the open opportunities in my pipeline that don't have a next action date" — and Claude figures out which API calls it needs to make to answer that question.

Paul's plain English version: "It's like a new-age version of Zapier or Make, except you can just use plain English."

The distinction that matters most for CRM users is this. A Zapier workflow is something you design in advance — when this happens, do that. It runs automatically and handles volume. An MCP is something you interact with in real time — you ask a question, you get an answer, you ask a follow-up. It's closer to having a conversation with your data than setting up a system to manage it.

Both are useful. They're just different tools for different moments.

When to use an MCP vs. a workflow

The interview surfaces a useful framework for thinking about when each approach makes sense.

If something happens repeatedly at scale — every new lead from a Facebook ad gets created as a contact and tagged in Keap, every purchase triggers a welcome sequence — that's a workflow. You build it once and it runs. The MCP isn't the right tool for that.

If you want to ask a question about your data, analyze a specific contact's situation, or do something bespoke for a particular person right now — that's where the MCP fits. You're the human in the loop, initiating the conversation and making decisions based on what comes back.

Paul put it this way: think of it as having an assistant who can talk to your CRM. You wouldn't send your assistant to run a mass email campaign — that's what automation is for. But if you want someone to pull together everything they know about a specific prospect before a call, that's exactly what you'd ask an assistant to do.

Setting it up: the project layer

Cam asked Paul how a Claude project factors into this, since the MCP connection happens at the project level. Paul's setup includes not just the Keap MCP connection but also a set of rules and context he's given the project — calendar link logic for clients versus prospects, which pipeline stages belong to his consulting business versus his nonprofit, and other business-specific context that helps Claude interpret queries correctly.

This means Claude doesn't just have access to the data. It has context about what the data means, which lets it give more useful answers and flag ambiguities — like recognizing that some pipeline stages in Paul's system belong to Keap Children Rockin', his nonprofit, rather than his consulting business.

Where to start

Paul's step one for anyone curious but not sure where to begin: connect the MCP and ask it what your own contact ID is. Don't try to do anything with it yet — just see whether it can find you. From there, ask it what it can see and what it can do. Get a feel for the boundaries before trying to push them.

Cam added one more useful tip: you don't have to Google whether your CRM has an MCP. Just ask Claude. "Can you work with ActiveCampaign?" is a more natural starting point than digging through documentation, and it gets you an answer in the same interface you'll be using anyway.

The technology is early enough that there are still real limitations — not every API endpoint is accessible through every MCP, and some queries require workarounds. But the direction is clear. CRMs that have APIs are going to be increasingly accessible through plain English conversation, and getting familiar with the concept now puts you ahead of the curve.

‍