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
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 sites and trigger a recrawl in Yandex Webmaster
- The token grants access to all sites on the account, so check its scopes before handing it to an agent
Install
Manual install
{
"mcpServers": {
"yandex-webmaster": {
"command": "npx",
"args": ["-y", "@rezlazy/yandex-webmaster-mcp"],
"env": {
"WEBMASTER_TOKEN": "<your-oauth-token>"
}
}
}
}The package is published to npm as @rezlazy/yandex-webmaster-mcp.
This is third-party code. Review the repository files before installing.
What it does
The server wraps the entire Yandex Webmaster API v4: the current user and site list, adding and verifying a host, SQI summary and history, sitemaps and feeds, search query stats, page indexing status, URL recrawl, inbound links and site diagnostics. Authorization uses an OAuth token with webmaster:hostinfo and webmaster:verify scopes, obtained through an app on oauth.yandex.ru. The typical flow is wm_user_get for the userId, then wm_hosts_list for a site's hostId, and the rest of the tools use both identifiers.
Who it is for. For SEO specialists and developers who want to run all of Yandex Webmaster from an agent instead of the web UI
Good fit when
- You want to check indexing status and site diagnostics right in a chat with an agent
- You need to manage sitemaps, trigger a recrawl, or add a new site to Webmaster
- You need search query stats and SQI history for a report
Not a fit when
- You have no access to Webmaster or an OAuth app to get a token
- You only need documentation reference without real API calls
Example request
Check the site's indexing status in Yandex Webmaster and show the latest diagnostic issuesLimitations
The project has no stars and a single author. The main branch needs a dist build on install via npx github; for stability, pin a specific release tag like v0.1.1, since v0.1.0 does not build from git. You need your own Yandex OAuth token with the right scopes.
How to disable. Remove the server from your MCP client config, for example with claude mcp remove yandex-webmaster in Claude Code.
MCP
- Transport
- stdio
- Authentication
- OAuth
| Environment variables | |
|---|---|
| WEBMASTER_TOKEN required, secret | Yandex OAuth token with webmaster:hostinfo and webmaster:verify scopes |
| WEBMASTER_API_URL | API base URL, defaults to https://api.webmaster.yandex.net/v4 |
Security check
- Can add sites and trigger a recrawl in Yandex Webmaster
- The token grants access to all sites on the account, so check its scopes before handing it to an agent
README in short
The README gives step by step instructions for getting a Yandex OAuth token, tables of tools by group (user and sites, verification and diagnostics, sitemaps, search queries, links, recrawl, feeds), and configuration examples for Cursor and local development. It also describes the typical call order using userId and hostId.
FAQ
How many tools does the server have?
42, covering sites, verification, sitemaps, search queries, indexing, links, recrawl, diagnostics and feeds.
Can I install a specific version?
Yes, via a tag in the package address: npx -y github:Rezlazy/yandex-webmaster-mcp#v0.1.1.
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