Yandex 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

MCP serverRussian stack

cybernexcorps/yandex-webmaster-mcpAuthor:cybernexcorps

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/cybernexcorps-yandex-webmaster-mcp

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

Run in a terminal

claude mcp add --transport stdio --env 'YANDEX_WEBMASTER_TOKEN=<your YANDEX_WEBMASTER_TOKEN>' yandex-webmaster -- npx -y @cybernexcorps/yandex-webmaster-mcp

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "yandex-webmaster": {
      "command": "npx",
      "args": [
        "-y",
        "@cybernexcorps/yandex-webmaster-mcp"
      ],
      "env": {
        "YANDEX_WEBMASTER_TOKEN": "<your YANDEX_WEBMASTER_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

YANDEX_WEBMASTER_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Install in Cursor

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "yandex-webmaster": {
      "command": "npx",
      "args": [
        "-y",
        "@cybernexcorps/yandex-webmaster-mcp"
      ],
      "env": {
        "YANDEX_WEBMASTER_TOKEN": "<your YANDEX_WEBMASTER_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Keys and settings

YANDEX_WEBMASTER_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Install in VS Code

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Run in a terminal

code --add-mcp '{"name":"yandex-webmaster","type":"stdio","command":"npx","args":["-y","@cybernexcorps/yandex-webmaster-mcp"],"env":{"YANDEX_WEBMASTER_TOKEN":"<your YANDEX_WEBMASTER_TOKEN>"}}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "yandex-webmaster": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@cybernexcorps/yandex-webmaster-mcp"
      ],
      "env": {
        "YANDEX_WEBMASTER_TOKEN": "<your YANDEX_WEBMASTER_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

YANDEX_WEBMASTER_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

codex mcp add yandex-webmaster --env 'YANDEX_WEBMASTER_TOKEN=<your YANDEX_WEBMASTER_TOKEN>' -- npx -y @cybernexcorps/yandex-webmaster-mcp

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.yandex-webmaster]
command = "npx"
args = ["-y", "@cybernexcorps/yandex-webmaster-mcp"]
env = { YANDEX_WEBMASTER_TOKEN = "<your YANDEX_WEBMASTER_TOKEN>" }

If the file already exists, append the block to the end.

Keys and settings

YANDEX_WEBMASTER_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "yandex-webmaster": {
      "command": "npx",
      "args": [
        "-y",
        "@cybernexcorps/yandex-webmaster-mcp"
      ],
      "env": {
        "YANDEX_WEBMASTER_TOKEN": "<your YANDEX_WEBMASTER_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

YANDEX_WEBMASTER_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "yandex-webmaster": {
      "command": "npx",
      "args": [
        "-y",
        "@cybernexcorps/yandex-webmaster-mcp"
      ],
      "env": {
        "YANDEX_WEBMASTER_TOKEN": "<your YANDEX_WEBMASTER_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Keys and settings

YANDEX_WEBMASTER_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "yandex-webmaster": {
      "command": "npx",
      "args": [
        "-y",
        "@cybernexcorps/yandex-webmaster-mcp"
      ],
      "env": {
        "YANDEX_WEBMASTER_TOKEN": "<your YANDEX_WEBMASTER_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Keys and settings

YANDEX_WEBMASTER_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "yandex-webmaster": {
      "command": "npx",
      "args": [
        "-y",
        "@cybernexcorps/yandex-webmaster-mcp"
      ],
      "env": {
        "YANDEX_WEBMASTER_TOKEN": "<your YANDEX_WEBMASTER_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

YANDEX_WEBMASTER_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "yandex-webmaster": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@cybernexcorps/yandex-webmaster-mcp"
      ],
      "environment": {
        "YANDEX_WEBMASTER_TOKEN": "<your YANDEX_WEBMASTER_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

YANDEX_WEBMASTER_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "yandex-webmaster": {
      "command": "npx",
      "args": [
        "-y",
        "@cybernexcorps/yandex-webmaster-mcp"
      ],
      "env": {
        "YANDEX_WEBMASTER_TOKEN": "<your YANDEX_WEBMASTER_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

YANDEX_WEBMASTER_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .codeassistant/mcp.json, in the project

{
  "mcpServers": {
    "yandex-webmaster": {
      "command": "npx",
      "args": [
        "-y",
        "@cybernexcorps/yandex-webmaster-mcp"
      ],
      "env": {
        "YANDEX_WEBMASTER_TOKEN": "<your YANDEX_WEBMASTER_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

YANDEX_WEBMASTER_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

You will need: Node.js

Checked against the repository on Sep 25, 2026, commit 1830ef2.

Text for your agent

Create an app at oauth.yandex.com with the Yandex.Webmaster permission, get a long-lived OAuth token, and add the server with npx @cybernexcorps/yandex-webmaster-mcp and the YANDEX_WEBMASTER_TOKEN variable.

Other ways from the author

npx @cybernexcorps/yandex-webmaster-mcp

Recommended method, npx fetches the package automatically.

This is third-party code. Review the repository files before installing.

What it does

The server covers nearly the whole Yandex Webmaster v4 API: diagnostics, indexing history and samples, SQI, search-URL events, sitemaps, important URLs, quota-limited recrawl, popular queries and their history, and external and broken internal links. Instead of a host_id like http:example.com:80, a site can be named simply example.com or пример.рф, the server resolves both ASCII and Unicode (IDN) forms. Every mutating tool without confirm: true returns a preview of the exact request that would be sent, not an actual change. Common Yandex error codes are mapped to plain-language hints: bad token, unverified host, rate limit, recrawl quota.

Who it is for. For people who care about protection from accidental writes and want to call sites by plain domains rather than the internal host_id format.

Good fit when

It matters that a Webmaster write requires explicit confirmation instead of firing on the first call
You need Cyrillic (IDN) domains in requests alongside Latin ones
You need broad API coverage: SQI, search-URL events, important-page history

Not a fit when

You need in-chat login without a pre-created OAuth app
A handful of basic tools is enough, 29 may be excessive

Example request

Show whether there are errors in example.ru's sitemap and when the Yandex robot last read it

Limitations

Needs a pre-created OAuth token from an app with Yandex Webmaster permissions, there is no in-chat login. The project honestly describes itself as a rewrite of the third-party theyahia/yandex-webmaster-mcp package, fixing two bugs (a wrong auth header and a URL base-path error). Not an official Yandex server.

How to disable. Remove the yandex-webmaster block from your MCP client config.

MCP

Transport: stdio
Authentication: API key

Environment variables
Environment variables
YANDEX_WEBMASTER_TOKEN required, secret	OAuth token from an app with the Yandex.Webmaster permission, sent as Authorization: OAuth

Security check

Can add sites, add and remove sitemaps, and trigger recrawl once confirm: true is passed
An OAuth token with access to every site in the account sits in the client config

README in short

The English README lists the 29 tools in a category table, explains the project's origin as a rewrite of a third-party package with bug fixes, shows installation via npx or building from source, Claude Desktop and Cursor configuration, and environment variables for a live smoke test against a real account.

FAQ

What happens calling a write tool without confirm?

The server returns a preview of the exact request that would be sent, with no real data change, the required confirm: true flag triggers the actual write.

Can a Cyrillic domain be used?

Yes, both ASCII and Unicode (IDN) forms resolve the same way, prefixing a scheme (https://…) helps disambiguate when both variants are registered.

DataLens Skills

Official

Official DataLens (Yandex) skills for Claude Code, Codex and OpenCode: SDK, HTML reports and RLS resolution

SkillMedium riskRussian stackNo VPN needed12

Yandex Metrika MCP Server

Editors’ pick

A Yandex Metrika MCP server generated from the API spec: 108 methods, 10 tools declared by default, transparent filters and response metadata

MCP serverMedium riskRussian stackNo VPN needed2

OpenSEO

Official

An open MCP server and agent skill set for SEO: keyword research, competitors, backlinks and site audits powered by DataForSEO

MCP serverMedium risk21.5K

Claude SEO

A Claude Code plugin for SEO audits: technical SEO, E-E-A-T, schema, local and AI search via parallel subagents

PluginHigh risk17.9K

Install

What it does

Good fit when

Not a fit when

Example request

Limitations

MCP

Security check

README in short

FAQ

Related

DataLens Skills

Yandex Metrika MCP Server

OpenSEO

Claude SEO