Marketing MCP for Claude and Cursor: Plumbing vs Kitchen

Marketing MCP is the plumbing that lets Claude and Cursor reach your marketing tools through one open protocol. It connects Google Ads, Notion, HubSpot, Slack, and dozens of other systems to a single AI surface. It is not a marketing system. The system is what you build on top of the plumbing: a kitchen of named workflows, approval gates, and a skill library that compounds with every campaign.

Anthropic open-sourced the Model Context Protocol in November 2024, and within twelve months its official intro video had crossed 240,000 views on YouTube. Gartner's 2024 CMO Spend Survey found that 64% of marketing leaders increased AI tool spending year over year while reporting declining satisfaction with tool effectiveness. The pattern shows up cleanly for marketing MCP too: more pipes, less throughput. The protocol is the foundation. Most teams are missing the layers above it.

TL;DR

• Marketing MCP is plumbing, not a system; it connects tools, it does not run campaigns.
• The Plumbing-vs-Kitchen Framework splits the stack into Protocol (MCP), Competency (Skills), and System (workflows + governance).
• Claude Desktop fits research and reporting; Cursor fits landing pages and asset builds; neither alone is a marketing operating system.
• Most marketing MCP pilots stall around day 30 because there is no skills layer, no approval gates, and no shared library.
• The 2026 default is MCP everywhere; the moat is the kitchen you run on top of it.

Why "marketing MCP" is the wrong unit of leverage on its own

The marketing MCP search is dominated by developer tutorials. Most pages explain how to install a server, edit a JSON config, and watch Claude pick up a new tool. That is a setup guide. It is not a marketing answer.

A marketer evaluating MCP for Claude or Cursor is not asking "can I make this tool call work." They are asking "will my paid program ship faster next quarter, and will my SEO compound, and will the system survive my best operator leaving in six months." Those questions live above the protocol layer.

The official MCP definition is precise. It is "an open standard for connecting AI applications to external systems" (modelcontextprotocol.io). The protocol's job is to standardize how an AI host (Claude Desktop, Cursor, Claude Code) talks to a server that exposes tools, resources, and prompts. The protocol does not know what a campaign is. It does not know what "approved to ship" means. That gap is structural, not a roadmap item.

The cleanest practitioner argument for treating marketing MCP as a system question, not a setup question, comes from Mkt1's catalogue of real marketers' Claude Code builds: the best operators are not the ones with the most servers installed. They are the ones who turned their MCP plumbing into reusable competencies.

This piece walks through that shift. The frame is the Plumbing-vs-Kitchen Framework. The point is to stop measuring marketing MCP by server count and start measuring it by the compound work it lets your team ship.

The Plumbing-vs-Kitchen Framework for marketing MCP

We use one framework internally when a marketing operator asks how to evaluate any marketing MCP setup. It carries the conversation cleanly: Protocol, Competency, System. Plumbing, recipes, kitchen.

Protocol (the plumbing). MCP servers expose tools and data through a standard wire format. Notion exposes pages. HubSpot exposes contacts and deals. Google Ads exposes campaigns and assets. The protocol's promise is that any compliant AI host can call any compliant server without bespoke glue. Anthropic's introduction post framed it as "USB-C for AI," which is the right analogy for what the protocol is and the wrong analogy for what it does for marketers.

Competency (the recipes). A recipe is a packaged competency an AI agent can install and run. Anthropic formalized this layer with Agent Skills in late 2025. A skill is a folder with a system prompt, reference documents, and example completions. The agent installs the skill, runs the work, and uninstalls it. A marketing MCP setup without skills produces a fresh prompt every time. A marketing MCP setup with skills produces repeatable output that gets better each cycle.

System (the kitchen). The kitchen is where the work actually happens. It has named workflows. It has approval gates so a misfire does not ship a real campaign. It has audit logs so the head of marketing can answer the CFO's question about a $40K spend variance. It has a shared library so the second operator does not start from scratch. The kitchen is what most marketing MCP guides skip and what most pilots quietly need by day 30.

The three layers together:

For background on how these three layers compose into shippable agentic work, see our piece on the difference between AI workflows, agents, and multi-agents.

The marketing MCP servers that actually matter in 2026

A marketing MCP stack ends up with somewhere between seven and twenty servers installed. Most of them go cold within three weeks. Our internal audit of the first thirty servers our team installed across Claude Desktop and Cursor found the median time-to-orphan was about seventeen days. The servers that survive cluster into four planes.

The data plane is where most marketing MCP setups earn their keep. The clearest single example is connecting Claude Desktop to Google Ads, which converts ten minutes of dashboard clicking into a one-sentence question. Our walkthrough for that exact build is here: connect Claude Desktop to Google Ads with MCP.

