The 10 best MCP servers for marketing

Almost every list ranking MCP servers for marketing was written by a vendor that put itself first — and none of them tell you.

So here's the deal with this one: I run Orshot, it's on this list, and I'll tell you exactly where it sits and why. Nearly everything else here is a server I pay for or use to market Orshot itself — the two newest additions are marked as such. Where something broke on me, I've written that down too.

Quick comparison

The "Works in Claude web" column is the one nobody prints. The rule: servers with OAuth connect to claude.ai in the browser as custom connectors. Servers that authenticate with a Bearer header — DataFast is the one on this list — only work in Claude Code or Claude Desktop, where you control the config file. Ahrefs documents Claude Code; I haven't gotten it into claude.ai web.

What an MCP server is, in one paragraph

MCP (Model Context Protocol) is the plug socket for AI assistants: a vendor ships a server, you connect it, and your assistant can query analytics, render an image or schedule a post instead of just talking about doing it. A vendor ships an MCP server; you connect it to Claude, ChatGPT, Cursor or any agent; the assistant can then read your data and take actions with your permission. That's the whole idea. The interesting question isn't the protocol, it's which servers are worth the context they consume.

How I picked these

Three rules, learned the slightly expensive way:

• Vendor-maintained or nothing. Security audits keep finding public MCP servers with no auth at all. If a server can write to a tool you care about, it should be the vendor's own. The one exception on this list (Search Console) is read-only.
• It has to be in our actual stack. Most of these run our marketing daily — this post's own research went through several of them. Two entries (Octolens, Senja) are newer: I trialed both while writing this rather than pretending long experience. No entry is here because it appears on other lists.
• Read-only wherever money moves. A recurring report on Reddit: an agent fumbles a tool call near a live ad budget. Our Stripe connection can read everything and change nothing, and Supabase ships a read_only=true flag for exactly this reason.

My bias is on the table: I make Orshot. It's the number-two entry, the catches listed under it are real ones, and you can judge whether it earned the slot.

1. PostHog — made for asking your analytics questions in plain English

Link to PostHog MCP docs ↗

Product analytics is where every marketing question ends up eventually. PostHog's MCP means the question can stay a question — "which marketing pages had the highest signup conversion last month?" — instead of becoming twenty minutes of dashboard archaeology.

Why it earns the slot

• A free remote server at mcp.posthog.com/mcp — OAuth sign-in, auto-routes to your US or EU region, and it sits in the Claude connector directory. No server to run.
• The code-mode rework is clever. Instead of a wall of tool schemas, it exposes a single exec tool the agent drives with CLI-style commands. A user on r/mcp walked through a real query days ago: the agent chained schema-read → docs → four SQL queries on its own, at a fraction of the old token cost.
• It reaches everything — events, funnels, session data, feature flags, experiments — so "why did signups dip Tuesday" is answerable in one place.

Setup

npx @posthog/wizard@latest mcp add

Or connect it straight from Claude's connector directory — first use prompts a PostHog login and OAuth handles the rest. Claude Desktop can also add it manually via mcp-remote pointing at https://mcp.posthog.com/mcp.

Queries we run

• "Compare signup conversion for visitors landing on competitor-alternative posts vs free-tool pages, last 30 days."
• "Which referrers sent visitors who reached the pricing page this week?"
• "Did signup-to-activation move after the last homepage deploy?"

The catches

• The minimal-tool design can briefly confuse clients — early users reported Claude expecting "a bunch of tools" and finding one. It settles once the agent reads the docs tool.
• Some MCP tools call LLMs internally and can show up as PostHog AI spend. Watch the first bill.

2. Orshot — made for branded creatives your agent can actually ship

Link to Orshot MCP ↗

Full disclosure: this one is ours.

Orshot is a creative automation suite, not just a render endpoint. There's a studio editor where the template gets built once, with the changing parts flagged as parameters; an API that renders images, PDFs and video from that template with data from anywhere — a spreadsheet, your product database, a form, a webhook, an agent; and delivery built in, so the output can publish straight to social platforms, land in cloud storage, or come back as a URL you drop anywhere.

For marketing, that turns the repetitive creative into a pipeline: product visuals at catalog scale, launch and changelog announcements, weekly report graphics, localized ad variants — one template each, rendered on demand with the right data. The MCP server puts that whole loop inside a chat.

Why it earns the slot

• Deterministic output. The agent fills a template; it doesn't improvise pixels. Same brand, same layout, correct price on every variant — which is the requirement in marketing, where "close enough" isn't.
• Any data source, bulk by default. Point it at a product feed, a spreadsheet or a CRM view and get one on-brand render per row — the job that eats design weeks when done by hand.
• OAuth remote server at mcp.orshot.com/mcp — works in claude.ai web, Claude Code, Cursor, ChatGPT and ten other agents. OAuth end to end — nothing to paste.
• It finishes the job. Render and publish to Instagram, LinkedIn, TikTok and 10+ platforms from the same conversation, or hand the file back for review first.
• 2,000+ ready templates plus your own imports, so the agent has somewhere to start.

