Seo Tools MCP

What antohins/seo-tools-mcp MCP server does

antohins/seo-tools-mcp MCP server gives MCP clients access to read-only SEO services aimed at Google and Yandex workflows, including the Russian and CIS markets. The repository describes separate stdio servers for SERP providers, Yandex Wordstat, Google Search Console, Google Analytics 4, Yandex.Webmaster, Yandex.Metrica, and self-hosted A-Parser. The supplied listing focuses on five of those service areas and reports 38 available tools.

Responses are returned as structured JSON. The tools do not publish content or modify data in the connected accounts. Defaults such as a Search Console property, GA4 property, Webmaster host, or Metrica counter can be selected during use rather than being fixed to one website.

How it works

The package runs locally over stdio and can be used from an MCP-compatible client. Service credentials are selected according to the provider: XMLStock uses API keys, while Google Search Console, Yandex.Webmaster, and Yandex.Metrica use OAuth-based access. The README also documents service-account authentication for some Google services and automatic OAuth refresh for Yandex services.

XMLStock calls provide SERP, image, news, video, and Wordstat data. SERP requests can target Google or Yandex, use one region, and specify device and other search parameters. Requests that go beyond the initial result page are paginated. XMLStock search and Wordstat operations are charged by that provider, while the balance check is described as free.

Setup and configuration

The repository identifies npm as a distribution channel and describes stdio installation with an npx command. The package name in the supplied installation text is incomplete, so the exact executable package should be verified in the repository or npm listing before putting it into an automated client configuration.

Credentials can be configured for the relevant provider. XMLStock has authorization-status and credential-setting tools: the status call reports which masked keys are present, and the setter can update selected fields, apply them without restarting, and save named profiles for multiple accounts. The README notes that XMLStock Wordstat uses the same XMLStock credentials as its other tools and does not require a separate Yandex Cloud key.

Tools and capabilities

The XMLStock tool group includes:

• Google and Yandex organic SERP snapshots, including positions, URLs, titles, snippets, and selected SERP features.
• Google image, news, and video search results.
• Yandex Wordstat frequency, related phrases, time trends, regional demand, and a region tree.
• XMLStock account balance and credential checks.

The broader repository also documents Search Console queries and URL inspection, property and sitemap discovery, Yandex.Webmaster query and indexing data, and Yandex.Metrica reporting. The README lists additional GA4, XMLRiver, and A-Parser servers, although those are separate service groups rather than one combined tool namespace.

Limitations and notes

Read-only describes account mutations, not cost. XMLStock SERP and Wordstat requests consume paid provider resources, and deeper SERP pagination creates additional requests. An empty SERP response can still be billed. Mobile XMLStock SERP results provide fewer features than desktop results, and the official yandex_xml mode has different fields and limitations from live Yandex search.

Search Console data uses Pacific Time, has roughly 16 months of history, and final data can lag by two to three days. The package therefore suits analysis and reporting, but users should account for provider billing, authentication scope, regional differences, and data freshness.