Yandex Webmaster MCP for a local SEO routine
kurerok-yandex-webmaster-mcp
A local Yandex Webmaster MCP server with a recommended weekly routine: queries, indexing, recrawl and diagnostics in order
- 0 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Can add a sitemap and submit recrawl URLs once confirmed: true is passed
- The site-scoped OAuth token is read from the process's environment variables
Install
- Works in
- Services
Manual install
npm install && npm run buildBuild from source, no published npm package.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Can add a sitemap and submit recrawl URLs once confirmed: true is passed
- The site-scoped OAuth token is read from the process's environment variables
This is third-party code. Review the repository files before installing.
What it does
The server talks to the official Yandex Webmaster API directly, with no third-party hosting: the OAuth token never leaves for another service. It provides tools for search query analytics, sitemap state, indexing history, pages in search, appearance and disappearance events, recrawl quota and queue, diagnostics, and external and broken internal link samples. Two tools change data: adding a sitemap and submitting a recrawl, both require confirmed: true. The README separately spells out a recommended weekly call order and warns against bulk-submitting weak pages before fixing the vacancy feed and JobPosting markup.
Who it is for. For a team with a specific weekly SEO process that wants to keep its OAuth token to itself, without a third-party hosted server.
Good fit when
- It matters that the token goes only directly to the Yandex API, with no intermediary hosting
- You want a ready weekly check order: sitemaps, quota, queries, pages in search, indexing
- You need write tools gated by a required confirmed: true
Not a fit when
- You need to add new sites or start ownership verification, these tools are not included
- You need in-chat login without pre-creating an OAuth app
Example request
Build a weekly report: sitemap state, recrawl quota, queries, and pages that appeared or dropped from searchMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
YANDEX_WEBMASTER_TOKENrequired, secret- OAuth token from an app with Yandex Webmaster API access
YANDEX_WEBMASTER_HOST_IDrequired- Site in scheme:domain:port form, e.g. https:kurerok.ru:443
Limitations
No tools for adding a site or starting verification. The token lives only in environment variables, but the README separately warns to keep it out of shell history and config files where possible. Built for a specific project (Kurerok) but applicable to any site.
How to disable. Remove the kurerok-yandex-webmaster block from your MCP client config.
FAQ
What is the recommended check order?
The README suggests: sitemaps, recrawl quota, search queries, pages in search, indexing history, then building a URL queue and submitting it with confirmed: true.
Why not bulk-submit pages for recrawl?
The README explicitly warns not to bulk-submit weak external-apply or low-value pages before fixing the vacancy feed and JobPosting/directApply semantics.
Discussion
No questions or reviews yet.
Related
All Yandex Webmaster toolsYandex Webmaster MCP with safe writes
Yandex Webmaster MCP
A Yandex Webmaster v4 API MCP server with 29 tools and friendly site names instead of host_id, every write requires confirm: true
Yandex Webmaster MCP
Яндекс Вебмастер MCP
A Yandex Webmaster MCP server with in-chat OAuth PKCE login: 20 tools for diagnostics, search queries, sitemaps and recrawl
A Python MCP server for Yandex Webmaster with writes disabled by default and a site whitelist for sitemaps and recrawl
Yandex Webmaster MCP server (npm)
@theyahia/yandex-webmaster-mcp
A TypeScript MCP server for the Yandex Webmaster API: sites, indexing, search queries, sitemaps, diagnostics and recrawl, 13 tools
Yandex Webmaster MCP by Rezlazy
@rezlazy/yandex-webmaster-mcp
An MCP server with 42 tools for the Yandex Webmaster API v4: sites, sitemaps, search queries, indexing, links, recrawl and diagnostics
Yandex Webmaster MCP
Yandex Webmaster MCP Server
MCP server for Yandex Webmaster API v4: indexing, search queries, broken links, SQI, recrawl, sitemaps and feeds
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Yandex Webmaster MCP for a local SEO routine (this card) | no | API key | 0 | |
| Yandex Webmaster MCP server (npm) | no | API key | 6 | indexing and queries |
| webmaster-mcp | no | API key | 0 | writes off by default, a site allowlist |
README in short
The English README splits tools into read-only and state-changing, shows installation via npm install and npm run build, token and host_id setup, Codex and Claude configuration, a security section on keeping the token only in environment variables, and a recommended weekly check sequence.