Setup

claude mcp add orshot --transport http https://mcp.orshot.com/mcp

Or in claude.ai: Settings → Connectors → Add custom connector → paste the URL. OAuth handles the rest.

Queries we run

• "Render this week's changelog as a branded announcement image and give me the file."
• "Make five variants of the launch template with these five headlines."

The catches

• The editor has real limits. A Reddit user testing us this month put it plainly: "their image editor is the weak point. Font rendering and text effects feel limited." Fair, and we're on it — but if your templates lean on heavy text effects, check yours renders the way you want before wiring up an agent.
• Past a few hundred renders a month, use the REST API instead. The MCP is for conversational and agent-driven work; bulk pipelines belong on the API, where you control batching and retries.
• Rendering draws plan credits. Connecting is free and every account starts with 30 free credits, but an agent that renders all day needs a plan sized for it.

3. Ahrefs — made for SEO data your agent can act on

Link to Ahrefs MCP docs ↗

The most useful SEO workflow we run: pull every query where we rank position 5–15, sort by impressions, and ask what's missing from each page. With the Ahrefs MCP that's one prompt, and the answer comes from live index data plus your own connected Search Console.

Why it earns the slot

• The full dataset over one remote server — keywords, SERPs, backlinks, rank tracking, site audit, and GSC endpoints once you've linked Search Console to your project.
• OAuth sign-in on first connect. The old npm-installed local server is archived; the remote one is the way in.
• Agent-shaped answers. "Which of our competitors' pages gained referring domains this quarter" comes back as a ranked table with URLs — pulling that used to cost me an afternoon of exports and pivots.

Setup

claude mcp add ahrefs --transport http https://api.ahrefs.com/mcp/mcp

Sign in with your Ahrefs account on first connect. Paid plans (Lite and up) only.

Queries we run

• "Pull our top organic keywords where position is 5–15 and impressions are over 500, and list what each page is missing."
• "Volume and difficulty for these 12 keyword candidates, US."

The catches

• It shares your plan's API-unit budget — Lite is 100,000 units a month, minimum 50 per request, and cost scales with rows returned. We exhausted the entire month's budget in one heavy research week while writing this. The units reset monthly; your research calendar should know that.
• Paid gate. No free tier at all — the MCP starts at the $129/mo Lite plan.

4. DataFast — made for knowing which page actually made money

Link to DataFast MCP docs ↗

Analytics tells you what got traffic. DataFast tells you what got revenue — it ties Stripe payments back to the page and source that brought the customer. We used to drive its CLI from Claude Code; they now ship a proper MCP server, and I retired the CLI wrapper the same week.

Why it earns the slot

• Revenue per page, per source, per campaign — the number most marketing dashboards can't give you, because they stop at conversions.
• ~40 tools with sensible guardrails — irreversible operations require an explicit confirm flag.
• A website-scoped read-only key option, so an agent can analyse one site without holding your whole account.

Setup

claude mcp add datafast --transport http https://datafa.st/api/mcp \
  --header "Authorization: Bearer dft_YOUR_TOKEN"

The account token comes from Account Settings (shown once). Bearer-header auth means Claude Code and Claude Desktop, not claude.ai web.

Queries we run

• "Which blog posts drove paying customers in the last 90 days, and what did each visitor cohort convert at?"
• "Revenue by referrer source this month vs last."

The catches

• Bearer-only auth keeps it out of browser Claude for now.
• It's only as good as your Stripe wiring. Attribution needs the payment link set up properly per site — do that first or the answers will be confidently empty.

5. Stripe — made for revenue truth

Link to Stripe MCP docs ↗

Our weekly metrics review starts here: every Monday the same conversation asks Stripe for MRR movement — new, expansion, churn — and the answer comes from the ledger instead of a chart I'd otherwise screenshot. Setup took about a minute.

Why it earns the slot

• Official, free, OAuth at mcp.stripe.com — works in claude.ai web as a connector.
• Admin-controllable — you can enable or disable MCP access for the whole account in dashboard settings, sandbox and live managed separately.
• Pairs with everything above. Traffic from analytics, attribution from DataFast, truth from Stripe — one conversation.

Setup

claude mcp add --transport http stripe https://mcp.stripe.com/

Queries we run

• "New customers this week, with plan and amount."
• "MRR movement over the last 30 days — new, expansion, churn."

The catches

• Give it read-only scope. Stripe supports restricted keys and recommends human confirmation on write tools. An agent has no business creating refunds unsupervised — scope it like you mean it.

6. Google Search Console — made for closing the publish-and-rank loop

