kurerok-yandex-webmaster-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@kurerok-yandex-webmaster-mcpget my search queries for the last 7 days"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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-mcpfor the multi-package Yandex API direction.theYahia/yandex-webmaster-mcpfor a compact Webmaster-only surface.yandex/yandex-search-mcp-serverfor official Yandex MCP packaging ideas.
It does not require sending OAuth tokens to a hosted third party.
Tools
Read-only:
yandex_get_useryandex_list_hostsyandex_get_host_summaryyandex_get_diagnosticsyandex_get_sitemapsyandex_get_search_queriesyandex_get_indexing_historyyandex_get_pages_in_search_historyyandex_get_search_events_samplesyandex_get_recrawl_quotayandex_get_recrawl_queueyandex_get_external_linksyandex_get_broken_internal_links
State-changing, quota-sensitive:
yandex_add_sitemapyandex_submit_recrawl_urls
Both require confirmed: true.
Related MCP server: SEO MCP Connector
Setup
npm install
npm run buildCreate 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:
yandex_get_sitemapsyandex_get_recrawl_quotayandex_get_search_queriesyandex_get_pages_in_search_historyyandex_get_indexing_historyBuild a curated URL queue from sitemap + Google winners.
yandex_submit_recrawl_urlswithconfirmed: true.
Do not bulk-submit weak external-apply or low-value pages before fixing the Yandex vacancies feed and JobPosting/directApply semantics.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/shutovdef-dotcom/kurerok-yandex-webmaster-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server