Model Context Protocol (MCP) consolidated in Q2 2026 from a scattered server ecosystem into a tractable production surface. Anthropic's reference servers, Cloudflare's MCP gateway, and the big-three vendor SDK rollouts (HubSpot, Salesforce, GA4) made MCP-native marketing workflows agency-viable. The directory we actually rely on day-to-day is now ~25 servers wide, not 250.
This review groups those 25 servers into six categories. For each server we capture: capability score (1–5), install ease (1–5), auth model (OAuth, API key, hybrid), agent compatibility (Claude Code, Cursor, Codex Desktop, ChatGPT Apps SDK), and the workflows the server powers in agency-grade agentic marketing stacks.
We close with the recommended 7-server stack — the minimum viable agentic marketing flow we deploy at most agency clients in 2026. Choose servers that fit the workflows your team runs, not the longest stack on the directory.
- 01Twenty-five MCP servers cover ~95% of agency-grade marketing workflows in 2026.Search & discovery (4), CRM (4), analytics (4), ads (3), social (3), content + ops (7). The directory still lists ~250 marketing-related servers, but the production-quality subset is ~25 — the rest are duplicates, abandoned forks, or single-feature wrappers. Concentrate stack effort on the 25, not the 250.
- 02OAuth is now table-stakes — 17 of 25 servers ship native OAuth flows.OAuth flows are now baseline (HubSpot, Salesforce, GA4, Google Ads, Meta, LinkedIn, Notion, Webflow, etc.). Eight servers still rely on API keys (Brave, Tavily, Exa, Plausible, PostHog, Attio, Buffer, Linear). API-key-only servers are fine for back-office workflows but force more secrets handling. Prefer OAuth-native servers for client-facing or cross-org deployments.
- 03Claude Code is the universal agent — all 25 servers connect cleanly.Claude Code's MCP-deep integration handles every server in this review without adapter quirks. Cursor handles ~24 of 25 cleanly. Codex Desktop handles ~22 (OpenAI Apps SDK schema flavor adds friction on a few). ChatGPT Apps SDK directly supports ~21 (OAuth servers) — the rest require a connector adapter. Pick the agent that matches your stack's connector compatibility profile.
- 04Capability and install ease are weakly correlated — pick by workflow, not score.High-capability servers (Salesforce 5/5, GA4 5/5, HubSpot 5/5) often have low install ease (3/5) — OAuth setup, scope configuration, custom-object permissions. High-install-ease servers (Brave 5/5, Plausible 5/5, Notion 4/5) sometimes cap on capability. The right pick is the server that covers the workflow with acceptable install effort, not the server with the highest combined score.
- 05The recommended 7-server stack: Brave + HubSpot + GA4 + Google Ads + LinkedIn + Notion + Linear.Covers 80%+ of agency-grade agentic marketing workflows: search/research (Brave), CRM + lifecycle (HubSpot), analytics + measurement (GA4), paid acquisition (Google Ads, LinkedIn), content + briefs (Notion), and project ops + delivery (Linear). Add Perplexity if research depth matters; add Meta + X if social is a heavy workload; add Webflow or Contentful if site CMS is in-scope.
01 — The FieldThe MCP marketing field.
MCP went from spec to production stack faster than any agent-tooling standard since the OpenAPI generation. Anthropic's reference servers, Cloudflare's MCP gateway pattern, and OAuth-native vendor SDKs collapsed the integration cost from per-customer custom code to per-team config. By Q2 2026 the directory listings (Smithery, Glama, PulseMCP) crossed 1,000 servers across all domains — but the production-quality marketing subset is much narrower.
We grouped the marketing-relevant servers into six categories. The count distribution roughly mirrors how agency teams spend time: content + ops is largest (7 servers covering writing, design, shipping, project tracking), CRM and analytics each take 4 servers of focused depth, search + discovery covers research and competitor work, ads handles paid surfaces, and social covers organic reach and engagement.
Search & discovery — 4 servers
Web search and research-grade retrieval. Powers competitor analysis, content discovery, brand monitoring, and live-data RAG. Brave is the install-ease leader; Perplexity and Exa win on research depth.
CRM — 4 servers
Lead capture, contact lifecycle, deal management, custom objects. HubSpot is the agency-default for SMB; Salesforce dominates enterprise; Pipedrive serves SDR teams; Attio is the modern API-first option.
Analytics — 4 servers
Web analytics + product analytics. GA4 is the universal default; Plausible for privacy-first; Mixpanel for product analytics; PostHog for combined product + session replay + feature flag.
Ads + Social — 6 servers
Paid acquisition (Google Ads, Meta, LinkedIn) and social management (X, LinkedIn organic, Buffer). LinkedIn ad and social servers are increasingly important for B2B; Buffer handles cross-platform scheduling.
Content + Ops — 7 servers
Content authoring (Notion, WordPress), site CMS (Webflow, Contentful), design (Figma), project ops (Linear), team comms (Slack). The largest category — covers the working surface of a marketing team.
02 — Search & DiscoverySearch & discovery — 4 servers.
The four search servers cover web search, research-grade retrieval, and live-data RAG. Most agency-grade agentic flows use at least one of these for competitor research, content discovery, or brand-mention monitoring. Pick by depth: Brave for ergonomic web search, Perplexity for research synthesis, Tavily for agent-tuned search, Exa for embeddings-driven semantic search.
Brave Search MCP — 5/5 install · 4/5 capability
Anthropic-reference quality. Free tier is generous, API key auth, install in ~2 min. The default search server for most agentic flows; pairs well with cited-source workflows. Supports image and news search alongside web.
Perplexity MCP — 4/5 install · 5/5 capability
Research-synthesis quality. The agent gets pre-summarized source bundles instead of raw search results. Pricing is more aggressive than Brave's free tier but the synthesis quality cuts downstream token spend by 30-50% on research workflows.
Tavily MCP — 4/5 install · 4/5 capability
Agent-tuned search built for retrieval-augmented generation. Returns chunked, cited results optimized for LLM consumption. Strong for any RAG flow that ingests live web data. API-key auth, simple setup, generous free tier.
Exa MCP — 4/5 install · 5/5 capability
Embeddings-driven semantic search. The right pick when keyword search misses (e.g., 'find articles like this one' or 'find companies similar to X'). Enterprise pricing higher than alternatives; pays back when semantic similarity is the workflow's central operation.
03 — CRMCRM — 4 servers, one per market segment.
CRM servers cover lead capture, contact lifecycle, deal management, and custom objects. Picks split by segment: HubSpot is the agency-default for SMB and mid-market, Salesforce dominates enterprise, Pipedrive serves SDR-heavy teams, and Attio is the modern API-first option for newer companies.
Agency default · OAuth · 5/5 capability
Most-used CRM in agency engagements. OAuth-native, full coverage of contacts, companies, deals, tickets, lifecycle stages, and custom properties. Deepest agentic-flow ergonomics among CRMs. Install ease 3/5 — OAuth scopes need careful selection.
Enterprise default · OAuth · 5/5 capability
Salesforce dominates enterprise. The MCP server covers leads, contacts, accounts, opportunities, custom objects, and Apex-defined endpoints. Install ease 2/5 — Salesforce permission model is genuinely complex; budget setup time. Enterprise deployments justify the friction.
SDR teams · OAuth · 4/5 capability
SDR-focused workflow CRM. Pipeline-centric data model maps cleanly onto sales workflows; agent ergonomics are tighter than HubSpot's for SDR-heavy use cases. Install ease 4/5 — much simpler OAuth surface than Salesforce.
Modern API-first · OAuth · 4/5 capability
Newer entrant; API-first design from day one. The MCP server is unusually clean — minimal endpoint sprawl, well-typed responses. Capability gap to HubSpot/Salesforce closes month-over-month. Right pick for newer companies that haven't committed to legacy CRM yet.
04 — AnalyticsAnalytics — four measurement surfaces.
Analytics MCP servers cover web traffic, product usage, conversion events, and session-level data. GA4 is the universal default; Plausible serves privacy-first deployments; Mixpanel and PostHog serve product-analytics needs at different price points.
Google Analytics 4 (GA4) MCP — universal default
OAuth, full coverage of GA4 reports, custom events, attribution, and audience exports. The agency default for any web-analytics workflow. Install ease 3/5 — OAuth scopes plus property-level permission setup. Capability 5/5 — covers the GA4 query API end-to-end.
Plausible MCP — privacy-first
API-key auth, lightweight, privacy-preserving analytics. Capability narrower than GA4 (3/5) but install ease is 5/5. Right default when privacy is non-negotiable or when GA4's complexity is overkill for the workload.
Mixpanel MCP — product analytics
Event-level product analytics with cohort and funnel queries exposed as MCP tools. Capability 4/5 for product workflows. OAuth + service-token auth. Right pick when the agentic flow needs to reason about user behavior, not just session traffic.
PostHog MCP — combined product + session + flags
Product analytics + session replay + feature flags + experiments in one server. Capability 4/5; install ease 4/5. Right pick when the team uses PostHog as the unified product-analytics surface and the agentic flows span behavior, replay, and experiment lifecycle.
05 — Ads + SocialAds + Social — six acquisition surfaces.
Ads servers (Google Ads, Meta, LinkedIn) cover paid acquisition. Social servers (X, LinkedIn organic, Buffer) cover organic reach and scheduling. Most agency-grade flows touch at least one ads server; social server picks split by which platforms the team actively manages.
"The Google Ads + LinkedIn pair covers ~70% of B2B paid workflows we see at agency engagements. Meta is the consumer-side counterpart."— Internal MCP-stack survey, March 2026
Google Ads MCP — OAuth · 5/5
Full coverage of Google Ads campaigns, ad groups, keywords, performance reports, and conversion tracking. OAuth-native. Install ease 3/5 — Google Ads OAuth scope is finicky. The default ads server for any paid-search workflow.
Meta Ads MCP — OAuth · 4/5
Facebook + Instagram ad management. OAuth, full campaign + ad set + creative coverage. Install ease 3/5 — Meta's permission model has its own quirks. Right pick for any consumer-side paid acquisition workflow.
LinkedIn Ads MCP — OAuth · 4/5
B2B paid surface. Covers Sponsored Content, Sponsored Messaging, and dynamic ad campaign types. OAuth-native; install ease 4/5. Increasingly important as B2B agentic-marketing flows treat LinkedIn as the dominant paid channel.
X (Twitter) MCP — OAuth · 3/5
Organic post + scheduling + analytics. Capability 3/5 — narrower than the dedicated social-management servers. Install ease 4/5. Right when X is a primary organic channel; pair with Buffer for cross-platform scheduling.
Buffer MCP — API key · 4/5
Cross-platform social scheduling. API-key auth, install ease 5/5. Lower-level than the platform-native servers but covers cross-platform scheduling cleanly. Right pick when the agentic flow needs to publish to multiple platforms in one operation.
LinkedIn organic MCP — OAuth · 3/5
Organic posts, comment management, profile + company-page management. Capability 3/5 — LinkedIn's API surface is still narrower than X or Meta for organic. Right pick for any B2B agentic flow that runs employee-advocacy or company-page workflows.
06 — Content + OpsContent + Ops — seven working surfaces.
The largest category — seven servers covering content authoring (Notion, WordPress), site CMS (Webflow, Contentful), design (Figma), project operations (Linear), and team communication (Slack). Most agency-grade agentic flows touch three or four of these per workflow.
Notion MCP — OAuth · 4/5 capability
Brief authoring, knowledge base reads, project pages. The agency-default authoring surface. Install ease 4/5. Pairs naturally with Linear for project ops and Figma for design briefs. Universal across agentic content flows.
Webflow MCP — OAuth · 4/5
Modern visual CMS. CMS item CRUD, collection management, publish flow. Install ease 4/5. Right pick when the client site is on Webflow; pairs cleanly with Notion (briefs) and Figma (design source).
Contentful MCP — OAuth · 5/5
Headless CMS with strong content-modeling primitives. Capability 5/5 — covers content types, entries, assets, locales, and webhooks. Install ease 3/5 — content model setup adds time. Right pick for enterprise headless deployments.
WordPress MCP — API key · 3/5
WP REST API exposed as MCP. Capability 3/5; install ease 4/5. Right pick when the client runs WordPress and the agentic flow needs to read/edit posts, pages, or custom-post-types. Auth via WP application passwords.
Figma MCP — OAuth · 4/5
Design file metadata, comments, design-token export, asset export. Capability 4/5. Install ease 4/5. Pairs naturally with Notion (briefs) and Webflow/Contentful (publish target). The design-system bridge for agentic content flows.
Linear MCP — OAuth · 4/5
Project ops and engineering ticket flow. Issue CRUD, project, cycle, label management. Install ease 5/5. The agency-default project-ops surface. Required when agentic flows need to create or update tickets as part of execution.
Slack MCP — OAuth · 4/5
Channel reads, message posts, file uploads, search. Capability 4/5. Install ease 4/5. The team-comms surface for agentic flows that need to surface results, request approvals, or post status updates inline with team workflows.
07 — Recommended StackRecommended 7-server agency stack.
The minimum-viable agentic marketing stack we deploy at most agency engagements is seven servers. The seven cover ~80% of the workflows we run; the remaining 20% adds two-to-four servers based on the specific client mix (consumer-paid, multi-CMS, etc.).
Brave — search & discovery
Default web search for research, competitor work, brand monitoring. Free tier covers most agency workloads.
HubSpot — CRM
Lead capture, lifecycle, deal management. Default CRM for agency engagements that aren't enterprise-Salesforce-bound.
GA4 — web analytics
Web traffic, conversions, attribution. The universal default; every agency engagement uses it.
Google Ads — paid search
Paid-search campaign management. Default for any paid-acquisition workflow.
LinkedIn (Ads + organic) — B2B
B2B paid + organic. Single-vendor coverage of LinkedIn's two surfaces — required for B2B agency engagements.
Notion — content + briefs
Brief authoring, knowledge base, project pages. The agency authoring surface; pairs with Linear and Figma.
Linear — project ops
Project ops, ticket flow, cycle management. Required when agentic flows need to create/update tickets as part of execution.
08 — ConclusionPick by workflow coverage, not directory size.
Twenty-five servers cover ~95% of workflows. The recommended seven cover ~80%.
By April 2026 the MCP server ecosystem has consolidated enough that agency-grade marketing teams can build production-quality agentic stacks with off-the-shelf servers. The directory size has crossed 1,000 — but the production-quality marketing subset is ~25, and the minimum-viable stack we deploy at most engagements is seven.
The pattern that scales: pick servers that fit the workflows you run, not the longest-stack on the directory. Brave + HubSpot + GA4 + Google Ads + LinkedIn + Notion + Linear covers ~80% of agency-grade flows. Add Perplexity if research depth matters; add Meta + X if social is a heavy workload; add Webflow or Contentful if site CMS is in-scope. Resist the urge to install every directory entry.
The right move for most agency teams: standardize the 7-server core, document the OAuth setup steps as a runbook, and only add new servers when a specific client engagement requires them. Stack sprawl is the most common MCP failure mode in 2026; disciplined coverage is the antidote.