SkillFoxx

Eight read-only SEO MCP servers plugin

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

  • 8 ★ on the repository
  • Last commit
  • MIT
Plugin

Extended access

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
All reasons and checks
Russian stack

antohins/seo-tools-mcpAuthor:antohins

Install

Works in

Manual install

cd seo-tools-mcp && pnpm install && pnpm build

Builds all eight servers from source.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • 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

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 paid Yandex frequency API via Yandex Cloud (only the region list is free), 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 balance

Limitations

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.

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 paid official API via Yandex Cloud.

Discussion

No questions or reviews yet.

All Yandex Wordstat tools
Russian stack

Five MCP servers for Yandex APIs: Wordstat, Search, Webmaster, Metrika and Direct, plus a Claude Code plugin with skills

MCP serverBroad access70
Russian stack

A dependency-free, mostly read-only MCP server for Metrika, Webmaster, Direct and Wordstat, with the token kept in Keychain

PluginExtended access4
Russian stack

Five MCP servers for Yandex Search, Wordstat, Webmaster, Metrika and Direct, bundled as a Claude Code plugin with two skills

PluginBroad access20
Russian stack

Five MCP servers for Wordstat, Search, Webmaster, Metrica and Direct, plus a Claude Code plugin with keyword and competitor skills

MCP serverBroad access1
Russian stack

A read-only Yandex Webmaster MCP with PKCE sign-in and no app registration needed: indexing, queries, diagnostics, backlinks

PluginBroad access4
Russian stack

A 155-tool MCP server for Yandex Direct, Metrika, Wordstat and Webmaster, with self-setup OAuth and read-only and confirm modes

MCP serverBroad access3

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 paid Wordstat API via a Yandex Cloud service account.

README badge

Report a problem