Ranked roundup · SEO
Best MCP Server for SEO
There is an official MCP server for SEO — three of them, in fact. Ahrefs, Semrush, and DataForSEO all ship vendor-supported servers as of September 2026, which means the community-workaround era for the big suites is over. Ahrefs and Semrush run hosted endpoints with OAuth sign-in, bundled into paid plans. DataForSEO publishes an open-source server (Apache-2.0, 242 stars, pushed the day we checked) with pay-as-you-go API pricing. The gap is Google: there is no official Search Console MCP server, so community projects fill it — the most-starred, ahonn/mcp-server-gsc, sits at 261 stars and authenticates with a service account. One trap for anyone following older tutorials: Ahrefs archived its local GitHub server in February 2026; the hosted endpoint replaced it. We ranked the six options below on verifiable criteria only — official status, maintenance recency, adoption, auth model, and documented coverage. Nobody paid for placement, and we don't publish benchmark scores we didn't run.
Facts checked September 1, 2026 · ranked on verifiable criteria · placement is never for sale
Founder, Automation Squad ·
The ranking
- Official · Ahrefs
Teams already paying for Ahrefs who want its data inside Claude, ChatGPT, or Cursor with zero hosting friction
40+ Ahrefs endpoints per the official docs: backlinks, keyword research, site explorer metrics, rank tracker, site audit, SERP overviews, content and competitive analysis
Hosted remote server — nothing to install or run locally; setup syncs across devices on your account · OAuth browser sign-in to your Ahrefs account; hosted endpoint at api.ahrefs.com/mcp/mcp, no keys to paste
- Requires a paid Ahrefs plan — Lite or higher; there is no free tier
- Usage draws from monthly API-unit caps by plan (100,000 units and 100 rows/request on Lite, up to 2M units on Enterprise)
- The GitHub repo (ahrefs/ahrefs-mcp-server, 101 stars) is the old local server, archived February 2026 — its own README calls it outdated and says it does not work with MCP keys; skip any tutorial that installs it via npm
- The current hosted server is closed source, so you can't self-host or audit it
- Official · DataForSEO
Developers and agencies building SEO agents who want raw data without committing to a full-suite subscription
The widest raw-data coverage on this page: SERP, Keywords Data, DataForSEO Labs, OnPage (with Lighthouse), Backlinks, Business Data, and Domain Analytics APIs through one server
Self-host via npx or Docker, run as a local HTTP server, or use the public remote endpoint at mcp.dataforseo.com/v3/mcp · OAuth 2.0 on the hosted endpoint by default; DATAFORSEO_LOGIN/DATAFORSEO_PASSWORD env vars (Basic auth) when self-hosting · Apache-2.0 · 242★
- Pay-as-you-go API: every tool call bills credits against your deposit-funded account, so a chatty agent runs up real costs
- No bundled subscription or documented free tier — you need a funded DataForSEO API account
- Self-hosted Basic auth means plaintext credentials in environment variables; prefer the OAuth path on the hosted endpoint
- The previous v2 MCP server is deprecated — make sure you're on the v3 server and endpoint
- Official · Semrush
Semrush-suite teams who want keyword, backlink, and traffic data in their AI client without leaving their existing plan
All of the Standard SEO API (keywords, backlinks, domain analytics), all of the Trends API (traffic and market data), and read-only access to the Projects API
Hosted remote server at mcp.semrush.com/v2/mcp — streamable HTTP transport only, nothing to run locally · OAuth 2.0/2.1 by default (redirects to Semrush login); API key via Authorization header as a fallback
- Requires a qualifying plan or API purchase: Semrush One Starter/Pro+ or SEO Classic Pro/Guru (50,000 units included), otherwise paid API unit packages
- Traffic and market data needs a separate Trends API subscription (Basic or Premium)
- MCP calls consume the same unit-based quota as regular API calls — budget accordingly
- Closed source, hosted-only; Projects access is read-only
Your own sites' real query, click, and indexing data — the one dataset the paid suites can't sell you
Search analytics up to 25,000 rows per query with regex filtering; query, page, country, device, and search-appearance dimensions; flexible date ranges and sitemap tools
Local Node.js server, run via npx/npm — no hosted option · Google Cloud service-account JSON via GOOGLE_APPLICATION_CREDENTIALS; the service account's email must be granted access on your Search Console property · 261★
- Community project — Google ships no official Search Console MCP server, so every option here is unofficial
- The repo declares no license (GitHub API reports none), which leaves reuse terms legally unclear
- Last pushed February 2026 — about six months before our verification date
- Setup is the most involved on this page: a Google Cloud project, the Search Console API enabled, a service account created, and its email added to your property
- If license and freshness matter more than adoption, surendranb/google-search-console-mcp (38 stars, MIT, pushed August 2026) is a smaller but more recently updated alternative
Teams already running many agent integrations through one managed platform who want SEO tools in the same place
Managed toolkits for Ahrefs (40 documented actions: backlinks, domain metrics, keyword research, rank tracking, SERP data) and Semrush, behind the same credential layer as hundreds of other app integrations
Managed integration platform — Composio runs the MCP layer; no server for you to host · Composio stores and manages credentials; the Ahrefs toolkit supports API key or OAuth2 — but you supply your own Ahrefs credentials (it is not a Composio-managed app)
- Not vendor-official — a third-party layer over Ahrefs' and Semrush's APIs
- You still need paid vendor accounts and API access underneath; Composio adds its own pricing on top
- Composio's own docs mark the Ahrefs toolkit as not a managed app, so you bring and configure your own credentials
- Action-only (0 triggers) — no event-driven workflows from the SEO toolkits
- Adds a dependency: if Composio changes or drops a toolkit, your integration goes with it
- Community
Understanding what the popular 'free Ahrefs MCP' actually is before you consider deploying it — we don't recommend it for production
Backlink analysis, keyword ideas and difficulty, and traffic estimates pulled from Ahrefs' free-tool data, with caching
Local Python server · Requires a paid CapSolver API key — the server uses it to solve Cloudflare Turnstile captchas and get past Ahrefs' bot protection on its free tools · MIT · 257★
- Works by paying a captcha-solving service to bypass Ahrefs' Cloudflare protection — almost certainly against Ahrefs' terms of service, and Ahrefs can break it at any time
- Its own README says it is for educational purposes only
- Not updated since April 2025 — 17 months stale at our verification date
- The 'free' pitch is misleading: CapSolver is a paid dependency
- Unofficial and unaffiliated with Ahrefs despite being built on Ahrefs data
SEO MCP servers compared
| Server | Maintained by | Runs | Auth | License |
|---|---|---|---|---|
| Ahrefs MCP Server | Ahrefs | Hosted remote server — nothing to install or run locally; setup syncs across devices on your account | OAuth browser sign-in to your Ahrefs account; hosted endpoint at api.ahrefs.com/mcp/mcp, no keys to paste | — |
| DataForSEO MCP Server | DataForSEO | Self-host via npx or Docker, run as a local HTTP server, or use the public remote endpoint at mcp.dataforseo.com/v3/mcp | OAuth 2.0 on the hosted endpoint by default; DATAFORSEO_LOGIN/DATAFORSEO_PASSWORD env vars (Basic auth) when self-hosting | Apache-2.0 |
| Semrush MCP | Semrush | Hosted remote server at mcp.semrush.com/v2/mcp — streamable HTTP transport only, nothing to run locally | OAuth 2.0/2.1 by default (redirects to Semrush login); API key via Authorization header as a fallback | — |
| mcp-server-gsc (Google Search Console, community) | Community | Local Node.js server, run via npx/npm — no hosted option | Google Cloud service-account JSON via GOOGLE_APPLICATION_CREDENTIALS; the service account's email must be granted access on your Search Console property | — |
| Composio (managed Ahrefs + Semrush toolkits) | Community | Managed integration platform — Composio runs the MCP layer; no server for you to host | Composio stores and manages credentials; the Ahrefs toolkit supports API key or OAuth2 — but you supply your own Ahrefs credentials (it is not a Composio-managed app) | — |
| seo-mcp (cnych) | Community | Local Python server | Requires a paid CapSolver API key — the server uses it to solve Cloudflare Turnstile captchas and get past Ahrefs' bot protection on its free tools | MIT |
How to choose
Pick Ahrefs if you already pay for a Lite plan or higher — the MCP is bundled into the subscription, OAuth handles auth, and there is nothing to host. Pick Semrush by the same logic if Semrush is your suite, but check the unit math first: MCP calls spend the same API units as everything else. Pick DataForSEO if you're building agents or don't want a full-suite subscription — it's open source, the most actively maintained server here, and pay-as-you-go, though every call costs credits. Pick a community Search Console server for your own sites' real query data; it's free beyond the Google Cloud setup. Pick Composio only if you're already standardizing many integrations behind one managed layer.
How this ranking works
Every server here is real and was checked against its repository or vendor documentation on the date above — stars and licenses come from the GitHub API, not from memory. Order reflects verifiable criteria only: official support, maintenance recency, adoption, auth model, and documented capability coverage. We do not run paid placements, and we list every caveat we find, including the unflattering ones.
Common questions
- Is there an official MCP server for SEO?
- Yes — three vendors ship them. Ahrefs and Semrush run hosted OAuth servers bundled with paid plans, and DataForSEO maintains an open-source server (Apache-2.0) alongside a public remote endpoint. Google is the exception: there is no official Search Console MCP server, only community projects.
- What does setup and authentication actually look like?
- The official hosted servers are the easy path: add the endpoint URL to your MCP client and sign in via OAuth in a browser — no keys to manage. Self-hosting DataForSEO means putting your API login and password in environment variables, and community Search Console servers are the most work: a Google Cloud project, the Search Console API enabled, and a service-account JSON granted access to your property.
- Do I need a paid subscription to use these?
- Mostly yes. Ahrefs requires a Lite plan or higher, Semrush requires a qualifying plan or purchased API units, and DataForSEO bills every call against a funded pay-as-you-go account. The community Google Search Console servers are the free option — your own site data costs nothing beyond the Google Cloud setup.
- Why is the free Ahrefs scraper (cnych/seo-mcp) ranked last despite 257 stars?
- Because of how it works: it pays a captcha-solving service to bypass Ahrefs' Cloudflare protection, which almost certainly violates Ahrefs' terms, and its own README limits it to educational use. It also hasn't been updated since April 2025, so it breaks whenever Ahrefs changes its defenses.
MCP servers we build
Automation Squad publishes its own open-source MCP servers and agent skills, documented with the same rules this ranking uses.