yandex-wordstat-mcp by nikolaymokh-dev
yandex-wordstat-mcp
A Wordstat MCP server via the Yandex Search API that estimates and tracks request cost before and after each call
- 0 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Starts a server via uvx that reads Wordstat statistics with a Yandex Cloud key
- Requests are paid, the server keeps a local log and estimates cost in advance
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/nikolaymokh-dev-yandex-wordstat-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Starts a server via uvx that reads Wordstat statistics with a Yandex Cloud key
- Requests are paid, the server keeps a local log and estimates cost in advance
This is third-party code. Review the repository files before installing.
What it does
A thin wrapper over the Wordstat methods of the Yandex Search API: top queries with related phrases, frequency dynamics by month/week/day, regional distribution with an affinity index, and the region code tree. Separately from Wordstat itself, the server keeps a local call log and offers two cost-tracking tools: wordstat_cost_report for a summary of actual spend, and wordstat_cost_estimate to price a batch of requests before the agent sends them.
Who it is for. For anyone who wants visibility into paid Search API spend both before and after an agent makes requests.
Good fit when
- You need Wordstat frequency and dynamics with transparent cost tracking
- You want to price a batch of requests before a large keyword-collection run
- You want a one-line uvx install straight from GitHub, no cloning
Not a fit when
- You have no card attached to Yandex Cloud billing: without it the Search API often returns 403
- You need tools beyond the four Wordstat API methods
Example request
Estimate how much it would cost to check yearly dynamics for 50 phrases before running itMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
YANDEX_SEARCH_API_KEYrequired, secret- Yandex Cloud API key with the yc.search-api.execute scope.
YANDEX_FOLDER_IDrequired- Yandex Cloud folder ID from the console, part of the URL after /folders/.
Limitations
Requires a card attached to Yandex Cloud billing (even with no real spend), a key with the yc.search-api.execute scope, and the search-api.webSearch.user role. Secrets are read from the environment at launch only; a local .env file is not picked up automatically.
How to disable. Run claude mcp remove yandex-wordstat, or remove the server entry from your client config.
FAQ
Why does the Search API return 403?
Usually there's no card attached to Yandex Cloud billing, or the key has the wrong scope, the README covers both cases.
How do I see how much I've already spent?
The wordstat_cost_report tool summarizes spend from the local call log.
Discussion
No questions or reviews yet.
Related
All Yandex Wordstat toolsAn MCP server for Yandex Wordstat via the official Yandex Cloud Search API: frequency, related queries, dynamics and regions
An MCP server for Yandex Wordstat via the Yandex Cloud Search API: frequency, dynamics, regions and an operator-aware phrase builder
Yandex Wordstat MCP Server by khanton
Yandex Wordstat MCP Server
A compact TypeScript MCP server for Yandex Wordstat via the Yandex Search API: top queries, dynamics and regions
Wordstat MCP Server: Yandex frequencies with limits and a cache
wordstat-mcp-server
An unofficial read-only Wordstat MCP server in TypeScript: five tools, local call limits, a region cache and spend counters
Yandex Wordstat MCP
Яндекс Вордстат MCP
Wordstat MCP server via Yandex Cloud Search API: query volume and related queries, seasonality, demand by region and device
Yandex Wordstat MCP with budget control
@cododel/yandex-wordstat-mcp
A Bun-based MCP server for the official Yandex Wordstat API v2, with per-call cost tracking and spending limits in rubles
README in short
The Russian README describes a one-command uvx install straight from GitHub, a step-by-step Yandex Cloud setup with card binding and role assignment, a tool table including two extra cost-tracking tools, and a table of common 401/403 errors.