There's no official Google MCP server for Search Console — this is the one community-server exception on the list, and it earns the slot because the workflow it unlocks is the single best marketing loop I've seen agents run: find queries with impressions but no clicks, fix the page, watch the delta.

Why it earns the slot

• The loop. A 340-point r/n8n thread documented a solo operator going from zero to 6,000+ impressions in 30 days with exactly this: Claude reads GSC, spots pages ranking 8–15 with no clicks, rewrites titles and meta, remeasures.
• The API itself is free and read-only by nature — low blast radius.

Setup

Community wrappers like ahonn/mcp-server-gsc run locally with Google OAuth credentials you provision. Honest alternative: if you're already paying for Ahrefs, its MCP exposes your GSC data through their gsc-* endpoints once Search Console is linked — that's how ours flows, one less server to run.

Queries we run

• "Queries where we get impressions at position 5–15 but under 1% CTR, sorted by impressions."
• "Which pages gained or lost clicks after the last deploy?"

The catches

• Community-maintained means you check the repo before you trust it, and you set up Google OAuth yourself.
• Data lags a couple of days, like GSC itself. Don't let an agent conclude anything from yesterday.

7. Octolens — made for hearing Reddit before it hears you

Link to Octolens MCP ↗

Reddit is a real acquisition channel for us — founder replies in the right thread beat most paid campaigns. The hard part is knowing the thread exists. Octolens watches Reddit, Hacker News, GitHub, DEV, Stack Overflow and nine more sources for your keywords, and its MCP makes all of it queryable from the chat.

A note on the tool everyone used to name here: GummySearch shut down in November 2025. The Reddit-listening slot is genuinely open, and no other list seems to have noticed.

Why it earns the slot

• The source mix is a founder's map — Reddit plus HN, GitHub, DEV and Stack Overflow is exactly where developer-adjacent buyers talk.
• OAuth remote server at app.octolens.com/api/mcp/v2 — sign in from claude.ai, Claude Code, Cursor or ChatGPT dev mode; no keys.
• It cannot post. 14 read tools, 9 config tools, zero publish tools — the ToS-safe shape for Reddit by construction. Automated posting is how accounts get banned; listening is how threads get found.

Setup

https://app.octolens.com/api/mcp/v2

Add it as a connector and sign in. MCP is included on every plan; the 7-day trial needs no card.

Queries we run

• "Any new mentions of us or our competitors on Reddit this week, sorted by engagement?"
• "Which subreddits mention template image generation most, and what's the sentiment?"

The catches

• It listens for keywords; it doesn't browse. No "show me this week's top posts in r/SaaS" — for raw subreddit mining, the free community server jordanburke/reddit-mcp-server (maintained, Safe-Mode defaults, needs your own Reddit script-app credentials, local only) covers what Octolens doesn't.
• $159/mo after the trial — priced for teams that treat mentions as pipeline, not as curiosity.

8. Clay — made for enriching anyone you're about to talk to

Link to Clay MCP docs ↗

Clay turns "who signed up yesterday?" into "who signed up yesterday, what do their companies do, and which ones match our ICP?" — enrichment against 150+ data providers, driven from the chat. It shows up on exactly one other list, and that one is about sales tools. For marketing it's just as useful: partner research, lookalike hunting, guest-post prospecting.

Why it earns the slot

• Signup triage before outreach. I run yesterday's signups through it before writing personal welcome notes — company size, what they do, whether they're an agency — so the note can mention something real instead of "saw you signed up."
• Your workspace's custom Functions are callable — admins choose which ones the MCP exposes, per user, with credit budgets. The most granular agent-permission model on this list.
• OAuth remote at api.clay.com/v3/mcp, works as a claude.ai connector; a separate CLI variant serves Claude Code.

Setup

https://api.clay.com/v3/mcp

Add it as a connector and sign in. Admins: Functions need "Enable for MCP" toggled, and per-user MCP credit budgets live under Settings → MCP users.

Queries we run

• "Enrich this list of signups with company size, industry and tech stack, and flag the agencies."
• "Find marketing leads at companies similar to our five best customers."

The catches

• The most expensive tool on this list. MCP needs a paid plan — from $167/mo — and the free plan's credits don't unlock it.
• An agent can burn credits fast. Enrichment costs the same via MCP as in-app; set the per-user budgets Clay provides before letting an agent loose.

9. Senja — made for putting your customers' words to work

Link to Senja ↗

The social-proof category is missing from every MCP list I read, which is odd, because it's the most chat-shaped marketing job there is: "find our best quote about the API" is a search problem, and Senja's MCP makes your testimonial library searchable from the conversation.

Why it earns the slot

• Search testimonials by keyword, tag or rating and get links or embed codes for walls, widgets and forms back.
• The two-connector trick. This is where the stack composes: ask for the best 5-star quote mentioning the API, then have Orshot render it into a branded testimonial graphic — one conversation, two connectors, a social post that used to take an afternoon.
• A real free plan (up to 15 testimonials, paid from $29/mo), and the setup is literally claude.ai's connector UI with https://mcp.senja.io pasted in.

