SkillFoxx

Yandex Webmaster MCP

Яндекс Вебмастер MCP

A Yandex Webmaster MCP server with in-chat OAuth PKCE login: 20 tools for diagnostics, search queries, sitemaps and recrawl

  • 1 ★ on the repository
  • Last commit
  • MIT
MCP server

Extended access

Why this level

  • Can add sites and sitemaps, start ownership verification and recrawl, including deletion via the generic raw_request
  • The obtained OAuth token grants access to all sites in the Yandex account for a year without re-login
All reasons and checks
Russian stack

askads/mcp-yandex-webmasterAuthor:Ask Ads

Install

Manual install

claude mcp add --transport stdio --scope user yandex-webmaster -- npx -y mcp-yandex-webmaster@latest

Command from the README, no token needed: login happens in chat after connecting.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Can add sites and sitemaps, start ownership verification and recrawl, including deletion via the generic raw_request
  • The obtained OAuth token grants access to all sites in the Yandex account for a year without re-login

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

What it does

The server provides 20 tools for the Yandex Webmaster API v4: a site list with ИКС quality scores, diagnostics by severity, search query impressions and clicks broken down by device, indexing history, crawl HTTP errors, sitemaps and external links. Almost every tool is read-only, with a few that can add a site or sitemap, start ownership verification, or queue a page for recrawl. The connection happens right in chat: the agent opens Yandex's login page, the user sends back a one-time code that gets exchanged for a token via PKCE inside the running server, with no config editing or pre-created token.

Who it is for. For SEO specialists and site owners who want quick conversational access to Yandex Webmaster data without manually configuring a token.

Good fit when

  • You want to connect without pre-creating an OAuth app and token
  • You need to review diagnostics, impressions, clicks and positions in natural language
  • You need to check a sitemap, queue a recrawl or add a new site

Not a fit when

  • You need Metrika, Wordstat or ad-account data: the server only covers Webmaster's organic search
  • You need continuous background monitoring: the server only responds to agent calls

Example request

What critical problems does the diagnostics show for my site right now?

MCP

Transport
stdio
Authentication
OAuth

Environment variables

YANDEX_OAUTH_TOKEN secret
A ready OAuth token for CI, not needed in normal mode: takes priority over the in-chat login
YANDEX_WEBMASTER_HOST_ID
The default site, so it does not need to be specified in every request
YANDEX_WEBMASTER_OAUTH_CLIENT_ID
Your own OAuth app's ClientID instead of the default app

Limitations

Diagnostics, queries and indexing require verified site ownership, without it only the site list and verification status are visible. Recrawl is limited by the site's daily quota. Top queries are capped at 3000 rows per week, 500 rows per request. By default the server sends anonymous technical telemetry (disable with ASKADS_TELEMETRY=0), the token and account data are never included.

How to disable. Tell the agent to disconnect Webmaster, or remove the server from your client config; access can also be revoked in Yandex ID.

FAQ

Does an OAuth token need to be created in advance?

No, for regular use no token is needed: the connection happens right in chat through a one-time PKCE code, which is safe to paste into the conversation.

What does HOST_NOT_VERIFIED mean?

It means site ownership is not verified in Webmaster, only the site list and verification status are available, everything else needs verification via DNS, an HTML file or a meta tag.

Discussion

No questions or reviews yet.

All Yandex Webmaster tools
Russian stack

A Yandex Webmaster v4 API MCP server with 29 tools and friendly site names instead of host_id, every write requires confirm: true

MCP serverExtended access

Yandex Webmaster MCP

Yandex Webmaster MCP Server

Russian stack

MCP server for Yandex Webmaster API v4: indexing, search queries, broken links, SQI, recrawl, sitemaps and feeds

MCP serverBroad access7
Russian stack

A read-only Yandex Webmaster MCP with PKCE sign-in and no app registration needed: indexing, queries, diagnostics, backlinks

PluginBroad access4
Russian stack

A Python MCP server for Yandex Webmaster with writes disabled by default and a site whitelist for sitemaps and recrawl

MCP serverExtended access
Russian stack

A local Yandex Webmaster MCP server with a recommended weekly routine: queries, indexing, recrawl and diagnostics in order

MCP serverExtended access

Yandex Webmaster MCP by Rezlazy

@rezlazy/yandex-webmaster-mcp

Russian stack

An MCP server with 42 tools for the Yandex Webmaster API v4: sites, sitemaps, search queries, indexing, links, recrawl and diagnostics

MCP serverExtended access

README in short

The Russian README describes connecting without a pre-created token via in-chat OAuth PKCE, npx-based installation for Codex, Claude Code, Claude Desktop, Cursor and VS Code, a table of which operations change data, environment variables for CI, a telemetry section, and links to detailed tool documentation.

README badge

Report a problem