🧠

The Marketing MCP Stack

The seven-server reference architecture per engagement.

AI-Native Operator's Field Manual · Expert · 7 min read · 5 quiz questions

By Ronan Liedmeier, fractional head of growth and course author · Reviewed 13 October 2026

What you will learn

  • The seven slots (default + alternates)
  • Why seven, not more
  • Extension pack: lead-gen
  • Delivery layer is not optional

Lesson preview

An April 2026 review of the full MCP directory reached a clear conclusion: of 1,000+ listed servers, roughly 25 are production-quality for marketing work — and the minimum viable deployment at most engagements is seven. Stack sprawl is the most common MCP failure mode. Every extra server is context tax (more always-visible tool descriptions), permission risk (more potential write surfaces), and demo fragility (one more thing that can break in front of a client). The seven core slots: Analytics (GA4), CRM (HubSpot), Paid-search (Google Ads official read + custom guarded write), Paid-social (Meta Ads), Search/research (Perplexity or Exa), Content/ops (Notion or the client's authoring surface), Delivery (Slack). Those seven slots cover the vast majority of engagement needs. Extend beyond them only when the engagement specifically requires it. Each slot has a default and battle-tested alternates. Swap based on what the client already uses — don't add slots. Analytics: GA4 (default) / Plausible, Mixpanel, PostHog CRM: HubSpot — generally available, read + write on contacts, companies, deals, tickets, and activities / Salesforce, Pipedrive, Attio. Note: HubSpot MCP is a CRM connector, not a prospecting tool. It doesn't do sourcing or sequences. The April 2026 agency-stack review measured production quality across 25 candidate marketing servers and found that seven slots covered the vast majority of engagement needs. The cost of sprawl compounds fast: every extra server adds always-visible tool descriptions to context, creates another credential to manage, introduces another potential write surface, and adds another point of failure during a demo. The discipline is: document each server's OAuth setup once as a client-installable runbook step, then add servers beyond the core only when the engagement specifically requires them. Runbook-once-reuse-forever is what makes this scale.

Continue reading

Frequently asked questions

Who is "The Marketing MCP Stack" for?
This Expert module in AI-Native Operator's Field Manual is for operators, founders and growth teams who run AI in real work and want production-grade judgement. It takes about 7 minutes and ends with a 5-question quiz.
Do I need to code?
Not necessarily. The workflows use operator tools such as Claude, n8n and Lovable; some exercises are easier if you are comfortable editing a config file or prompt template.
What comes before and after this module?
Before "The Marketing MCP Stack", take "MCP: The Integration Layer" (module 5 of AI-Native Operator's Field Manual). Afterwards, continue with "Gateways, Sprawl, and the Seven-Server Rule".

Unlock this lesson and the full academy

  • Monthly€9.99 / month
  • Yearly€69.99 / year
  • Lifetime€129.99 one time
See plansStart with the free lessons

Loading your lesson…

Related modules