Yandex Webmaster API v4.1 MCP server
Яндекс Вебмастер MCP-сервер
A Python MCP server with full Yandex Webmaster API v4.1 coverage: 37 tools from diagnostics and sitemaps to important-URL monitoring
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
- Can add and remove sites, sitemaps and trigger recrawl without a separate confirmation step
- A broad-permission Webmaster OAuth token is passed through an environment variable
Install
Manual install
pip install -e .Install from source via pip.
This is third-party code. Review the repository files before installing.
What it does
The server covers almost the entire Yandex Webmaster API v4.1: sites and adding or removing them, verification status and owner lists, a summary with ИКС quality scores and its history, popular queries (top 3000) and analytics, recrawl quota and submission, diagnostics, indexing history by HTTP status, important-URL monitoring, pages in search with history and samples, auto-discovered and manually added sitemaps, and external and broken internal links. The server URL-encodes the host_id in scheme:domain:port form itself when sending API requests.
Who it is for. For SEO specialists who want the widest possible Yandex Webmaster API coverage in a single Python server.
Good fit when
- You need the full Webmaster spectrum: from diagnostics and ИКС to important-URL monitoring and external links
- Installing via pip install -e . and running the Python server directly is fine
- You need call examples with real date and indicator parameters
Not a fit when
- You need write operations gated by explicit confirmation, no confirm flag is documented
- You need in-chat login without pre-creating an OAuth app
Example request
Show example.com's popular queries for March 2026 with impressions, clicks and average positionLimitations
The OAuth token lasts 6 months and needs manual refresh. The README does not describe write operations being gated by a confirmation step. The host_id format (scheme:domain:port with no slashes) needs care when building requests manually.
How to disable. Remove the yandex-webmaster block from your MCP client config.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| YANDEX_WEBMASTER_API_KEY required, secret | OAuth token with webmaster:hostinfo and webmaster:verify scopes, valid for 6 months |
Security check
- Can add and remove sites, sitemaps and trigger recrawl without a separate confirmation step
- A broad-permission Webmaster OAuth token is passed through an environment variable
README in short
The Russian README lists capabilities by section covering nearly all of API v4.1, shows pip install -e . installation, obtaining an OAuth token with the right permissions, Claude Desktop and Claude Code configuration, and tool call examples with real date, indicator and host_id parameters.
FAQ
What is a host_id?
Yandex Webmaster's special site identifier format: scheme:domain:port with no slashes, e.g. https:example.com:443, not a regular URL.
How long does the OAuth token last?
Six months from issuance, after which it needs to be obtained again through the same oauth.yandex.ru/authorize link.
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