Yandex Wordstat MCP
An MCP server for Yandex Wordstat via the official Yandex Cloud Search API: frequency, related queries, dynamics and regions
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- Only reads search query statistics, changes nothing in accounts
- Search API calls are billed, so watch the spend
Install
Manual install
pipx install git+https://github.com/N1arko/yandex-wordstat-mcp.gitThe main README method: install an isolated package via pipx.
This is third-party code. Review the repository files before installing.
What it does
The server gives an agent four tools over the Wordstat API: wordstat_top_requests returns popular and related queries for a phrase, wordstat_dynamics shows demand dynamics over a date range, wordstat_get_regions_tree returns Yandex's region tree, and wordstat_find_region looks up a region ID by name. Region 225 (all of Russia) is the default. The README shows how an agent chains the calls, find the region, check top queries, then dynamics, and turns the results into a marketer-facing read on commercial vs. informational intent.
Who it is for. For marketers who build keyword lists and check demand seasonality directly in a Codex or Claude Desktop conversation.
Good fit when
- You need a quick demand check on a phrase and related wordings
- You need a year of seasonality data to plan a campaign launch
- You need a Yandex region ID by city name
Not a fit when
- You have no Yandex Cloud account with Search API access
- You need automatic clustering or negative-keyword collection: the server returns only raw data
Example request
Check the seasonality of "kids summer camp" over the last year across Russia and tell me when to launch the campaignLimitations
You need YC_SEARCH_API_KEY (or YC_IAM_TOKEN) and YC_FOLDER_ID from Yandex Cloud, and calls are billed. Stop words are not applied by default; ask the agent explicitly. The smoke test in scripts/ needs real credentials.
How to disable. Remove the yandex_wordstat entry from your MCP client config, and if installed via pipx, run pipx uninstall yandex-wordstat-mcp.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| YC_SEARCH_API_KEY required, secret | Service account API key with the yc.search-api.execute scope. |
| YC_FOLDER_ID required | Yandex Cloud folder ID. |
| YC_IAM_TOKEN secret | An alternative to the API key. |
Security check
- Only reads search query statistics, changes nothing in accounts
- Search API calls are billed, so watch the spend
README in short
The Russian README explains why the server exists, gives a ready-made phrase for an agent to self-install it, a table of the required Yandex Cloud variables, example marketing tasks, a tool table, and a detailed troubleshooting section for common auth errors.
FAQ
What region is used if none is specified?
225, all of Russia. For Moscow specifically, pass region 213.
Do I need a Yandex Direct account?
No, access goes through the Yandex Cloud Search API via a service account with the search-api.webSearch.user role.
Related
Official DataLens (Yandex) skills for Claude Code, Codex and OpenCode: SDK, HTML reports and RLS resolution
A Yandex Metrika MCP server generated from the API spec: 108 methods, 10 tools declared by default, transparent filters and response metadata
An open MCP server and agent skill set for SEO: keyword research, competitors, backlinks and site audits powered by DataForSEO
A Claude Code plugin for SEO audits: technical SEO, E-E-A-T, schema, local and AI search via parallel subagents