Wordstat Readonly MCP
A read-only MCP server for Yandex Wordstat statistics: top phrases, dynamics, regions, with OAuth sign-in for ChatGPT
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- The server is deliberately limited to read methods; no mutations or other Yandex Cloud services exist in the code
- The Yandex key stays only on the server and is never passed to the model directly in the OAuth variant
Install
Manual install
git clone https://github.com/zimuspro156-lab/mcp-wordstat-readonly.git && cd mcp-wordstat-readonly && npm ciLocal install for stdio use; then npm test and npm run check to verify.
This is third-party code. Review the repository files before installing.
What it does
The server wraps Wordstat methods via the Yandex Cloud Search API and deliberately excludes anything that could change data in Yandex: just five read tools, top queries over 30 days, monthly/weekly/daily dynamics, regional distribution, the region code tree, and a status check that reports configuration without revealing keys. It runs locally over stdio (e.g. for Cursor), and for ChatGPT Web it's hosted on your own server behind a Cloudflare tunnel with OAuth 2.0 + PKCE sign-in: the Yandex key stays on the server, and ChatGPT gets a separate MCP login rather than the API key itself.
Who it is for. For anyone who wants to give ChatGPT or Cursor access to Wordstat statistics without the risk of an agent changing anything in Yandex Cloud.
Good fit when
- You need Wordstat access from ChatGPT Web via OAuth rather than a local process
- It matters that the server physically cannot change anything, only read
- You need a local stdio option for Cursor without deploying a server
Not a fit when
- You don't want to run an Ubuntu VPS and a Cloudflare tunnel for the OAuth variant
- You need tools this server doesn't have: a phrase builder, clustering, other Yandex Cloud services
Example request
Show the top queries for "washing machine repair" and how demand changed over the last yearLimitations
The full ChatGPT scenario needs your own server (Ubuntu VPS) and setup per a separate DEPLOY.md, not a one-line install. You need a Yandex Cloud Search API key and YANDEX_FOLDER_ID. The project is not an official Yandex product; MIT license.
How to disable. For Cursor, remove the server entry from your MCP config. For the hosted variant, stop the wordstat-readonly-mcp systemd service and remove the Cloudflare tunnel.
MCP
- Transport
- stdio, http
- Authentication
- OAuth
| Environment variables | |
|---|---|
| YANDEX_FOLDER_ID required | Yandex Cloud folder ID. |
Security check
- The server is deliberately limited to read methods; no mutations or other Yandex Cloud services exist in the code
- The Yandex key stays only on the server and is never passed to the model directly in the OAuth variant
README in short
The Russian README gives a table of five read tools with their API methods, an architecture diagram from ChatGPT through a Cloudflare tunnel to the Search API, links to separate docs for Ubuntu install, usage examples and AI setup, and explicitly states the project is not an official Yandex product.
FAQ
Can this server change anything in Yandex Cloud?
No, it deliberately includes only Wordstat read methods; mutations and other Yandex Cloud services are excluded.
Does ChatGPT get the Yandex key directly?
No, sign-in goes through a separate MCP OAuth login; the Yandex key stays only on the server.
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