The content plane is the second-highest-leverage install. Notion MCP lets Claude pull from and write to a content calendar without an operator extracting and pasting blocks. Sanity MCP closes the loop on publishing. The Medium essay How I Use Claude Code as My Full Marketing Operations System is the cleanest first-person account of this pattern in the wild.

The execution plane is where governance starts to bite. A Slack MCP that posts to channels is fine. A Gmail MCP that sends customer-facing email without an approval gate is one bad prompt away from a brand incident.

The discovery plane is the most underrated. Firecrawl, Perplexity, and a SERP server turn a marketing MCP setup from "internal automation" into "external sensing." Most of the operator value our team sees from marketing MCP in 2026 starts here.

How marketing teams use MCP in Claude versus Cursor

Claude Desktop and Cursor are both MCP hosts. They are not the same product for marketers, and treating them as interchangeable is the second most common mistake we see on day one.

Claude Desktop is a chat surface. It is best at research, reporting, brief generation, and any workflow where the deliverable is a structured document. The marketing MCP workflows that fit Claude Desktop are weekly performance roll-ups, competitor SERP teardowns, draft briefs for the content pipeline, and ad-account audits. The output is a markdown report or a Notion page.

Cursor is an IDE. The Cursor docs cover MCP support cleanly in Cursor's MCP integration page. Cursor shines when the deliverable is code or content that needs to live in a repo: landing pages, programmatic SEO templates, hero image prompts versioned alongside the page, schema markup, A/B test variants, edge-case copy that has to ship via git. Cursor is also the right host when the marketer is collaborating with a GTM engineer on shared assets. For the engineering-side framing on that role, see what a GTM engineer does.

The failure mode looks the same on either host: a marketer installs five marketing MCP servers in one afternoon, gets a magical first demo, and then plateaus by the end of week four. Reddit's r/ClaudeAI thread comparing Cursor against Claude Desktop with MCP captures the pattern perfectly: the runtime works, but nothing is compounding.

Anthropic's own framing helps here. The official MCP introduction explains the protocol layer well. Watching it once is the cheapest way to internalize why MCP is the plumbing and why something else has to be the kitchen.

The marketing MCP plumbing trap: why most pilots stall after thirty days

Three patterns explain almost every stalled marketing MCP pilot we have audited. Each maps cleanly to a missing layer in the framework.

Trap one: no skills layer. The operator types a prompt, the agent calls four MCP tools, the deliverable is decent, the operator moves on. Next week, the same operator (or a teammate) types a slightly different prompt for the same job. The agent does something slightly different. The output is uneven. There is no skill installed, so there is nothing to improve. Our piece on how to create Claude skills walks through the fix.

Trap two: no approval gates. A marketing MCP setup that can update HubSpot deals or send Resend campaigns without a human check is a draft incident waiting to happen. The fix is not to remove the capability. The fix is to wrap the destructive action in an approval gate that logs the proposal, the approver, and the outcome. This is exactly the discipline our piece on how to build AI agents that actually get stuff done covers in detail.

Trap three: no shared library. The first operator builds five great workflows on Claude Desktop and Cursor. The second operator joins, opens a blank chat, and starts over. The team's marketing MCP setup is sole-operator dependency dressed up as automation. Without a shared skills directory and a system around it, every new hire restarts the learning loop.

Harvard Business Review's enterprise AI guidance reaches the same conclusion from a different angle: durable value comes from workflow integration, not point tools. The marketing MCP equivalent is that durable value comes from the kitchen, not the plumbing.

From marketing MCP plumbing to a working kitchen: the operator playbook

Three steps move a marketing MCP setup from interesting demo to system that compounds.

Step one: install MCP only where the agent needs primitives. A common failure is installing fifteen servers in the first week. Start with three. Pick one from data (Google Ads or HubSpot), one from content (Notion or Sanity), and one from discovery (Firecrawl or a SERP server). Add a fourth only when the first three are pulling their weight on a real campaign. The plumbing should follow demand, not anticipate it.

Step two: turn repeat work into Skills. Any prompt you type twice gets packaged. Capture the system prompt, the reference materials (brand voice, ICP, tone guide), and two example outputs. Save the folder. Reference it from Claude Code or your host's skills mechanism. The investment is one to two hours per skill. The payoff is consistent output forever. For paid programs, the highest-leverage starting skill is a Google Ads audit; see Claude skills for Google Ads for the template.

Step three: put the system above the skills. Above Skills, you need workflows, approval gates, audit logs, and a shared library. This is the kitchen. You can build it yourself (a private repo plus careful conventions plus Slack-based approvals), or you can adopt one of the emerging marketing operating systems that ship this layer out of the box. Metaflow is one such system, designed specifically to sit on top of MCP and Skills rather than replacing either. The hosted Metaflow AI marketing agents catalogue is the easiest first surface to evaluate.

For teams that want to skip ahead to the production setup pattern, our best Claude Code setup for marketing teams breakdown is the most concrete walkthrough we have published.

