Yandex Webmaster MCP

Install

{
  "mcpServers": {
    "yandex-webmaster": {
      "command": "npx",
      "args": ["-y", "yandex-webmaster-mcp-server"],
      "env": {
        "YANDEX_WEBMASTER_OAUTH_TOKEN": "your-token",
        "YANDEX_WEBMASTER_HOST_URL": "https://example.com"
      }
    }
  }
}

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

What it does

The server gives the agent 46 Webmaster tools in four groups. Core tools cover sites, verification, summary and diagnostics. Content tools handle sitemaps, indexing history, URLs in search, important pages, broken links and excluded pages. Analytics returns search queries, external links and SQI history, and actions submit pages for recrawl, add original texts and manage feeds. With a default site set, the agent does not have to look up the host ID every time.

Who it is for. SEO specialists, marketers and site owners who monitor sites in Yandex Webmaster.

Example request

What issues did Webmaster find on my site and are there broken internal links?

Limitations

Needs a Yandex app OAuth token with webmaster:verify and webmaster:hostinfo scopes. Recrawl requests consume the daily quota. Some tools write: adding and deleting sites, sitemaps, original texts and feeds.

How to disable. Remove the yandex-webmaster block from the MCP config and revoke the app token at oauth.yandex.ru.

MCP

Transport

stdio

Authentication

API key

Security check

• Can remove a site, sitemaps and feeds from Webmaster
• Recrawl submissions consume a limited quota

README in short

The Russian README groups features into core, content, analytics and actions, marking each tool as read or write. It gives sample prompts for audits, monitoring, link profiles and actions. It covers install via npx, globally or from source, getting an OAuth token, stdio and HTTP modes and client config. MIT license.

Related