Wordstat MCP in Go: Yandex query stats for an AI agent
yandex-wordstat-mcp-golang
A Go MCP server with four Wordstat tools and Bearer-token access: top queries, dynamics and regions
- 0 ★ on the repository
- Last commit
Extended access
Why this level
- Wordstat calls are billed by Yandex: an unbounded agent loop spends the balance
- The Yandex Cloud key and the server token live in the container environment, and a leak gives a stranger access
Install
- Works in
- Services
Manual install
docker compose up --buildSet `WORDSTAT_API_KEY`, `WORDSTAT_FOLDER_ID` and `WORDSTAT_MCP_TOKEN`; the README has no instructions, `Dockerfile` and `docker-compose.yml` are in the root.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Wordstat calls are billed by Yandex: an unbounded agent loop spends the balance
- The Yandex Cloud key and the server token live in the container environment, and a leak gives a stranger access
This is third-party code. Review the repository files before installing.
What it does
A Go MCP server sends requests to the Yandex Wordstat API (Search API v2, `searchapi.api.cloud.yandex.net/v2/wordstat/`) and gives the agent four tools: top and related queries for a phrase over 30 days (`top_requests`), frequency dynamics, regional distribution and the region tree. It runs over Streamable HTTP, default port 8080, and access is closed by a Bearer token from `WORDSTAT_MCP_TOKEN`. The Yandex Cloud key and folder id come from `WORDSTAT_API_KEY` and `WORDSTAT_FOLDER_ID`. The client retries on 429 and 5xx (three attempts in total), limits the call rate and caches responses. The repository has a `Dockerfile`, `docker-compose.yml`, a `Makefile` and tests.
Who it is for. SEO specialists and marketers who want Wordstat in an agent and one shared team server with a token instead of a key for everyone.
Good fit when
- The agent picks keyword phrases and checks frequency for Moscow or Russia itself
- You need demand dynamics by week or month to plan content
- A team prefers one HTTP server with a token to Yandex Cloud keys on every computer
- You need to compare interest in a phrase across regions and cities
Not a fit when
- You need a local stdio server without Docker and a network: the only transport here is Streamable HTTP
- You need detailed docs and setup examples: the README is empty and you have to work from the code
- You must process phrases in batches of hundreds: the Search API quota is shared and every call is billed
Example request
Show the top queries for the phrase "buy a coffee machine" over 30 days for region 213 and the monthly dynamicsMCP
- Transport
- http
- Authentication
- API key
Environment variables
WORDSTAT_API_KEYrequired, secret- Yandex Cloud key with Search API access
WORDSTAT_FOLDER_IDrequired- Yandex Cloud folder id
WORDSTAT_MCP_TOKENsecret- Bearer token for access to the MCP server itself
WORDSTAT_HTTP_ADDR- HTTP server address and port, port 8080 by default
Limitations
The repository is small: zero stars, last commit in October 2026 and an empty README, so installation and client setup have to be worked out from `Dockerfile`, `docker-compose.yml` and the sources. There is one transport, Streamable HTTP, and no stdio. A Yandex Cloud key with Search API access and a folder id are required. Wordstat calls are billed by Yandex, and the cache and rate limiter only soften the spend. Frequencies cover the last 30 days, and the dynamics period is set in the parameters.
How to disable. Remove the server from the MCP client settings, stop the container and delete the `WORDSTAT_API_KEY` key and the `WORDSTAT_MCP_TOKEN` token.
FAQ
Which tools are there?
Four: top queries `top_requests`, frequency dynamics, regional distribution and the region tree.
Where do I get the key?
In Yandex Cloud: an API key with Search API access and a folder id, passed in `WORDSTAT_API_KEY` and `WORDSTAT_FOLDER_ID`.
How is access to the server protected?
With a Bearer token: the value comes from `WORDSTAT_MCP_TOKEN` and the client sends it in the Authorization header.
Can it run without Docker?
Yes, it is an ordinary Go project with the entry point `cmd/server/main.go`, but the README has no ready instructions.
What about request limits?
The client limits the rate, caches responses and retries on 429 and 5xx up to three attempts.
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
Yandex Search and Wordstat MCP: web_search and phrase stats
mcp-yandex-search
An MCP server on a single AI Studio key: four Wordstat methods, search over the Yandex index and a raw request to the Wordstat API
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
An MCP server for Yandex Wordstat via the Yandex Cloud Search API: frequency, dynamics, regions and an operator-aware phrase builder
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
README in short
The README is practically empty and holds only a directory tree. The description comes from the code and from `tech.md` with the server requirements: Streamable HTTP transport, port 8080, error handling and security.