Buyer profile decision table: which marketing MCP stack fits which team

The right marketing MCP stack depends on who is running it. The table below maps the four buyer profiles we audit most often to a concrete recommended stack.

Two honest call-outs go on the table too.

The first: a solo founder publishing fewer than two pieces a month does not need a marketing MCP setup. The right answer is Claude or ChatGPT in a browser, plus discipline. The kitchen overhead exceeds the throughput it unlocks.

The second: an enterprise team with strict data residency or privileged-data constraints should evaluate self-hosted MCP servers and a governance-first kitchen before connecting any cloud-based AI host to live customer data. The protocol does not handle that for you. The system does.

What to evaluate when you choose your marketing MCP stack

Five criteria, in order of weight.

Protocol coverage and host compatibility. Does the stack support the MCP servers you actually need (data, content, execution, discovery) and the hosts your team uses (Claude Desktop, Cursor, Claude Code)? A marketing MCP stack that locks you into one host or one server vendor is a step backward from raw MCP.

Marketing depth. Does the system above MCP include marketing-shaped workflows out of the box (paid audits, SEO briefs, content pipelines, outbound sequences) or does it ship empty and ask your team to author every skill from scratch? Empty is fine for engineering-heavy teams. It is expensive for marketing-only teams.

Deploy effort. How long does the first end-to-end ship take? Our internal benchmark across the four common stacks (raw MCP, Claude Code with Skills, Cursor, Metaflow) found first-ship times of 4-6 hours, 3-4 hours, 3-4 hours, and 1-2 hours respectively. The deltas compound across the first ten ships.

Governance and observability. Approval gates, audit logs, role-based access, rollback. The five questions a head of marketing should be able to answer about any agent action: who triggered it, when, on what data, what changed, who approved. If the stack cannot answer them, the kitchen does not exist yet.

Compounding library. Does your team's marketing MCP work get more valuable over time, or does it reset every quarter? A shared skills directory and a versioned workflow library are the difference between a tool and an asset.

The cleanest way to apply the rubric is to score your current setup against each criterion on a 1 to 5 scale and look for the lowest number. That layer is the one to invest in next. Most teams in 2026 score high on protocol coverage and low on compounding library. That is the gap the kitchen layer is designed to close.

Frequently Asked Questions

What is a marketing MCP server, in plain English?

A marketing MCP server is a small program that exposes a marketing tool (Google Ads, Notion, HubSpot, Slack) through the Model Context Protocol so that any compliant AI host (Claude Desktop, Cursor, Claude Code) can read and write through it without custom code. The server is the plumbing; the AI host is the surface that uses it. The marketer's job is to install only the servers that map to real work.

Is marketing MCP better in Claude Desktop or in Cursor?

It depends on the deliverable. Claude Desktop is best when the output is a structured document or report (briefs, audits, weekly roll-ups). Cursor is best when the output is code or content that lives in a repo (landing pages, programmatic SEO templates, hero image prompts, schema). Most mid-sized marketing teams end up running both. Solo operators usually start with Claude Desktop because the chat surface has the lowest learning curve.

Which MCP servers should a marketing team install first?

Start with three: one data server (Google Ads or HubSpot), one content server (Notion or Sanity), and one discovery server (Firecrawl or a SERP server). Get them pulling weight on a real campaign before adding a fourth. The most common mistake is installing fifteen servers in week one. Time-to-orphan in our audit was about seventeen days for servers that were not tied to an immediate workflow.

How is MCP different from Claude Skills or AI agents?

MCP is the protocol that connects an AI to tools and data. Claude Skills are packaged competencies the agent installs to do specific work (a Google Ads audit, a SEO brief, a content humanizer). An AI agent is the runtime that decides what to do next. In the Plumbing-vs-Kitchen Framework, MCP is the plumbing, Skills are the recipes, and the agent runs inside the kitchen that orchestrates both.

Do I need a marketing operating system on top of MCP?

For solo operators publishing under five pieces a month, no. Discipline plus Claude Desktop is enough. For in-house growth teams above five pieces a month, agencies serving multiple clients, or any team that needs an audit trail, yes. The marketing operating system is where workflows, approval gates, audit logs, and the shared skills library live. Without it, marketing MCP setups stall around day thirty.

When should a marketing team not bother with MCP at all?

When the volume does not justify the setup investment, when the team has no operator who will own the system, or when the data is sensitive enough that a cloud AI host is not yet acceptable to the security team. The honest answer for those teams is to wait, run a small pilot on synthetic data, or hire a GTM engineer first. Marketing MCP is the right answer for most growing teams in 2026; it is not the right answer for every team in 2026.

For broader context, see our roundup of claude skills for marketing, and explore connect Claude Desktop to Google Ads with MCP for related setup guidance.