yandex-mcp
A dependency-free, mostly read-only MCP server for Metrika, Webmaster, Direct and Wordstat, with the token kept in Keychain
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Reads Direct ad account data and site analytics, including campaign spend
- Can queue pages for Webmaster recrawl, the only write action, which requires confirmation
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/nozikov-yandex-mcpDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Run one by one in the Claude Code chat
/plugin marketplace add nozikov/yandex-mcp
/plugin install yandex-mcp@nozikovIn Claude Code run /plugin marketplace add nozikov/yandex-mcp and /plugin install yandex-mcp@nozikov, then run yandex-mcp setup to register the application with Yandex and tell the agent to connect Yandex to complete login.
Other ways from the author
/plugin marketplace add nozikov/yandex-mcp
/plugin install yandex-mcp@nozikovInstalls the server together with the site-weekly and seo-opportunities skills.
This is third-party code. Review the repository files before installing.
What it does
The server gives an agent 15 tools across four Yandex services: Metrika summaries, period comparisons and custom reports, Webmaster's quality index and search query stats with page recrawl as the only write action, requiring explicit confirmation, Direct campaigns and spend, and Wordstat phrase frequency. It is written with zero third-party libraries, because it handles access to analytics and an ad account, and less foreign code is safer, per the author. Login happens right in the conversation with the agent via PKCE with no application password, and the token is stored in the system's appropriate secure store: Keychain on macOS, secret-tool on Linux, or a 0600 file, chosen automatically. Installing the Claude Code plugin also installs two ready skills: a weekly site report and a search for queries sitting just below the first page.
Who it is for. For SEO and PPC specialists who want unified Yandex analytics in a conversation with an agent, with minimal trust placed in third-party code.
Good fit when
- You want a quick weekly report on traffic, search and ads in one command
- You want to find queries that are just short of ranking on the first page
- It matters that the token and data never pass through a third-party server and are stored securely
Not a fit when
- You need to manage Direct campaigns, change bids or budgets: the server only reads Direct, and apart from Webmaster recrawl there is no other write action
- You need Direct access immediately: the direct:api scope takes up to 7 days for Yandex to approve
Example request
How has traffic changed over the past month, and where did the growth come from?Limitations
Direct access needs separate approval of the direct:api scope in the dashboard, which can take up to 7 days; until then the server logs in without Direct. Registering your own OAuth application with Yandex is required before the first login, though the setup command simplifies it. The only write action, Webmaster page recrawl, requires explicit confirmation.
How to disable. Run yandex-mcp logout to remove the token from storage, and remove the server from your MCP client config.
Security check
- Reads Direct ad account data and site analytics, including campaign spend
- Can queue pages for Webmaster recrawl, the only write action, which requires confirmation
README in short
The Russian README, with diagrams, explains that the server runs locally and talks to the Yandex API directly with no server in between, and is written with zero third-party libraries. It shows three install paths: the Claude Code plugin, Codex CLI, and any client via PyPI and uvx. The login section covers registering an OAuth application via the setup command, PKCE with no password, and Direct access appearing gradually after the direct:api scope is approved. It gives a tool table for Metrika, Webmaster, Direct and Wordstat, two Claude Code skills, and a section on automatic secure token storage selection. It separately explains the choice of 15 tools instead of full API coverage, to save the model's context.
FAQ
Why only 15 tools instead of a hundred?
The author explains that every tool's description goes into the model's context on each call, so the set is deliberately limited to the essentials instead of full API coverage.
Can the server change Direct campaigns or bids?
No, Direct is read-only: campaigns, spend and reports; the server's only write action anywhere is Webmaster page recrawl, and it requires confirmation.
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