The best SEO MCP servers in September 2026

What actually changed in 2026

Twelve months ago the SEO MCP landscape was community scripts on GitHub. Today the notable servers are first-party and hosted. Ahrefs, Semrush and SE Ranking all run remote servers you authorise with OAuth instead of a pasted API key. Screaming Frog put an MCP server inside the SEO Spider itself in version 24.0, released in May 2026, which made the desktop crawler agent-controllable without a wrapper. DataForSEO moved its whole API to pay-as-you-go on 1 July 2026, which quietly turned it into the cheapest way to test an agent workflow before committing to a subscription.

One gap survived all of it: Google still has no official Search Console MCP server. Google publishes an official Google Analytics MCP server under the googleanalytics org, labelled experimental, and nothing equivalent for Search Console. Every "Google Search Console MCP" you find is either a community project wrapping the public API or a commercial service. That asymmetry is worth holding onto, because it is the single most common misconception in this category and it changes who is accountable when a connector breaks.

How to judge one (six criteria that actually matter)

The shortlist at a glance

First-party performance data

This is where every SEO stack should start, because it is the only category where the numbers are measurements rather than estimates, and it is the category where an AI assistant adds the most value per token: the questions are analytical ("which pages lost non-brand clicks since the June update, and did their rankings move or their CTR?") rather than lookups.

1. GSC Wizard MCP

Good at: asking real Search Console and GA4 questions in plain language and getting a finished answer back. It is hosted, so it works in Claude, ChatGPT, Gemini, Grok, Cursor and any other MCP client without a local install, and it exposes over a hundred tools covering query and page performance, cannibalisation, content and query decay, striking-distance opportunities, indexing checks, ranking changes, forecasting, Bing Webmaster data and GA4. The important design decision is the one described in criterion 4: analysis runs server side against a ClickHouse warehouse and the model receives computed figures, not a truncated row dump. That also removes Google's 16-month history limit, since stored properties keep up to ten years.

Watch for: it is a paid product, and it is ours. If your only need is "list my top 50 queries", a free community server does that fine and you should use one. The case for a commercial server is multi-year history, analyses that would otherwise be twenty API calls stitched together by the model, and not maintaining a local process yourself.

Access: plans from €17/month with a 7-day free trial, MCP and API access included on every plan. Sign in with Google at mcp.gscwizard.com, or read the full breakdown of the GSC MCP first.

2. Community Search Console servers

Good at: free, first-party Search Console access with nothing between you and Google's API. The maintained projects worth looking at are ahonn/mcp-server-gsc, AminForou/mcp-gsc and surendranb/google-search-console-mcp. For a single site and a curious owner, this is the cheapest possible entry point and it costs nothing but an afternoon.

Watch for: three things. Setup usually means creating a Google Cloud project and downloading a service-account JSON key, which is a broader credential than an OAuth consent screen and lives in plain text on your machine. They run locally over stdio, so they do not work in ChatGPT's or Claude's web clients. And they inherit every Search Console API limit, including the 16-month history ceiling and row caps, which the model will not tell you it hit.

Access: free, MIT-style licences, your own Google credentials.

3. Google Analytics MCP (official)

Good at: the behaviour half of the picture. Google's own server exposes account and property discovery plus run_report and run_funnel_report against the GA4 Data API, so an assistant can answer "which landing pages convert" instead of only "which pages get clicks". Pairing it with a Search Console server is what turns an SEO chat from ranking trivia into revenue reasoning.

Watch for: the repository is explicitly marked experimental, it is read-only, and it runs locally against a Google Cloud project you set up yourself. GA4's API also has its own cardinality traps: ask for a page-level report on a large faceted-navigation site and you will get sampled or truncated results without a warning.

Access: free, Apache 2.0, at googleanalytics/google-analytics-mcp. GSC Wizard also exposes GA4 through the same hosted connector if you would rather not run two servers.

Third-party SEO platforms

These answer the questions your own properties cannot: what competitors rank for, who links to them, how a keyword behaves outside your site. All three of the big ones now bundle MCP access into an existing subscription, so the real decision is which platform you already pay for.

4. Ahrefs MCP

Good at: backlinks, above all. Ahrefs runs an official remote server with an OAuth consent flow, covering backlink analysis, keyword data, rank tracking, site audit and batch analysis. If your agent workflow is "find the pages linking to competitors that do not link to us, and score them", this is the one to connect.

Watch for: row caps scale with your tier, so a Lite plan returns a much shallower slice than Enterprise, and an agent asked a broad question will burn through allowance quickly. Ahrefs data is also modelled: treat traffic and volume figures as directional and never blend them into a Search Console table without labelling which column is which.

Access: included on paid Ahrefs plans from Lite upwards. See the Ahrefs MCP docs.

5. Semrush MCP

Good at: competitive research if Semrush is already your platform of record. The server is official and covers the familiar domain and keyword analytics surface.

Watch for: the cost model, which is the harshest on this list for agent use. Semrush MCP has no price of its own; it draws on the API units attached to your subscription, and different endpoints cost between roughly 1 and 100 units per line returned. A historical organic-keywords pull is one of the expensive ones. An exploratory agent conversation can consume units at a rate a human clicking through the UI never would, so cap the date ranges and row counts in your prompts rather than letting the model choose.

Access: feature of a paid Semrush subscription, metered against plan units.

6. SE Ranking MCP

