SEO MCP Servers: 5 Providers Compared and What They Automate

Every major SEO platform shipped an SEO MCP server in the last year. Semrush, Ahrefs and DataForSEO all have one. So does OpenSEO.

I connected all four. Some are excellent. One bills you 50 API units for a single question.

This is the part nobody tells you: an agent is a terrible judge of what a query costs. It will happily burn 5,000 units exploring a hunch.

So this guide covers two things. Which providers actually have working servers, and which SEO operations are worth automating once you are connected.

I have skipped the vendor marketing. Every endpoint below is from official documentation, and I have flagged the ones that do not exist.

What Is an SEO MCP Server?

An SEO MCP server exposes a platform's SEO data as tools an AI model can call directly. No CSV exports, no dashboard pivoting.

If you are new to the protocol itself, start with what the Model Context Protocol is. The short version: MCP is a standard way for a model to discover and call external tools.

The practical difference is chaining. A keyword tool answers one question per export.

Through MCP, a model can discover keywords, check which ones you rank for, pull the live SERP for the promising ones, and cross-reference Search Console — in a single request.

The 5 SEO MCP Servers Worth Knowing in 2026

Here is the honest comparison. Endpoints are quoted from each vendor's own documentation, not from a directory listing.

1. Semrush MCP Server

Semrush has the broadest tool surface of any SEO MCP server. The endpoint is https://mcp.semrush.com/v2/mcp over streamable HTTP.

OAuth is the default. No headers needed — the agent registers itself and redirects you to Semrush login.

For headless clients, use an API key: Authorization: Apikey YOUR_API_KEY. Note the format is Apikey, not Bearer. That trips people up.

Tools it exposes: domain_overview, organic_research, keyword_research, competitors_research, backlinks_research, audience_research, traffic_overview, paid_search_research, shopping_research, position_tracking, site_audit and projects.

Two of those matter more than the rest. get_report_schema and execute_report let the model discover a report shape before calling it.

That is unusually well designed. Most SEO servers make the model guess parameters.

The catch is the plan requirement. You need Semrush One Starter, Pro+, or SEO Classic Pro/Guru, which includes 50,000 units.

2. Ahrefs MCP Server

Ahrefs runs a remote server at https://api.ahrefs.com/mcp/mcp over streamable HTTP, with OAuth.

Add it to Claude Code in one line:

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

Skip the npm package. The @ahrefs/mcp repo was archived on 24 February 2026. Its own README says it does not work with MCP keys and is outdated.

I wasted twenty minutes on that before reading the archive notice. Use the remote endpoint.

Ahrefs is the one to watch on cost. One API call costs a minimum of 50 units, more for complex requests.

Monthly allowances: Lite gets 100,000 units, Standard 400,000, Advanced 1,000,000, Enterprise 2,000,000.

Do the arithmetic. On Lite, that is 2,000 calls a month at absolute best. An agent exploring a competitor set can spend fifty calls answering one question.

3. DataForSEO MCP Server

DataForSEO is the one I reach for when I want raw data without a platform subscription. The endpoint is https://mcp.dataforseo.com/mcp, with an SSE variant at /http.

Auth is HTTP Basic — your API login and password, base64-encoded. Less elegant than OAuth, but trivial in a headless environment.

Seven APIs are exposed as tools: SERP, Keywords Data, Labs, Backlinks, On-Page, Business Data and Domain Analytics.

The pricing is the differentiator. The server itself is free and open source; you pay only for data.

Roughly $0.024 for 100 related keywords, and from $0.002 per live SERP query. There is a $1 trial credit, then a $50 minimum top-up.

Per-query pricing suits agents far better than unit allowances. You can watch spend accumulate in real terms instead of guessing what a unit is worth.

Prefer running it locally? The config is standard:

{
  "mcpServers": {
    "dataforseo": {
      "command": "npx",
      "args": ["-y", "dataforseo-mcp-server"],
      "env": {
        "DATAFORSEO_USERNAME": "your_api_login",
        "DATAFORSEO_PASSWORD": "your_api_password"
      }
    }
  }
}

4. OpenSEO MCP Server

OpenSEO runs at https://app.openseo.so/mcp over streamable HTTP. OAuth by default, or Authorization: Bearer oseo_YOUR_KEY for headless clients.

It covers the usual organic set — keyword metrics, live SERPs, competitor comparison, backlinks and Search Console performance.

Two things make it worth a look. The local SEO coverage is unusually deep for a general platform.

Google Business Profile audits, Maps rank grids around a location, review collection, and business category lookups. Most competitors treat local as an afterthought.

The second is project context. Your business, goals and competitor set persist across calls, so the model stops re-asking who you are.

You can see the full tool list on our OpenSEO MCP server page, or start from the OpenSEO research agent template — it comes pre-wired with a system prompt that constrains queries before they run.

5. Google Analytics MCP Server

Google publishes an official GA4 server at github.com/googleanalytics/google-analytics-mcp. Set expectations low.

It is labelled experimental, runs locally only, and is read-only. There is no hosted endpoint.

Three tools: get_account_summaries, run_report and run_realtime_report. That covers reporting and nothing else.

It cannot edit your GA configuration. For read-only analysis that is fine, and honestly correct.

Why Google Search Console Has No Official MCP Server

This surprises people, so I will be blunt. As of August 2026, Google does not publish an official Search Console MCP server.

