Skip to main content
Glama
kurerok-yandex-webmaster-mcp

kurerok-yandex-webmaster-mcp

kurerok-yandex-webmaster-mcp

Local-first MCP server for Yandex Webmaster. It exposes the pieces we need for Kurerok SEO operations: search query analytics, sitemap state, indexing history, pages in search, recrawl quota/submission, diagnostics, and link samples.

This project intentionally talks to the official Yandex Webmaster API directly. It was informed by the public MCP ecosystem, especially:

  • altrr2/yandex-tools-mcp for the multi-package Yandex API direction.

  • theYahia/yandex-webmaster-mcp for a compact Webmaster-only surface.

  • yandex/yandex-search-mcp-server for official Yandex MCP packaging ideas.

It does not require sending OAuth tokens to a hosted third party.

Tools

Read-only:

  • yandex_get_user

  • yandex_list_hosts

  • yandex_get_host_summary

  • yandex_get_diagnostics

  • yandex_get_sitemaps

  • yandex_get_search_queries

  • yandex_get_indexing_history

  • yandex_get_pages_in_search_history

  • yandex_get_search_events_samples

  • yandex_get_recrawl_quota

  • yandex_get_recrawl_queue

  • yandex_get_external_links

  • yandex_get_broken_internal_links

State-changing, quota-sensitive:

  • yandex_add_sitemap

  • yandex_submit_recrawl_urls

Both require confirmed: true.

Related MCP server: Yandex Webmaster MCP Server

Setup

npm install
npm run build

Create a Yandex OAuth application with Yandex Webmaster API access and set:

export YANDEX_WEBMASTER_TOKEN="..."
export YANDEX_WEBMASTER_HOST_ID="https:kurerok.ru:443"

Codex/Claude MCP config:

{
  "mcpServers": {
    "kurerok-yandex-webmaster": {
      "command": "node",
      "args": ["/absolute/path/to/kurerok-yandex-webmaster-mcp/dist/index.js"],
      "env": {
        "YANDEX_WEBMASTER_TOKEN": "use-env-or-secret-manager",
        "YANDEX_WEBMASTER_HOST_ID": "https:kurerok.ru:443"
      }
    }
  }
}

Security Notes

  • Tokens are read only from environment variables.

  • The server never prints the token intentionally.

  • API errors are surfaced without request headers.

  • Mutating tools require explicit confirmed: true.

  • Default auth scheme is OAuth, matching Yandex API examples.

  • Keep the OAuth token out of shell history and MCP config files when possible.

Kurerok Workflow

Recommended daily/weekly sequence:

  1. yandex_get_sitemaps

  2. yandex_get_recrawl_quota

  3. yandex_get_search_queries

  4. yandex_get_pages_in_search_history

  5. yandex_get_indexing_history

  6. Build a curated URL queue from sitemap + Google winners.

  7. yandex_submit_recrawl_urls with confirmed: true.

Do not bulk-submit weak external-apply or low-value pages before fixing the Yandex vacancies feed and JobPosting/directApply semantics.

Available Tools

15 tools
yandex_add_sitemapC

Add a sitemap file to Yandex Webmaster. Requires confirmed=true.

Inputs: confirmed (required), sitemap_url (required), host_id.

yandex_get_diagnosticsC

Get Yandex Webmaster diagnostics for the site.

Inputs: host_id.

yandex_get_host_summaryC

Get site summary metrics from Yandex Webmaster.

Inputs: host_id.

yandex_get_indexing_historyC

Get crawl/indexing history for a date range.

Inputs: date_to (required), date_from (required), host_id.

yandex_get_pages_in_search_historyC

Get pages-in-search count history for a date range.

Inputs: date_to (required), date_from (required), host_id.

yandex_get_recrawl_queueC

Get Yandex recrawl queue/tasks.

Inputs: host_id.

yandex_get_recrawl_quotaB

Check remaining Yandex recrawl quota.

Inputs: host_id.

yandex_get_search_events_samplesB

Get sample pages added to or removed from Yandex search.

Inputs: host_id.

yandex_get_search_queriesC

Get Yandex search query metrics for a date range.

Inputs: date_to (required), date_from (required), host_id.

yandex_get_sitemapsB

List sitemap files known to Yandex Webmaster.

Inputs: host_id.

yandex_get_userA

Get the authenticated Yandex Webmaster user id.

Inputs: no named parameters.

yandex_list_hostsA

List sites available in Yandex Webmaster.

Inputs: no named parameters.

yandex_submit_recrawl_urlsB

Submit up to 150 URLs to Yandex recrawl queue. Requires confirmed=true.

Inputs: urls (required), confirmed (required), host_id.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of Yandex Webmaster, such as sitemaps, diagnostics, links, indexing, and search queries. There is no functional overlap, making it easy for an agent to select the correct tool.

    Naming Consistency5/5

    All tools follow a consistent 'yandex_<verb>_<object>' pattern in snake_case, using descriptive verbs like 'add', 'get', 'list', and 'submit'. The naming is predictable and uniform.

    Tool Count5/5

    With 15 tools, the set is well-scoped for a Yandex Webmaster API wrapper. It covers essential operations without being excessive, and each tool serves a clear purpose within the domain.

    Completeness5/5

    The tool set provides comprehensive coverage of Yandex Webmaster features, including sitemap management, diagnostics, link analysis, indexing history, search queries, recrawl operations, and user/host info. No obvious gaps are present.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      MCP server for interacting with Yandex.Webmaster API to manage sites, retrieve search queries, and check indexing status. Requires an OAuth token.
      13
      96 npm
      6
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      MCP server that provides 46 tools for managing Yandex Webmaster API v4, enabling site management, sitemaps, indexing, search analytics, and more through natural language.
      46
      30 npm
      7
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      This MCP server lets you query Yandex Webmaster data in plain language, covering search queries, indexing, diagnostics, sitemaps, backlinks, and recrawl status. It is read-only by default (except recrawl submission) and uses OAuth without storing secrets.
      10
      125 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Self-hosted MCP server for Google Search Console. Enables natural language queries to list sites, analyze search analytics, inspect URLs, and check sitemaps through AI assistants.
      MIT