# 14 live-tested MCP servers for marketing, SEO, and AI visibility (2026)

> We probed 14 marketing and SEO MCP servers and 911,413 AI answers: MCP mentions grew +127% on ChatGPT. Compare live endpoints, auth, and context overhead.

HTML: https://parse.gl/blog/best-mcp-servers-for-marketing-and-seo · Site index: https://parse.gl/llms.txt · Published: 2026-11-20 · Updated: 2026-11-21

Most "best MCP server" roundups copy README blurbs without sending a single JSON-RPC packet. On November 20, 2026, we probed 14 live marketing, SEO, analytics, CRM, and web-data MCP servers directly over Streamable HTTP `initialize`, `tools/list`, RFC 9728 OAuth protected-resource metadata checks, and GitHub API inspections. Start with **Parse MCP** for keyless 90-day AI visibility benchmarks, **GA4 and GSC MCPs** for zero-cost organic analytics, **Ahrefs or Semrush** if you already hold paid SEO seats, and **Firecrawl** when an assistant needs clean Markdown from stubborn HTML.

We tested the endpoints and repositories in this guide directly on November 20, 2026, and paired that live engineering benchmark with our 911,413-answer study, [How AI recommends MCP and agent-native tools](https://parse.gl/research/how-ai-recommends-mcp-and-agent-native-tools) (September 1 to November 19, 2026). Parse tracks AI visibility across **853,414 active brands** and **1,774 markets**, backed by **744,460** counted-engine answers (`378,499` ChatGPT Search and `365,961` Google AI Mode) and **4,053,878** citations across **73,847** buyer questions in our 90-day public MCP snapshot (August 23 to November 20, 2026).

- **Live marketing, SEO, analytics, ops, and web-data MCP servers verified by JSON-RPC and GitHub checks (Nov 20, 2026):** 14 (Parse Live Probe)
- **Jump in ChatGPT Search MCP mention share from Sep (0.660%) to Nov 2026 (1.499%):** +127.12% (Parse, Sep-Nov 2026)
- **Of 6,292 MCP mentions across 911,413 organic AI answers that surfaced unprompted (5,975 of 6,292):** 95.0% (Parse, Sep-Nov 2026)
- **Estimated schema tokens for Parse MCP's 6 unauthenticated tools vs 450 tokens for Cloudflare Docs (2 tools):** 5,380 (Parse JSON-RPC Probe)

## Why marketers need an MCP shortlist backed by live probes

MCP adoption inside buyer recommendations is moving faster than explicit MCP search volume. Across `130,776` active organic buyer questions in Parse's corpus, only `18` explicitly named MCP (`3,146` asked for MCP, AI agents, Claude/Cursor, headless setups, APIs/SDKs, or CLI workflows). Yet across `911,413` September 1 to November 19, 2026 answers (`463,371` ChatGPT Search, `440,174` Google AI Mode, `6,780` Claude reference answers, and `1,088` Perplexity), **6,292 answers** mentioned MCP anyway, with **94.96%** (`5,975` of `6,292`) surfacing unprompted.

ChatGPT Search drove the sharpest surge, more than doubling its MCP mention share (`+127.12%`) from `0.660%` in September (`1,063` of `161,053` answers) to `1.499%` in November (`1,711` of `114,137` answers), putting it `2.72×` ahead of Google AI Mode's `0.552%` (`595` of `107,732` answers). Teams wiring marketing workflows into Claude Code, Cursor, or ChatGPT face messy vendor docs, because old guides still list dead URLs and archived repos.

Our November 20 live probes caught three recurring traps:

- **Dead docs URLs:** Legacy Ahrefs docs (`docs.ahrefs.com/docs/mcp/reference/introduction`) return `404`; canonical docs sit at `https://docs.ahrefs.com/en/mcp`.
- **Broken path guesses:** `mcp.hubspot.com/mcp` returns `404`; HubSpot's endpoint is `https://mcp.hubspot.com` (`https://developers.hubspot.com/mcp`).
- **Deprecated local repos:** `makenotion/notion-mcp-server` (`4,719` stars) now redirects users to Remote Notion MCP at `https://mcp.notion.com/mcp`.

## Which of the 14 live-tested MCP servers fits each marketing job?

No single MCP server covers search telemetry, product analytics, web extraction, and sprint ops. Split your stack by job so assistants pull exact missing data without loading unused schemas.

The table below lists all 14 MCP servers probed on November 20, 2026, with verified endpoints, transport and auth models, and pricing.

| Server & category                | Verified endpoint or repo                                                    | Transport & auth model                                                                | Key capabilities & pricing                                                                                                         |
| -------------------------------- | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Parse MCP** (AI visibility)    | `https://agent.parse.gl/mcp` (alias `mcp.parse.gl/mcp`)                      | Streamable HTTP; keyless public view (5 read tools, 6 listed unauth) + Bearer / OAuth | 16 canonical tools; free 90-day index + weekly check + `$5` signup credit; `$0.01`/live check or fetch; no subscription            |
| **Ahrefs MCP** (SEO & backlinks) | `https://api.ahrefs.com/mcp/mcp`                                             | Streamable HTTP (`?tools=` filter); OAuth 2.0 (RFC 9728, `apiv3-mcp`)                 | 10 groups (`site-explorer-*`, `keywords-explorer`, `brand-radar-*`, `gsc`); paid Ahrefs plan (Lite+) + API units                   |
| **Semrush MCP** (SEO & traffic)  | `https://mcp.semrush.com/v2/mcp`                                             | Streamable HTTP; OAuth 2.0 (`mcp.access`) or Bearer API key                           | Keywords, traffic/backlinks, AI Visibility / Prompt Research, rank tracking, audit; paid Semrush / API plan                        |
| **GA4 MCP** (Web analytics)      | `googleanalytics/google-analytics-mcp` (`3,838` stars)                       | Local stdio (`pipx analytics-mcp`) or HTTP; Google Cloud ADC / read-only OAuth        | `run_report`, `run_funnel_report`, `run_conversions_report`, `run_realtime_report`; free Apache-2.0                                |
| **GSC Community MCPs** (Search)  | `AminForou/mcp-gsc` (`2,249` stars); `crunchtools/mcp-google-search-console` | Local stdio (`npx`/`uvx`/Python); Google OAuth 2.0 or service account                 | 20 tools (`get_search_analytics`, `compare_search_periods`, `inspect_url_enhanced`, `manage_sitemaps`); MIT / AGPL-3.0             |
| **HubSpot MCP** (CRM & ops)      | `https://mcp.hubspot.com`                                                    | Streamable HTTP + local CLI; OAuth 2.0 (RFC 9728)                                     | Read/write contacts, companies, deals, tickets, engagements; included in HubSpot plans                                             |
| **PostHog MCP** (Product & LLM)  | `https://mcp.posthog.com/mcp`                                                | Streamable HTTP; OAuth 2.0 or API token (`160` scopes verified)                       | Funnels, cohorts, feature flags, A/B tests, replays, LLM analytics; free tier + usage-based                                        |
| **Notion MCP** (Docs & wikis)    | `https://mcp.notion.com/mcp`                                                 | Streamable HTTP (replaces local repo); OAuth 2.0                                      | Semantic search, Markdown-native page reads/edits, database queries; included in Notion plans                                      |
| **Slack MCP** (Team alerts)      | `https://docs.slack.dev/ai/slack-mcp-server/`                                | Remote HTTP/SSE; OAuth 2.0 / Dynamic Client Registration                              | Search messages/files, post updates, canvases, lists; included with admin MCP approval                                             |
| **Linear MCP** (Marketing ops)   | `https://mcp.linear.app/mcp`                                                 | Streamable HTTP; OAuth 2.0 (`read`, `write`)                                          | Search, create, and update issues, projects, cycles, docs, comments; included in Linear plans                                      |
| **Stripe MCP** (Revenue data)    | `https://mcp.stripe.com`                                                     | Streamable HTTP + `stripe agent setup`; OAuth 2.0 or restricted key (`mcp`)           | Customers, invoices, subscriptions, payments, balances, Stripe docs; free with Stripe account                                      |
| **Firecrawl MCP** (Extraction)   | `https://mcp.firecrawl.dev/mcp` (`7,872` stars)                              | Streamable HTTP + local `npx firecrawl-mcp`; Firecrawl API key                        | `firecrawl_scrape`, `firecrawl_map`, `firecrawl_crawl`, `firecrawl_search`, `firecrawl_interact`, `firecrawl_parse`; MIT + credits |
| **Playwright MCP** (Browser QA)  | `microsoft/playwright-mcp` (`39,934` stars)                                  | Local stdio / SSE (`npx @playwright/mcp@latest`); no external auth                    | `65+` `browser_*` tools using accessibility snapshots; free Apache-2.0                                                             |
| **Cloudflare Docs MCP** (Ref)    | `https://docs.mcp.cloudflare.com/mcp`                                        | Streamable HTTP (SSE); public read-only, zero auth                                    | `2` tools (`search_cloudflare_documentation`, `migrate_pages_to_workers_guide`); free public endpoint                              |

Treat that matrix as an architecture menu rather than a list to install all at once. For [Claude Code or Cursor AI visibility workflows](https://parse.gl/blog/claude-code-and-cursor-ai-visibility-workflows), pairing one public visibility server (`Parse`), one owned analytics source (`GA4` or `GSC`), and one Markdown fetcher (`Firecrawl`) covers most weekly work.

## How auth models, OAuth scopes, and schema bloat affect agent context

Connecting five heavy MCP servers to one coding agent can wreck performance before your first prompt finishes. Two technical constraints decide whether an MCP stack stays fast or stalls out: **authentication mechanics** and **`tools/list` schema token footprint**.

On the auth front, only **Parse MCP** (public index view) and **Cloudflare Docs MCP** answered our unauthenticated HTTP `POST` JSON-RPC `initialize` + `tools/list` probe with HTTP `200`. Every SaaS ops, CRM, and paid SEO endpoint (`Ahrefs`, `Semrush`, `HubSpot`, `PostHog`, `Notion`, `Linear`, `Stripe`) returned HTTP `401` advertising RFC 9728 OAuth protected-resource metadata (`/.well-known/oauth-protected-resource`).

Scope discipline varies wildly across those OAuth servers. **Linear MCP** keeps its surface crisp with two scopes (`read` and `write`). **PostHog MCP**, by contrast, advertises **160 granular OAuth scopes** (`insight:read`, `experiment:write`, `llm_analytics:read`, `web_analytics:read`) so teams can lock read-only analytics tokens away from billing or feature-flag mutations. Always audit scopes before giving an autonomous agent write access to **HubSpot**, **Notion**, or **Slack**.

Schema size hits even harder on coding agents. We measured the exact `tools/list` JSON-RPC byte and token footprint (`characters / 4`) on every unauthenticated endpoint and checked vendor guidance across heavy tool suites.

**450 tokens**
**Minimal remote (`Cloudflare Docs MCP`).** Exposes `2` tools in `1,801` bytes (`450` est. tokens). Zero auth and tiny context overhead for docs lookup.
**5,380 tokens**
**Scoped public analytics (`Parse MCP`).** Unauthenticated `tools/list` exposes `6` tools (`check_brand`, `resolve_ids`, `query_metrics`, `search_answers`, `search_cited_pages`, `get_brief`) in `21,520` bytes (`5,380` est. tokens; OpenAPI is `18,274` bytes).
**65+ tools**
**Heavy browser suite (`Playwright MCP`).** Exposes `65+` `browser_*` tools. Microsoft's own README warns coding agents to prefer Playwright `CLI+SKILLs` when large MCP schemas and accessibility trees strain context windows.

Notice how smart servers solve schema sprawl. **Ahrefs MCP** lets you append `?tools=` query parameters to restrict the endpoint to specific tool groups (such as `brand-radar-simple` or `keywords-explorer`) rather than loading all 10 groups at once. **Google Search Console** still has no Google-hosted remote MCP server, so teams choose between the `20`-tool MIT `AminForou/mcp-gsc` server (`2,249` stars, updated November 6, 2026, defaulting to read-only OAuth unless `GSC_ALLOW_DESTRUCTIVE=true` is set) or `crunchtools/mcp-google-search-console` (AGPL-3.0, also supporting Streamable HTTP container mode). Meanwhile, [Firecrawl MCP](https://parse.gl/blog/make-your-site-readable-for-ai-agents) (`7,872` stars) compresses multi-hundred-kilobyte HTML pages into clean Markdown before text ever touches your model context.

## How AI models recommend AI visibility and marketing MCP tools today

We make Parse, and we don't hide behind cherry-picked screenshots when evaluating our own category. Inside our [911,413-answer MCP study](https://parse.gl/research/how-ai-recommends-mcp-and-agent-native-tools), we compared `85` standard AI-visibility buyer questions (`2,391` answers across ChatGPT Search, Google AI Mode, and Perplexity) against `5` explicit MCP/agentic AI-visibility prompts (`158` answers: `79` on ChatGPT Search and `79` on Google AI Mode).

The split between standard buyer prompts and MCP-focused prompts is dramatic, and the differences between ChatGPT Search and Google AI Mode are even sharper.

| Platform                            | Standard AI visibility (`2,391` ans) | ChatGPT Search MCP prompts (`79` ans) | ChatGPT `#1` wins & avg pos | Google AI Mode MCP prompts (`79` ans) |
| ----------------------------------- | -----------------------------------: | ------------------------------------: | --------------------------- | ------------------------------------: |
| **LLM Pulse** (`llmpulse.ai`)       |                                1.21% |                                84.81% | 11 `#1` picks (avg 4.45)    |               27.85% (`6` `#1` picks) |
| **Peec AI** (`peec.ai`)             |                               49.85% |                                70.89% | 8 `#1` picks (avg 4.32)     |               46.84% (`3` `#1` picks) |
| **Otterly AI** (`otterly.ai`)       |                               51.07% |                                62.03% | 6 `#1` picks (avg 4.67)     |               45.57% (`0` `#1` picks) |
| **SE Ranking** (`seranking.com`)    |                               10.66% |                                60.76% | 2 `#1` picks (avg 8.04)     |               45.57% (`5` `#1` picks) |
| **Ahrefs** (`ahrefs.com`)           |                               36.89% |                                54.43% | 0 `#1` picks (avg 7.91)     |               10.13% (`3` `#1` picks) |
| **Cite42** (`mcp.cite42.dev`)       |                     <0.2% (`<5` ans) |                                41.77% | 4 `#1` picks (avg 6.42)     |                         1.27% (1 ans) |
| **Scrunch** (`scrunch.com`)         |                               21.83% |                                37.97% | 0 `#1` picks (avg 6.71)     |                5.06% (`0` `#1` picks) |
| **TryProfound / Profound**          |                      40.28% / 11.25% |                       32.91% / 17.72% | 1 / 0 `#1` picks            |                       11.39% / 34.18% |
| **Promptwatch** (`promptwatch.com`) |                                6.65% |                                17.72% | 3 `#1` picks (avg 5.07)     |               11.39% (`0` `#1` picks) |
| **Parse** (`parse.gl`)              |                                0.33% |                                13.92% | 7 `#1` picks (avg 1.82)     |                0.00% (`0` `#1` picks) |
| **Semrush** (`semrush.com`)         |                               48.68% |                                 6.33% | 0 `#1` picks (avg 8.80)     |                8.86% (`3` `#1` picks) |

Look closely at what that table teaches both buyers and product marketers:

- **Standard prompts stay sticky around early category incumbents.** On the `85` generic AI-visibility prompts, `Otterly AI` (`51.07%`), `Peec AI` (`49.85%`), `Semrush` (`48.68%`), `TryProfound` (`40.28%`), and `Ahrefs` (`36.89%`) take the lion's share of mentions, while Parse sits at just `0.33%` (`8` of `2,391`).
- **MCP prompts reward documentation, GitHub, and fast-moving specialists on ChatGPT Search.** On the `5` MCP-focused AI-visibility prompts on ChatGPT Search, `LLM Pulse` surges from `0.41%` (`5` of `1,208` standard ChatGPT answers) to `84.81%`, `Cite42` jumps to `41.77%`, and **Parse jumps 42× to `13.92%` (`11` of `79`), winning `#1` in `7` of `11` appearances at a `1.82` average rank** because ChatGPT cites `parse.gl` technical docs directly.
- **Google AI Mode looks elsewhere.** On those exact same `79` Google AI Mode answers, Parse earned **zero** mentions, while `Radarkit` won `18.99%` (`9` `#1` picks) and `Peec AI`, `SE Ranking`, and `Otterly AI` led. Why? Across all `58,092` citation links on MCP-mentioning answers, ChatGPT Search leaned `2.4×` harder on Docs/Dev pages (`30.73%` vs `12.65%`) and `github.com` (`4.01%` vs `2.40%`), whereas Google AI Mode cited **YouTube (`9.32%` vs `0.00%`)**, **Reddit (`3.47%` vs `0.01%`)**, and **MCP registries like `mcpmarket.com` and `mcpservers.org` (`0.79%` vs `0.02%`)**.

If you want deeper comparison across AI-visibility vendors specifically, pair this 14-server buyer's guide with our [seven headless AI visibility platforms comparison](https://parse.gl/blog/best-headless-ai-visibility-platforms), our [ChatGPT connectors guide](https://parse.gl/blog/best-chatgpt-plugins-ai-visibility), and our [GitHub and DevRel AI visibility playbook](https://parse.gl/blog/devrel-and-github-ai-visibility-playbook).

## Which three marketing MCP stacks work without overloading your agent

Instead of wiring 14 servers into one config, run three focused profiles:

1. **Zero-cost SEO & AI visibility audit:** Pair **Parse MCP** (`https://agent.parse.gl/mcp`, keyless public index + `$5` signup credit), **GA4 MCP**, and **GSC MCP** (`AminForou/mcp-gsc`, read-only OAuth) for 90-day AI answers, organic queries, and conversions without subscriptions.
2. **Technical SEO & Markdown debugging:** Pair **Parse MCP** with **Firecrawl MCP** (`https://mcp.firecrawl.dev/mcp`) to compare AI-cited gaps against live extracted Markdown, using **Playwright CLI** for JS pricing checks.
3. **Growth ops loop:** Pair **Parse MCP** with **Linear MCP** (`https://mcp.linear.app/mcp`) or **Notion MCP** (`https://mcp.notion.com/mcp`) and **Slack MCP**, adding **Ahrefs MCP** (`?tools=brand-radar-simple,keywords-explorer`) or **Semrush MCP** only when keyword or backlink queries demand it.

Here is a lean `.mcp.json` starter for Cursor or Claude Code combining Parse, Firecrawl, and GSC:

```json
{
  "mcpServers": {
    "parse-agent": {
      "url": "https://agent.parse.gl/mcp",
      "headers": {
        "Authorization": "Bearer ${PARSE_API_KEY}"
      }
    },
    "firecrawl": {
      "url": "https://mcp.firecrawl.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${FIRECRAWL_API_KEY}"
      }
    },
    "gsc": {
      "command": "uvx",
      "args": ["mcp-gsc"]
    }
  }
}
```

For quick keyless discovery, omit the `Authorization` header on `parse-agent` and `check_brand`, `resolve_ids`, `query_metrics`, `search_answers`, and `search_cited_pages` still answer immediately.

## Run this workflow with your agent

Before signing an annual contract for any MCP visibility or SEO suite, test your own category inside Claude Code, Cursor, Codex, or ChatGPT using [Parse MCP](https://parse.gl/mcp) (`https://agent.parse.gl/mcp`). Reading the 90-day public index and recording notes with `log_work` is free, and live page inspections (`fetch_live_pages`) or fresh checks (`ask_ai_engines`) quote at `$0.01` inside a monthly cap you control.

```text
Run get_brief, then check_brand for "<our domain>" and query_metrics over the last 90 days
across ChatGPT Search and Google AI Mode.
Call search_cited_pages and search_answers to list the top 10 third-party pages citing
competitors on our primary buyer topics while skipping us.
If we have GA4 or GSC connected, cross-check organic clicks and AI-referral conversions
on those matching landing pages, then save a prioritized sprint plan with log_work.
```

Your assistant calls `check_brand`, `query_metrics`, `search_cited_pages`, `search_answers`, `get_brief`, and `log_work` in sequence, storing an audit trail any teammate can reopen with `list_work` or verify next month via `track`. Explore [market research workflows](https://parse.gl/use-cases/research-a-market), [competitor comparison workflows](https://parse.gl/use-cases/compare-competitors), or review transparent [pay-as-you-go pricing](https://parse.gl/pricing) before adding credits.

## Sources

- [How AI Recommends MCP and Agent-Native Tools (Parse)](https://parse.gl/research/how-ai-recommends-mcp-and-agent-native-tools)
- [Parse MCP endpoint and 16-tool catalogue](https://parse.gl/mcp)
- [Ahrefs MCP documentation](https://docs.ahrefs.com/en/mcp)
- [Semrush MCP server documentation](https://www.semrush.com/mcp)
- [Official Google Analytics MCP server (GitHub)](https://github.com/googleanalytics/google-analytics-mcp)
- [Google Search Console MCP server (AminForou, GitHub)](https://github.com/AminForou/mcp-gsc)
- [HubSpot MCP documentation](https://developers.hubspot.com/mcp)
- [PostHog Model Context Protocol documentation](https://posthog.com/docs/model-context-protocol)
- [Remote Notion MCP documentation](https://developers.notion.com/docs/mcp)
- [Official Slack MCP server documentation](https://docs.slack.dev/ai/slack-mcp-server/)
- [Linear MCP documentation](https://linear.app/docs/mcp)
- [Stripe MCP documentation](https://docs.stripe.com/mcp)
- [Official Firecrawl MCP server (GitHub)](https://github.com/firecrawl/firecrawl-mcp-server)
- [Official Playwright MCP server (Microsoft, GitHub)](https://github.com/microsoft/playwright-mcp)
- [Cloudflare Model Context Protocol documentation](https://developers.cloudflare.com/agents/model-context-protocol/)

## For agents

- Any brand's shares and rivals, with 95% ranges: `https://agent.parse.gl/v1/tools/check_brand?subject=%3Cbrand-domain%3E`
- Search the index: `https://parse.gl/api/public/search?q=<words>`

Reuse: Figures and tables on this page are free to republish with attribution: a link to https://parse.gl/blog/best-mcp-servers-for-marketing-and-seo beside them. A standard followed link (dofollow) is preferred.

- No account: Public figures and up to 5 examples per list, about 120 brands a day per address.
- Free account: $5 in credit, your brand's first check (20 buyer questions) and a free weekly check.
- After your first top-up: Exports and deeper search results. The first top-up starts at $5.
- Live checks: $0.01 per question per engine ($0.05 on Gemini and Claude).
- Full public answers and pages: 25 free per day, then $0.005 each.
- Public answers older than 90 days: $0.001 each the first time your workspace counts or lists one, then yours.
- An agent can save work before signup: `POST https://agent.parse.gl/v1/workspaces`
- Connect an assistant: `https://agent.parse.gl/mcp`

[Prices](https://parse.gl/pricing.md) · [Map of the site](https://parse.gl/llms.txt)
