Developer · Local MCP server
Yandex Wordstat MCP
MCP server for Yandex Wordstat API: top & related queries, demand dynamics and regions.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.askads/mcp-yandex-wordstat- Version
- 2.3.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-18
- Updated
- 2026-08-18
- Publisher
- askads (GitHub) · 5 servers with pages here
- Website
- github.com/askads/mcp-yandex-wordstat#readme
- Repository
- github.com/askads/mcp-yandex-wordstat
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | mcp-yandex-wordstat | 2.3.0 | stdio |
How to connect Yandex Wordstat MCP
Yandex Wordstat MCP runs locally from a Node.js package published to the npm registry: mcp-yandex-wordstat version 2.3.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y mcp-yandex-wordstat@2.3.0. It reads these environment variables: WORDSTAT_API_KEY (required, secret), WORDSTAT_FOLDER_ID (required), WORDSTAT_LANG, WORDSTAT_API_BASE, WORDSTAT_TIMEOUT_MS and WORDSTAT_MAX_RETRIES; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp-yandex-wordstat": {
"command": "npx",
"args": [
"-y",
"mcp-yandex-wordstat@2.3.0"
],
"env": {
"WORDSTAT_API_KEY": "<secret>",
"WORDSTAT_FOLDER_ID": "<value>",
"WORDSTAT_LANG": "<value>",
"WORDSTAT_API_BASE": "<value>",
"WORDSTAT_TIMEOUT_MS": "<value>",
"WORDSTAT_MAX_RETRIES": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from askads (GitHub)
| Server | Runs |
|---|---|
| VK Ads MCPMCP server for VK Ads (VK Реклама) API: manage ad plans, ad groups, banners, and statistics. | Local · stdio |
| Yandex Direct MCPMCP server for Yandex Direct API v5: manage PPC campaigns, ads, keywords, and statistics. | Local · stdio |
| Yandex Metrica MCPMCP server for Yandex Metrica API: list counters, goals and pull web-analytics statistics. | Local · stdio |
| Yandex Webmaster MCPMCP server for Yandex Webmaster API: indexing, search queries, sitemaps, diagnostics, links. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| Yandex Metrica MCPQuery Yandex Metrica analytics — reports, trends, metadata and raw log exports — via an AI agent. | Local · stdio |
| Yandex MetrikaMCP server for Yandex Metrika API — counters, goals, reports, segments, logs. | Local · stdio |
| Yandex Webmaster MCPMCP server for Yandex.Webmaster API — hosts, search queries, indexing status. Bearer token auth. | Local · stdio |
| yandex-direct-mcpMCP server for Yandex Direct — PPC campaigns, ads, keywords, statistics (Russia) | Local · stdio |
| yandex-metrika-mcpMCP server for Yandex Metrika — web analytics, counters, goals, traffic (Russia) | Local · stdio |
| YandexbotValidate whether an IP address belongs to YandexBot. Remote MCP server exposing a validate_ip tool. | Remote · HTTP |
| yandexgpt-mcpMCP server for YandexGPT — completions, embeddings, classification, summarization (Russia) | Local · stdio |