MCP explained: or, as MarOps people might call it…
Model Context Protocol is a big deal. The name does it absolutely no favors.
If you work in marketing operations, you’re probably used to acronyms that require another acronym to explain them. MCP has quickly joined the club.
Technically, MCP stands for Model Context Protocol.
Practically, it gives an AI application a standard way to connect to external context and capabilities exposed by MCP servers.
What the words mean together
Model
The “model” is the AI language model used by an application. MCP does not provide or train the model, and it does not dictate how the model reasons. It standardizes part of the application’s connection to outside information and actions.
Context
“Context” is the information relevant to the work—such as campaign details, customer records, approved messaging, or lifecycle definitions—and, through tools, the actions a connected system makes available. It is not a copy of every system’s data by default; a server exposes what it is designed and authorized to expose.
Protocol
A “protocol” is a shared set of rules that lets software discover capabilities and exchange requests and results in a predictable format. MCP is the common interface—not a model, database, AI agent, or replacement for a CRM or marketing platform.
How MCP works technically
An AI application, called a host, can connect to one or more MCP servers. For each connection, it uses an MCP client to communicate with a server. The server is a program that exposes context or capabilities; it can run locally or remotely. “Server” names its role in the exchange, not necessarily the location of an AI or a special vendor product.
MCP messages use JSON-RPC 2.0, a structured format for requests, responses, and notifications. The messages travel over a transport: stdio for a local process or Streamable HTTP for remote connections. This lets an AI host use the same basic conversation with different MCP servers, even when each server connects to a different underlying platform. The server may use that platform’s existing API behind the scenes; MCP standardizes the host-to-server interface, not every platform’s internal data model.
MCP servers can expose three useful kinds of capabilities:
- Tools are functions the AI application can ask to run, such as searching for a campaign or creating a draft task.
- Resources are information the application can retrieve as context, such as campaign records or approved definitions.
- Prompts are reusable prompt templates or workflows that help users request work consistently.
For more detail, see the official MCP architecture guide and the MCP specification.
MCP does not grant blanket access or make every action safe. The AI application and server configuration determine what is available; identity, permissions, tool design, approvals, and audit controls still matter. A model can request a tool, but the implementation decides whether that request is allowed and what actually happens.
Think about how most of us use AI today. You ask a question. It gives you an answer. Then you go into the CRM, marketing automation platform, reporting tool, project management system, or wherever else and actually do the work.
MCP can start changing that relationship. Instead of relying only on what you type into a prompt, the AI application can request context and tools exposed by connected MCP servers.
Depending on which servers and permissions are configured, an AI application could potentially:
- Find the right customer or campaign data.
- Look at activity across connected systems.
- Create or update records.
- Build a campaign from an approved brief.
- Pull performance information and explain what happened.
- Identify something that looks wrong and help investigate it.
- Execute repeatable operational tasks instead of giving you instructions for doing them yourself.
In other words, AI starts moving from “tell me how” toward “help me do it.”
Why MarOps should care
Because MarOps has never really had a shortage of software.
We have a shortage of systems that cooperate.
Data lives in one place. Campaigns live somewhere else. Sales activity is over there. Reporting has its own version of reality. Someone changed a field. A permission disappeared. A workflow stopped firing. And somehow there are now 14 versions of the same contact.
Which brings us to our unofficial definitions of MCP.
Depending on the day, MCP may also stand for:
- Marketing Chaos Protocol.
- Maybe Check Permissions.
- Mysterious Campaign Problems.
- Manual Processes Continue.
- Metrics Completely Pointless.
- Marketing Created Duplicates.
- Merge Contacts, Pray.
And, on a particularly good day:
Marketing Crisis Prevention.
That last one is actually where this gets interesting.
MCP isn’t another marketing platform you need to buy. It gives an AI application and connected MCP servers a common way to exchange context and tool requests. A server may use a platform’s existing API behind the scenes; MCP doesn’t replace that API, unify every system’s data model, or make systems cooperate automatically.
And that could matter enormously in MarOps.
The opportunity isn’t simply having AI write another email faster.
It’s giving AI enough context and controlled access to help find the broken workflow, reconcile the data, surface the anomaly, execute the repetitive task, or tell you what happened before someone asks why the dashboard looks weird.
That is a much more interesting future for AI in marketing operations.
What that could look like in Marketing Ops
These are illustrative workflows, not features built into the protocol. The server has to expose the right data and tools, and access has to be configured.
- Campaign preflight: Read an approved brief, campaign setup, audience rules, and UTM standards, then flag a missing suppression list or mismatched segment. The assistant can draft a correction checklist; a campaign owner approves changes and launch.
- Lead-routing investigation: Check an authorized CRM record, marketing automation program history, and routing rules to explain why a lead was not assigned. The assistant can propose a fix or stage an update for review instead of silently editing a live record.
- Performance triage: Retrieve campaign, spend, response, and pipeline metrics from connected reporting sources, align date ranges and definitions, and summarize an anomaly with links to source records for an analyst to confirm.
- Database hygiene: Find likely duplicate contacts and compare the matching evidence and consent or source history, then prepare a merge recommendation. A person reviews it because an incorrect merge can damage records.
MCP provides the common channel. Data quality, consistent field definitions, privacy rules, and approval policy remain Marketing Ops work. It connects an assistant to chosen capabilities; it is not a shortcut around governance.
So for the next 34 days, we’re giving MCP a new definition every day based on the things MarOps teams actually deal with.
Some will be painfully familiar.
Tomorrow’s MCP: Marketing Chaos Protocol.
Because before we let AI operate the stack, we should probably introduce it to the stack.