Good at: breadth from one connection. SE Ranking's hosted server lists 160+ tools spanning keyword research, backlinks, domain analysis, site audits, SERP analysis, project management and AI search visibility, and MCP access is included in every subscription rather than gated behind a higher tier. If you want the fewest possible connections covering the widest surface, this is the strongest single pick.

Watch for: the flip side of 160+ tools is the context cost described below. On a client that loads every tool definition up front, a server this large can dominate your context budget before you have typed a question. Use client-side tool filtering if you have it, and do not run it alongside four other large servers.

Access: included in SE Ranking subscriptions, metered against plan API credits. See SE Ranking's MCP docs.

7. DataForSEO MCP

Good at: being the raw layer underneath much of the rest of this list. SERP results, keyword metrics, backlinks, on-page audits and an AI-optimisation module that reads AI Overview citations, all billed per request. Since DataForSEO moved to pay-as-you-go on 1 July 2026 there is no subscription to commit to: you fund a balance and calls draw it down, with SERP requests starting in fractions of a cent. That makes it the cheapest honest way to prototype an agent workflow before deciding whether it deserves a platform subscription.

Watch for: it is a data API, not an SEO product. Responses are large and structural, and the model is doing all of the interpretation, which is exactly the pattern that produces confident wrong answers. It rewards people building a pipeline and punishes people expecting an assistant.

Access: pay as you go, $50 minimum balance, self-hosted or hosted server.

Technical SEO and the live web

The most underrated category, because two of the three are free with software you already own and none of them appear on most roundups.

8. Screaming Frog SEO Spider v24

Good at: letting an assistant drive a real crawl. Version 24.0 built an MCP server into the Spider itself: you enable it in Settings > MCP Server and your client can start, pause and resume crawls, pull reports and bulk exports with field selection, inspect individual URLs and take screenshots. No CLI flags, no exported CSVs, no spreadsheet in between. For anyone whose technical audits already start with a crawl, this removes the most tedious step in the loop.

Watch for: it is local and desktop-bound by design. Client, crawler and MCP server all live on the same machine, so it cannot power a scheduled team workflow or a hosted agent. Crawls are also slow relative to an agent's patience: expect to design prompts that start a crawl, stop, and come back to the results rather than waiting inline.

Access: no extra cost with a paid SEO Spider licence on v24.0 or later.

9. Chrome DevTools MCP

Good at: the thing every Core Web Vitals conversation is missing, which is a measurement. Google's official server exposes DevTools itself: performance traces, network inspection, console access, CPU and network throttling. An assistant can load a page, record a trace, read the Core Web Vitals and the long tasks behind them, suggest a fix and then re-measure. That measure-fix-remeasure loop is genuinely new, and it is free.

Watch for: it measures lab data on your machine and your connection. That is a diagnostic, not what Google ranks on, which is field data from real Chrome users. Use it to find the cause of a regression, then confirm the fix in CrUX field data. It also drives a real browser, so treat it as you would any automation touching logged-in sessions.

Access: free, from the Chrome team.

10. Firecrawl MCP

Good at: turning arbitrary pages into clean markdown an assistant can reason over. Scrape, crawl, map and search, priced at one credit per page for the core endpoints. It is the standard answer for competitor content analysis, SERP-result summarisation and anything where you need the text of pages you do not own.

Watch for: credits disappear faster than expected when an agent decides to crawl a site rather than fetch three URLs, and premium modes cost several times the base rate. Constrain scope in the prompt. There is also an ethical and legal dimension to scraping at volume that a tool call makes very easy to skip past.

Access: free tier to start, paid tiers from around $16/month.

Three failure modes nobody puts in the roundup

The tool-list tax

Every connected server injects its complete tool list, with descriptions and JSON schemas, into the model's context before you ask anything. One large server is fine. Five is not: the definitions alone can consume tens of thousands of tokens, which shrinks the room left for actual data and measurably increases wrong-tool selection, because the model is choosing from a menu of four hundred near-synonymous options. The symptoms look like model stupidity ("why did it call the wrong report?") and are actually a configuration problem. Connect two or three servers per workspace, matched to the job in front of you, and disable the rest. This is also why raw tool count is a bad buying signal: what matters is whether one call answers your question or you need twelve.

Blended data with no provenance

Ask an assistant with four servers connected for "our top opportunities" and you will get a table mixing Search Console clicks (measured, yours, complete), Ahrefs traffic estimates (modelled, third party) and DataForSEO volume (modelled, different methodology) in adjacent columns with no indication that they are different kinds of number. Nothing in the protocol carries provenance, so the model flattens it. The fix is a prompt habit, not a tool: require the source and date range per column, and never let a modelled figure sit unlabelled next to a measured one in something you will send to a client.

Row dumps and confident arithmetic

The most expensive failure is silent. A server returns 25,000 rows, the client truncates the response to fit the context window, and the model computes a total over whatever survived, then reports it with the same confidence it would report a real figure. You will not see an error. The defences are to prefer servers that aggregate server side, to ask explicitly for the row count behind any total, and to sanity-check one number per report against the source UI. If a figure cannot be traced back to a named tool and a date range, do not put it in a deck.

Three stacks that actually work

Connecting your first one

Whichever you pick, the shape is the same. A hosted server needs a URL and an authorisation, and takes about two minutes; a local one needs Node or Python, a credential file and a client config block, and takes an afternoon the first time. If you are starting with Search Console data, we have step-by-step guides for Claude, ChatGPT, Gemini and Grok, plus a wider comparison of five ways to get Search Console into ChatGPT if you want to weigh the DIY route against a hosted one before committing.

Frequently asked questions