Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
6,000+ web scrapers for your AI agent, start free logo6,000+ web scrapers for your AI agent, start free

Apify gives your agent live web data: 6,000+ prebuilt scrapers and actors, MCP-ready. Sign up free with $5 in usage credits.

Try Apify free
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 48,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

Local-first MCP server for Yandex Webmaster that exposes tools for SEO operations including search query analytics, sitemap management, indexing history, recrawl quota, and diagnostics.

README.md

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.

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.

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Search servers.