Google has shipped more than 50 MCP servers — BigQuery, Cloud Run, Firestore, Maps, Drive, Gmail, Calendar. Search Console is not among them.

Google Analytics having one is why people assume GSC does too. Only GA4 got the official treatment.

You have three options:

• A community server. Several wrap the official Search Console API. Read the source before handing over OAuth credentials to your entire search data
• Build your own on the Search Console API. It is a small API and a reasonable weekend project
• Use a platform that already integrates GSC. OpenSEO and Semrush both pull Search Console data through their own connectors

The third option is what I do. It avoids a second OAuth grant against a Google property.

If you do run a community server, scan it before you connect it. A server holding your Search Console OAuth token deserves scrutiny.

SEO Operations You Can Actually Automate

This is the part that matters. Not every SEO task is worth handing to an agent.

The ones that pay off share a shape: multi-step, tedious, and requiring data from more than one place.

Keyword Research to Content Brief

The classic chain. Discover keywords, filter by difficulty, check which ones you already rank for, pull the SERP for survivors.

Doing that by hand is four exports and a spreadsheet. As one prompt, it is about ninety seconds.

A prompt that works:

Find 20 keywords related to "mcp server testing" with volume
above 100 and difficulty under 30. For each, check whether
my domain already ranks. For the five best gaps, pull the
live SERP and summarise what the top 3 results cover.

Constrain it. Without the numeric filters, the model explores and your unit balance evaporates.

SERP Competitor Teardown

Ask which competitors appear across a keyword set, and what they have in common. Semrush's competitors_research handles this directly.

The useful output is not the list. It is the pattern across the list — shared subtopics, content format, page depth.

Rank Tracking and Regression Alerts

Position tracking is available in Semrush (position_tracking) and OpenSEO. The automation is not the tracking, it is the triage.

Ask for positions that dropped more than three places this week, then have the model pull the current SERP for each and guess why.

That second step is where an agent earns its cost. A dashboard shows you the drop; the model tells you a new competitor entered.

Backlink Monitoring

Backlink data is available from Semrush (backlinks_research), Ahrefs, DataForSEO and OpenSEO. Ahrefs remains the deepest index.

Worth automating: new and lost referring domains week over week, with the model classifying whether losses matter.

Not worth automating: bulk link auditing. The unit cost will exceed the value.

Technical Audit Triage

DataForSEO's On-Page API and Semrush's site_audit both surface technical issues. Agents are good at the sorting, not the finding.

Feed it the audit and ask which issues actually affect indexation, ordered by how many pages each touches.

Local SEO and Google Business Profile

OpenSEO and DataForSEO's Business Data API both cover this. The automatable operation is the rank grid.

Check Maps position across a geographic grid, then ask where coverage is weakest and which competitor owns those cells.

Chaining Two Servers — The Real Unlock

Here is what I did not expect. The interesting workflows use two servers at once.

Research in DataForSEO because queries are cheap. Verify the shortlist in Ahrefs because the index is better.

Or pull rankings from an SEO platform and page data from your own database, and ask which ranking pages have stale content.

MCP clients merge tools from multiple servers into one list. The model picks across all of them without knowing they are separate.

You can test a multi-server setup free in the browser. Test any MCP server free →

How to Pick an SEO MCP Server

Four questions, in order:

1. Do you already pay for one of these? Then use it. The MCP server is included, not an upsell
2. Do you need per-query cost visibility? DataForSEO. Unit allowances hide spend until the balance is gone
3. Is backlink depth the priority? Ahrefs, and budget for the 50-unit floor
4. Is local SEO a real part of the job? OpenSEO or DataForSEO's Business Data API

If you are starting cold with no subscription, DataForSEO's $1 trial credit is the cheapest way to find out whether any of this fits your workflow.

The Credit Problem Nobody Warns You About

Every guide skips this, so here it is plainly. Agents are bad at cost discipline.

A human runs one keyword export and works with it. A model runs four, decides the fourth was wrong, and runs three more.

On Ahrefs Lite, that exploration pattern can spend 350 units answering a question worth 50.

Three things that help:

• Put numeric limits in the prompt. "Top 20", "under difficulty 30", "last 28 days" — every constraint is a call the model does not make
• Use a cheaper model for simple fetches. A single metric lookup does not need a frontier model. Compare the same prompt across models before committing
• Watch the tool calls. Most clients hide them. If you cannot see which tool ran and what it returned, you cannot tell why a run cost triple

That last point is why I test SEO servers in a client that shows raw JSON before wiring them into anything scheduled.

How MCP Playground Can Help

Before you connect an SEO MCP server to a paid workflow, it is worth seeing exactly what it does. MCP Agent Studio connects any of these endpoints in the browser and shows every tool call with its full JSON input and output — so you can see which tool the model reached for, what arguments it built, and how many calls a question actually costs. You can run the same prompt across 60+ models side by side to find the cheapest one that still picks the right tool, which matters more here than in most MCP use cases, because every wrong tool call has a price attached.

Frequently Asked Questions

Conclusion

Four SEO platforms now ship working remote MCP servers, and the endpoints above are all from official docs. Search Console is the notable gap, and Google Analytics is local-only.

Pick based on what you already pay for, then constrain your prompts hard — the difference between a useful agent and an expensive one is almost entirely in how specific you are.

Before you wire any of these into a scheduled workflow, connect it in a browser and watch the tool calls. Test any MCP server free →