Yandex Webmaster, Direct and Metrika MCP server
yandex-mcp
An MCP server with 125 tools for Yandex Webmaster, Direct and Metrika, multiple projects and tokens in one process
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- Write tools change campaigns, bids, ads and goals in Direct and Metrika
- It can upload offline conversions and CRM orders that affect the client's statistics
- Start with a read-only token or the Direct Sandbox until you have verified the server's behavior
Install
Manual install
npm install && npm run buildBuild from source after cloning; set the token in .env as YANDEX_OAUTH_TOKEN.
This is third-party code. Review the repository files before installing.
What it does
A TypeScript server combines three Yandex APIs in one stdio MCP process: 52 Webmaster tools (indexing, sitemaps, diagnostics, links, recrawl, feeds), 43 Direct tools (campaigns, ad groups, ads, bids, reports) and 22 Metrika tools (counters, goals, expense and CRM import, Logs API, Stat API). It ships 6 ready prompt scenarios such as a campaign audit or a weekly report. The server supports several projects with different tokens at once, and Direct and Metrika write tools require confirm true and respect the project's budget and bid change limits.
Who it is for. For marketers and agencies who manage Yandex search, ads and analytics for several projects from one agent.
Good fit when
- You want one server for Yandex SEO, ads and analytics together
- You manage several projects or client accounts with different tokens
- You need guarded Direct write tools with diffs and budget limits
Not a fit when
- You only need one of the three services: a narrower single-purpose server is simpler
- You lack Direct access: the access request is submitted from the Direct account separately from Webmaster and Metrika
Example request
Check site indexing in Webmaster and show Direct campaign spend and conversions for the weekLimitations
The Webmaster token expires after 6 months and must be reissued. Direct access must be requested separately after registering the app; until approved, only the Direct Sandbox is available. The package is not published to the npm registry; the README only shows building from source and running locally with node.
How to disable. Remove the yandex server from your MCP client settings and stop the node process.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| YANDEX_OAUTH_TOKEN required, secret | Yandex OAuth token for Webmaster and Metrika; Direct needs separately approved access |
Security check
- Write tools change campaigns, bids, ads and goals in Direct and Metrika
- It can upload offline conversions and CRM orders that affect the client's statistics
- Start with a read-only token or the Direct Sandbox until you have verified the server's behavior
README in short
The README lists all 125 tools by group with the yandex_webmaster_, yandex_direct_ and yandex_metrika_ prefixes, explains getting an OAuth token and the specifics of requesting Direct access. It separately covers the multi-project projects.json configuration with active project switching and budget limits, plus the src directory layout.
FAQ
Can the server's Direct changes be limited?
Yes, the project config sets a maximum budget and bid change percentage, and write tools preview a diff by default without applying it.
Do I need a separate token per API?
One OAuth token covers Webmaster and Metrika with the right scopes; Direct needs a separate access request.
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