Eight read-only SEO MCP servers
seo-tools-mcp
SERP, Wordstat, GSC, GA4, Yandex Webmaster, Metrika and A-Parser: eight read-only MCP servers with strict JSON and multi-account support for Claude Code
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Some tools spend a paid balance on XMLStock, XMLRiver and A-Parser requests
- OAuth tokens grant access to every property in the GSC, GA4, Webmaster and Metrika account
Install
Manual install
cd seo-tools-mcp && pnpm install && pnpm buildBuilds all eight servers from source.
This is third-party code. Review the repository files before installing.
What it does
The repository bundles eight independent stdio MCP servers for SEO: xmlstock and xmlriver for paid Google and Yandex search results with highlights and SERP features, wordstat for the official free Yandex frequency API via Yandex Cloud, gsc for Google Search Console, ga4 for Google Analytics 4, ywm for Yandex Webmaster, metrika for Yandex Metrika, and aparser for self-hosted A-Parser. Every reading tool is tagged readOnlyHint, except twenty tools that spend a paid resource on each call and are deliberately left untagged so the client keeps asking for confirmation before a bulk run. Secrets live in one ~/.config/seo-tools-mcp/.env file with 600 permissions; each server has its own auth tools for interactive authorization right in the session, and OAuth for GSC, GA4, Webmaster and Metrika refreshes automatically.
Who it is for. For SEO specialists and agencies who want one read-only toolset covering Google and Yandex search results, frequency data and analytics.
Good fit when
- You want both Google (GSC, GA4) and Yandex (Webmaster, Metrika, Wordstat) tools in one consistent format
- You care that paid SERP-provider requests never run without confirmation
- You need multiple accounts on one host via separate env profiles
Not a fit when
- You need write tools: every server is read-only and does not publish or change account data
- You do not need paid SERP services: xmlstock and xmlriver require a funded balance
Example request
Show my site's positions in Google and Yandex for a keyword and check the XMLStock balanceLimitations
Building it needs pnpm and Node.js; ready .mcpb bundles and npm packages exist per server in the releases and on npm. XMLStock and XMLRiver are paid and need a funded balance. GSC, GA4, Webmaster and Metrika require a Google or Yandex OAuth application with the right scopes; Wordstat via Yandex Cloud needs a service account with the search-api.webSearch.user role. XMLStock's mobile results do not include highlights or related questions, which is the provider's own limitation, not the server's.
How to disable. Remove the relevant server with claude mcp remove, for example claude mcp remove metrika, or uninstall the plugin with /plugin uninstall if you installed it via the marketplace.
Security check
- Some tools spend a paid balance on XMLStock, XMLRiver and A-Parser requests
- OAuth tokens grant access to every property in the GSC, GA4, Webmaster and Metrika account
README in short
The Russian and English README describes the eight servers in a table with their tools and auth type, explains the readOnlyHint policy for paid tools, and covers publication on npm, the official and GitHub MCP Registry, Claude Code plugins and .mcpb bundles in the releases. It details a from-source build, a single secrets file with environment variables taking priority, registering each server in Claude Code, and getting access per service, including XMLStock quirks (mobile results without highlights, error codes) and the free Wordstat API via a Yandex Cloud service account.
FAQ
Can it accidentally spend extra money?
Tools that spend a paid resource are deliberately left without the readOnlyHint tag, so the client asks for confirmation before every such call.
Do I need Wordstat separately from xmlstock?
Yes, XMLStock has no Wordstat frequencies; those come from a separate free official API via Yandex Cloud.
Related
Official DataLens (Yandex) skills for Claude Code, Codex and OpenCode: SDK, HTML reports and RLS resolution
A Yandex Metrika MCP server generated from the API spec: 108 methods, 10 tools declared by default, transparent filters and response metadata
An open MCP server and agent skill set for SEO: keyword research, competitors, backlinks and site audits powered by DataForSEO
A Claude Code plugin for SEO audits: technical SEO, E-E-A-T, schema, local and AI search via parallel subagents