Yandex Webmaster MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 105 installs a week from npm. Last commit 1 Nov 2026.
MCP server for Yandex Webmaster API: indexing, search queries, sitemaps, diagnostics, links.
What the code does
We read the source, 23 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
/(?<key>(?:login|password|secret|token|api[_-]?key|authorization)\s*[:=]\s*["']?|(?:bearer|basic)\s+)(?<val>[^,;]+)|[^\s,;]*(?:@|:\/\/|%3A|\p{L}\.\p{L})[^\s,;]*|(?<key2>\b(?:token|secret|password|api[_-]?key|access_token|refresh_token|client_secret)\s+)(?!(?:expired|invalid|is|…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-yandex-webmaster -e 'YANDEX_OAUTH_TOKEN=<YANDEX_OAUTH_TOKEN>' -- npx -y mcp-yandex-webmaster{
"mcpServers": {
"mcp-yandex-webmaster": {
"command": "npx",
"args": [
"-y",
"mcp-yandex-webmaster"
],
"env": {
"YANDEX_OAUTH_TOKEN": "<YANDEX_OAUTH_TOKEN>"
}
}
}
}[mcp_servers.mcp-yandex-webmaster]
command = "npx"
args = ["-y", "mcp-yandex-webmaster"]
env = { YANDEX_OAUTH_TOKEN = "<YANDEX_OAUTH_TOKEN>" }{
"mcpServers": {
"mcp-yandex-webmaster": {
"command": "npx",
"args": [
"-y",
"mcp-yandex-webmaster"
],
"env": {
"YANDEX_OAUTH_TOKEN": "<YANDEX_OAUTH_TOKEN>"
}
}
}
}{
"servers": {
"mcp-yandex-webmaster": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-yandex-webmaster"
],
"env": {
"YANDEX_OAUTH_TOKEN": "<YANDEX_OAUTH_TOKEN>"
}
}
}
}Put your own value in place of
<YANDEX_OAUTH_TOKEN> (Yandex OAuth token with Webmaster access, sent as `Authorization: OAuth <token>`. Treat it as a secret).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
YANDEX_USER_ID (Token owner's user id; auto-detected via GET /v4/user when unset), YANDEX_WEBMASTER_HOST_ID (Default host_id (e.g. https:example.com:443) used when a tool call omits one), YANDEX_WEBMASTER_API_BASE (API root override), YANDEX_WEBMASTER_TIMEOUT_MS (Per-request timeout in milliseconds), YANDEX_WEBMASTER_MAX_RETRIES (Retries on transient errors (429 — except the daily QUOTA_EXCEEDED; 5xx/network for reads)).
Alternatives to Yandex Webmaster MCP
same job, measured the same wayMCP server for Yandex Webmaster API — site analytics, indexing, search queries
MCP server for Yandex.Webmaster API — hosts, search queries, indexing status. Bearer token auth.
MCP server for Yandex.Webmaster search queries (read-only).
Google Search Console MCP for analytics, indexing, sitemaps, and SEO diagnostics.
Query Yandex Webmaster indexing, queries, diagnostics and backlinks, and recrawl, via an AI agent.
MCP server for Google Search Console & Indexing API — search analytics, sitemaps, URL inspection
MCP server for Yandex Search API (v2, Cloud)
Google Search Console MCP server — query performance, sitemaps, indexing & more
Yandex Webmaster MCP — questions
Answers built from our own checks of this server.