Key takeaways
- Three SEO vendors have verifiable, official MCP servers you can connect today: Ahrefs (hosted), Semrush (hosted, read-only) and Screaming Frog (local, built into SEO Spider v24.0).
- Google ships MCP for Analytics (GA4) and Chrome DevTools, but has no official Search Console MCP. You are relying on community servers for that.
- Most real constraints are practical, not technical: API-unit burn, row caps, read-only limits and security around script-execution tools.
- For several vendors (Moz, Sistrix, DataForSEO, Similarweb, Conductor, BrightEdge) I could not verify MCP status, so treat any claim about them as unconfirmed until you see docs.
- A sensible starter stack is Search Console MCP plus one market-data vendor, and nothing else until it pays back.
Why this question matters now
MCP, the Model Context Protocol, started as an Anthropic project in November 2024. By late 2026 it is plumbing. The official MCP Registry listed 47,879 server names on October 21, 2026 (47,267 active), against 1,204 at the end of 2025, according to Digital Applied's adoption tracker. The TypeScript SDK logged 231.9M npm downloads in September 2026, up from 31.3M a year earlier.
Big numbers like that say little about SEO, though. Most registry entries are not SEO tools, and a press release saying "we support MCP" is not the same as a server you can authenticate against on Monday morning. So this guide sorts SEO vendors into three buckets: shipping (I found documentation and setup steps), partial or community (works, but with real caveats), and unverified (I could not confirm either way).
One more bit of context. The 2026-07-28 specification made MCP stateless and deprecated Roots, Sampling and Logging. The NVD now lists 382 MCP-related CVEs, and in Stacklok's December 2025 survey, 64% of respondents named security as the top obstacle to production use. Keep that in mind when you read the Screaming Frog section.
The scorecard
| Vendor | Status | Hosting | Access | Main catch |
|---|---|---|---|---|
| Ahrefs | Shipping | Hosted | Every paid plan from Lite ($129/mo) | Uses API units; Lite returns up to 100 rows per request |
| Semrush | Shipping | Hosted, read-only | Semrush One Starter, One Pro+, SEO Classic Pro/Guru | 50,000 API units per plan; One Advanced needs an add-on |
| Screaming Frog | Shipping | Local | Paid licence ($279/user/year), database storage mode | Partial feature coverage; two risky script tools |
| Google Analytics (GA4) | Shipping | Official | Free | Analytics only |
| Google Chrome DevTools | Shipping | Official | Free | Runs Lighthouse, not a data source |
| Google Search Console | No official server | Community | Free or $10-19/mo wrappers | Setup friction, read-only quirks |
| Moz, Sistrix, DataForSEO, Similarweb, Conductor, BrightEdge | Unverified | n/a | n/a | I did not confirm status |
Vendors that are actually shipping
Ahrefs
Ahrefs has the cleanest story. It is an official, hosted server at api.ahrefs.com/mcp/mcp, available on every paid plan starting at Lite ($129/mo). Answer Socrates counts 20 tool groups, and Brand Radar is included. A separate performance-marketing roundup counts 112 tools in total.
Setup in Claude Code is one line:
claude mcp add ahrefs --transport http https://api.ahrefs.com/mcp/mcp
Two practical notes from the InstaWP comparison. First, calls draw down the API units in your allowance, so a chatty agent can burn through them. Second, Lite caps results at 100 rows per request, and Ahrefs does not let custom scripts call the endpoint directly. The gsc tool group is a nice touch: it can read Search Console data you have already connected inside Ahrefs, which partly papers over Google's missing official server.
Semrush
Semrush runs an official, hosted, read-only server at mcp.semrush.com/v2/mcp, streamable HTTP only. OAuth 2.1 is the default, with an API key header as fallback. Reports say it works in both Claude and ChatGPT Plus/Business. Answer Socrates counts 12 research tools, which is fewer than Ahrefs, so expect a narrower surface.
It is bundled with Semrush One Starter ($199/mo according to InstaWP), One Pro+, and SEO Classic Pro or Guru, each with 50,000 API units. One Advanced needs an extra API units package. There is a pricing conflict I could not resolve: AIclicks lists Semrush from $139.95/mo, while InstaWP says the cheapest plan that names MCP is $199/mo. Check Semrush's pricing page before you budget. Every request consumes units, and the cost varies by report and rows returned, so a broad agent prompt can get expensive fast.
Screaming Frog
SEO Spider v24.0 shipped on May 19, 2026 with a built-in MCP server (Nightwatch says "late 2025", which conflicts with the other sources, so I would go with the May 2026 date). It runs locally and exposes 29 tools: start and load crawls, export reports, inspect URLs, take screenshots, and read and write files in an allowed folder. The official guide walks through setup.
Requirements: a paid licence ($279 per user per year) and database storage mode. The free tier stays capped at 500 URLs per crawl. Coverage is partial, since not every SEO Spider feature is exposed yet, and teams wanting a headless instance would have to provision a cloud VM.
Here is the part I would not skim. Two tools run Node.js scripts and npm install. They are off by default, and Screaming Frog's own guide warns of real risk if you turn them on. Given the CVE count above, I would leave them off and treat that as a firm rule, not a suggestion.
Google: half shipped, half community
Google's official MCP products list (updated October 2, 2026) includes Analytics but not Search Console. That is a strange gap, because Search Console is the first-party data most SEOs want an agent to read. The official GA4 MCP and Chrome DevTools MCP (which runs Lighthouse) are free.
For Search Console you have three community routes:
- AminForou/mcp-gsc: open source (MIT), 20 tools, runs locally. It needs Python, a Google Cloud project and an OAuth flow per machine.
- mcp-server-gsc: lighter, but it includes a
submit_sitemaptool while requesting only read-only access, so that tool will fail. - Paid wrappers: OpenSEO at $10/mo (no Google Cloud project needed) and GSC Wizard at $19/mo (up to 10 years of history).
Google also used I/O 2026 to push AI agents inside Search itself, which makes the missing first-party Search Console server feel even more conspicuous.
Vendors I could not verify
I did not verify MCP status for Moz, Sistrix, DataForSEO, Similarweb, Conductor or BrightEdge. I also did not verify which vendors have only announced an MCP without shipping one. That is a real limit of this research, and I would rather say so than guess. If you use one of these, look for a docs page with an endpoint, an auth method and a tool list. A blog post that says "coming soon" does not count.
If you want to browse what is out there, Moz, Similarweb, Conductor and BrightEdge are all in the SurferStack directory, and the software directory at surferstack.com is a decent place to check vendor docs links.
A quick test for shipping versus announcing
I use five questions. If a vendor fails two, assume it is an announcement.
- Is there a public docs page with an endpoint URL?
- Is the auth method documented (OAuth, API key, local licence)?
- Is there a tool list, with a count you can verify?
- Is pricing or plan eligibility stated, including how usage is metered?
- Can you add it with a single command or config block today?
Ahrefs, Semrush and Screaming Frog pass all five. The community Search Console servers pass most, but with the OAuth setup burden on you.
The practical constraints that actually bite
The recurring theme in every source is not capability, it is cost and control.
- API-unit burn. Ahrefs and Semrush both meter usage. An agent that explores aggressively can chew through an allowance before you notice.
- Row caps. Ahrefs Lite returns up to 100 rows per request, which limits bulk analysis.
- Read-only limits. Semrush is read-only. The lighter Search Console package asks for read-only scope but exposes a write tool.
- Script execution. Screaming Frog's Node.js and npm tools should stay disabled.
- Local versus hosted. Screaming Frog and the Search Console community servers run on a machine you manage, which complicates team use.
Nightwatch's advice is the one I agree with: start with the free Search Console MCP, add Ahrefs or Semrush for market data, and add only the MCPs that pay back the API units they consume.
What about AI search visibility?
MCP matters on the other side of the fence too. If you are using agents to do SEO work, you also want to know whether AI systems can read your site. Promptwatch Data's AI crawler traffic report shows OpenAI at 79.8% of IP-verified AI crawler requests from Aug 31 to Sep 6, 2026, down from 94.8% from Jun 8 to Jun 14, 2026. The advice from that report is to check robots.txt, CDN and WAF rules for every AI provider, because a provider that is large in the chart but near zero in your logs probably means you are blocking it.
For tracking that, tools like Promptwatch cover AI visibility, citations and crawler logs, and it also ships a hosted MCP server with 110+ tools, so the same agent that pulls Ahrefs data can query your AI visibility data.
If you want to compare other options in that category, the GEO software directory at bestgeosoftware.com is a good starting point.
A starter stack I would actually run
| Layer | Pick | Why |
|---|---|---|
| First-party search data | Community Search Console MCP | Free, and Google has no official option |
| Site behaviour | Official GA4 MCP | Free, official |
| Market and backlink data | Ahrefs or Semrush, not both at first | Metered, so start with one |
| Technical crawling | Screaming Frog MCP | Local, licence required, scripts off |
| AI visibility | An AI visibility platform with MCP | Closes the loop on AI search |
Wire in one layer at a time, run a week of real prompts, and look at the unit consumption before adding the next. If a server does not earn its keep, remove it.
The bottom line
Three SEO vendors are verifiably shipping in 2026, and Google covers analytics but not Search Console. For everyone else, the honest answer is that I could not confirm it, and you should ask for the docs page before you plan around it. Start small, keep script tools off, and watch your API units.