Setup

https://mcp.senja.io

Settings → Connectors → Add custom connector → paste the URL → sign in to Senja. That's the whole thing.

Queries we run

• "Find our highest-rated testimonial that mentions automation and give me the embed code."
• "Which testimonials mention a competitor by name?"

The catches

• Narrow by design — testimonials in, embeds out. No analytics, no workflow tools.
• Young server (April 2026) and MCP plan limits aren't documented yet — assume your Senja plan's limits apply.

10. Slack — made for where the reports land

Link to Slack MCP docs ↗

The quiet workhorse. Every automated report, alert and "hey, this page just converted" ping ends up in Slack, so the agent that writes those messages needs to be able to post them.

Why it earns the slot

• Official server (shipped February 2026) at mcp.slack.com/mcp, OAuth, with workspace admins in control of which MCP clients are approved.
• Where our reports already end. The weekly metrics conversation finishes by posting its summary to Slack — the query below is copied from that transcript, not invented for this post.
• Read and summarize is the underrated half: "what did I miss in #marketing this week" beats scrolling.

Setup

In claude.ai, Slack is available directly as a connector — approve it from the workspace admin side and you're done.

Queries we run

• "Post the metrics summary above to #general as a thread."

The catches

• Posting as an agent needs a norm. Decide as a team what agents may post where, or someone's channel fills with robot enthusiasm.
• Free-workspace availability is unclear — Slack's docs don't state a plan requirement either way.

Worth knowing about

Servers that didn't make the ten but earn a mention:

• HubSpot — the most-listed marketing MCP anywhere, and rightly so if you run HubSpot. We don't — a CRM that size isn't part of a two-person stack — so it stays here, unreviewed by us.
• n8n — not a data source; a server builder. Its MCP Server Trigger turns any workflow into a custom MCP endpoint, which is how you wire up tools that don't ship their own. The community server that builds n8n workflows from chat is popular for good reason; the top caveat from its own mega-thread applies — generated workflows cover the happy path.
• Notion — official hosted server, OAuth, solid if your marketing docs live there. Ours don't.
• Supabase — official OAuth server with a read_only=true flag worth copying. If your leads and content queues live in Postgres, this is your database-as-CRM entry.
• Autosend — the OAuth email server our weekly metrics report actually sends through; it left the main list only to make room for less-covered categories.
• Scheduling (Metricool / Postiz / Buffer) — the most crowded MCP category. Metricool's works on their free plan, Postiz is self-hostable with 18 networks, Buffer's is free on every plan. Pick whichever already holds your accounts.
• Firecrawl / Tavily — research and scraping. Firecrawl even has a keyless free mode now. We covered both in our marketing platforms roundup.
• For template and brand-kit workflows specifically, see our separate deep-dive on AI design tools with MCP — different job, different toolset.

What this stack costs us

The number no listicle prints. Line items, monthly, as of this writing:

• PostHog — free tier covers us; MCP endpoint itself is free
• Orshot — MCP free; renders draw plan credits (plans from $39/mo, 30 free credits to start)
• Ahrefs — $129/mo Lite, and the MCP shares its API-unit budget
• DataFast — from $9/mo, priced by monthly events; MCP access included on every plan
• Stripe, Slack, Search Console — free / included with accounts we'd have anyway
• Senja — free plan covers a small testimonial library (15 testimonials); paid from $29/mo
• Octolens — $159/mo after the 7-day trial
• Clay — from $167/mo, the priciest line here

The daily core — analytics, SEO, attribution, revenue, rendering — runs roughly $180/mo, with Ahrefs most of it. Octolens and Clay are the two big-ticket adds: another $326/mo, worth it only if listening and enrichment are jobs you'd otherwise hire for.

One warning before you connect anything

A story from r/SEO worth knowing: a user connected an SEO vendor's MCP, and when a call failed, the error message that came back contained instructions telling the assistant not to mention any competing tools. Claude flagged it to the user instead of complying.

That's the new reality of vendor-run servers: the tool responses are input to your assistant. It's why "vendor-maintained or nothing" isn't enough by itself — connect vendors you'd trust with a seat in the meeting, keep write access scoped, and read the occasional transcript.

The bottom line

You don't need ten of these. You need the few that close your loops — PostHog for traffic, DataFast and Stripe for money, Orshot for creative, in our case — and once they're wired up, most weeks I open the actual dashboards only to screenshot something.

That last loop — turning data into on-brand creative without a human in the middle — is the one we build. The MCP server connects free, and plans start at $39/mo when you outgrow the 30 free credits.

Get stuck connecting anything on this list? Hit the chat on the site — I'll help you out.