Log inSubmit server
Seo Tools MCP logo

Seo Tools MCP

by antohins

Read-only MCP tools for SERP, Wordstat, Search Console, Yandex Webmaster, and Yandex Metrica data.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Seo Tools MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "antohins-seo-tools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-xmlstock"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 11 tools correctly (1mo ago).

Overview

antohins/seo-tools-mcp MCP server exposes read-only SEO data sources for Google and Yandex through local stdio MCP servers. It covers SERP retrieval, Yandex Wordstat, Google Search Console, Yandex.Webmaster, and Yandex.Metrica, with 38 tools and support for multiple accounts. Authentication uses API keys or OAuth with automatic token refresh, depending on the service. Reach for it when an agent needs structured SEO research or reporting data without changing connected accounts.

Use cases

  • Inspect Google and Yandex SERP positions by region and device
  • Analyze Yandex Wordstat demand and related phrases
  • Review Search Console indexing and search-performance data
  • Compare regional keyword demand over time
  • Read Yandex Webmaster and Metrica SEO metrics

Key features

  • Read-only SEO data access
  • Google and Yandex SERP retrieval
  • Yandex Wordstat frequency and regional analysis
  • Google Search Console queries and URL inspection
  • OAuth auto-refresh and multi-account support
  • Structured JSON responses

Tools11

What Seo Tools MCP lets your agent do. Expand a tool for its parameters.

Verified live~3.0k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

18/18 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · seo-tools-mcp-xmlstock (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars8Stargazers on the source repository.
npm downloads225Package downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed11Callable tools this server registers over MCP.
Directory activity7 viewsConfig copies, upvotes, and views on AllMCPs.

How Seo Tools MCP works

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.

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.

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.

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.

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Seo Tools MCP

API keys are required for XMLStock, while the documented Google Search Console, Yandex.Webmaster, and Yandex.Metrica services use OAuth. Some Google services also support a service account.

Yes. The Google Search Console group includes URL Inspection, search analytics, site listing, access details, and sitemap tools.

Yes. The listing describes multi-account support, and XMLStock credentials can be stored in named profiles.

Related MCP servers

All in Marketing All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSeo Tools MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/antohins-seo-tools-mcp?style=directory)](https://allmcps.com/mcp/antohins-seo-tools-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/antohins-seo-tools-mcp"><img src="https://allmcps.com/api/badge/antohins-seo-tools-mcp?style=directory" alt="Seo Tools MCP on AllMCPs" /></a>