YaAll
Monorepo of Yandex MCP servers: Direct, Metrica, Webmaster, Wordstat, Tracker, 360, Maps, SpeechKit, YandexGPT and AppMetrica
Install
{
"mcpServers": {
"yandex-direct": { "command": "npx", "args": ["-y", "@theyahia/yandex-direct-mcp"],
"env": { "YANDEX_DIRECT_TOKEN": "..." } },
"yandex-metrika": { "command": "npx", "args": ["-y", "@theyahia/yandex-metrika-mcp"],
"env": { "YANDEX_METRIKA_TOKEN": "..." } }
}
}File ~/.claude.json or claude_desktop_config.json. Other servers follow the same pattern; variables are in each mcp/ folder's README.
This is third-party code. Review the repository files before installing.
What it does
The repo gathers the author's ten MCP servers for Yandex APIs, each published to npm as a separate @theyahia package and run via npx. The largest, for Direct, covers campaigns, strategies, ads, keywords, bids, negative keywords, audiences, feeds and statistics with ruble amounts and sandbox support. A separate server exposes Wordstat statistics through the Search API, which Yandex's official servers lack. The skills folder holds Claude Code skills: a site audit against EPOS criteria, demand checks via Wordstat and ready scenarios on top of the servers. The author's separate repos that formed the set are now archived.
Who it is for. PPC and SEO specialists, analysts and teams working in the Yandex ecosystem.
Good fit when
- You need to review Direct campaign performance and adjust bids or negative keywords
- You need Wordstat frequency and seasonality before a launch
- You need a weekly Metrica traffic report
- You need indexing and search queries from Webmaster
Not a fit when
- You need an official Yandex server: this set is community-built
- The agent must not access the ad budget
Example request
Show weekly stats for active Direct campaigns, find high-CPC keywords without conversions and suggest negative keywordsLimitations
There is no shared key: each server needs its own product token, while Wordstat and the skills need a Search API key and a Yandex Cloud folder ID with the right service account role. Search API is paid, and a 403 often means an empty billing account. The EPOS audit skill requires Python 3.12 or newer. Each server's exact variables are in its own README.
How to disable. Remove the yandex-* blocks from ~/.claude.json or your client config and delete the skills from ~/.claude/skills.
MCP
- Transport
- stdio
- Authentication
- OAuth
| Environment variables | |
|---|---|
| YANDEX_DIRECT_TOKEN secret | Direct OAuth token for yandex-direct-mcp |
| YANDEX_METRIKA_TOKEN secret | Metrica OAuth token for yandex-metrika-mcp |
| YANDEX_SEARCH_API_KEY secret | Search API key for the Wordstat skills |
| YANDEX_FOLDER_ID | Yandex Cloud folder ID |
Security check
- The Direct server changes bids, campaigns and ads, affecting budget spend
- Needs several tokens with access to ads, analytics, mail and disk
- Search API requests are paid
README in short
The Russian README, with a short English section, explains which server fits which role and lists ten servers with their purpose. The quick start shows npx configs for Direct and Metrica. It separately covers the skills, snapshots of official Yandex material in upstream and three authorization mechanisms that are easy to confuse. It states what was deliberately left out. Code and skills are MIT, Yandex material is Apache 2.0.
FAQ
How does it differ from Yandex's official MCP?
The official Yandex Cloud and Search API servers sit in upstream only as a snapshot. The author's own servers cover ads, analytics and Wordstat, which the official ones lack.
Can I install just one server?
Yes, each server is a separate npm package, so add only what you need.
Related
A Claude Code plugin for SEO audits: technical SEO, E-E-A-T, schema, local and AI search via parallel subagents
A Claude Code skill set for auditing sites for AI search: citability, AI crawler access, llms.txt, schema and reports
The experimental official Google Analytics 4 MCP server: reports, funnels and realtime data on request
Google Search Console MCP
Google Search Console MCP Server for SEOs
An MCP server for Google Search Console: queries and pages with clicks and positions, URL indexing checks, sitemaps and ready SEO skills