Direct, Metrika, Wordstat and Webmaster MCP server
Yandex MCP Server
An MCP server with 141 tools: full Direct campaign management, Metrika counters and goals, Wordstat and Webmaster
- 0 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- It creates, stops and deletes campaigns, ads and keywords directly in the live Direct account
- metrika_delete_counter deletes a Metrika counter with its entire data history, with no way back
- Start with YANDEX_USE_SANDBOX=true and a minimally scoped token until you trust the agent's behavior
Install
- Works in
- Services
Manual install
git clone https://github.com/seklekov/yandex-direct-mcp.git && cd yandex-mcp && python -m venv .venv && source .venv/bin/activate && pip install -e .Install from source, then set YANDEX_TOKEN in .env.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- It creates, stops and deletes campaigns, ads and keywords directly in the live Direct account
- metrika_delete_counter deletes a Metrika counter with its entire data history, with no way back
- Start with YANDEX_USE_SANDBOX=true and a minimally scoped token until you trust the agent's behavior
This is third-party code. Review the repository files before installing.
What it does
A Python server exposes 141 tools across four Yandex APIs. Direct (80 tools) covers the full cycle: creating, pausing, archiving and deleting campaigns, ad groups and ads of every type, bids and modifiers, retargeting, smart ad targets, business cards, feeds, video and stats. Metrika (43 tools) manages counters, goals, segments, filters, access grants, and uploads offline conversions, calls and expenses. Wordstat (5 tools) returns query frequency, dynamics and regions. Webmaster (13 tools) adds and verifies sites, submits URLs for recrawl and reads popular queries. Create, update and delete tools exist almost everywhere: the server does not just read, it directly changes campaigns and counters.
Who it is for. For PPC specialists who want to run Direct campaigns and Metrika entirely through an agent.
Good fit when
- You need to not just read but create and change campaigns, ads, bids and goals from chat
- You want one server covering Direct, Wordstat, Webmaster and Metrika at once
- You are ready to test in the Direct sandbox before making live changes
Not a fit when
- You only need safe read-only access to reports: most of this server exposes delete and change operations
- You do not have time to review the agent's actions carefully before confirming
Example request
Pause the Summer sale campaign and raise the bid on the keyword buy iphone to 60 rublesMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
YANDEX_TOKENrequired, secret- OAuth token for Direct and Metrika, one shared token can be used
YANDEX_WORDSTAT_API_KEYsecret- Yandex Cloud service-account key for Wordstat via Search API v2
YANDEX_USE_SANDBOX- true routes Direct requests to the sandbox instead of the live account
Limitations
The package is not published to PyPI; install by cloning and pip install -e. Wordstat only works via the new Search API v2 with a Yandex Cloud service-account key, the old OAuth Wordstat API is shut down. Metrika can delete a counter entirely with all its data: the metrika_delete_counter tool is irreversible.
How to disable. Remove the yandex server from your MCP client settings and stop the process or container.
FAQ
Can it be tested without risking the live account?
Yes, setting YANDEX_USE_SANDBOX=true routes Direct requests to Yandex's sandbox.
What does Wordstat need?
A separate Yandex Cloud service-account key for Search API v2; the old OAuth Wordstat API no longer works.
Discussion
No questions or reviews yet.
Related
All Yandex Direct toolsAn MCP server for Yandex Direct, Metrika, Wordstat and Webmaster: campaigns, ads, bids, reports and keyword research from chat
A 155-tool MCP server for Yandex Direct, Metrika, Wordstat and Webmaster, with self-setup OAuth and read-only and confirm modes
A ZAI.ONE MCP server bringing Direct, Metrika, search, Wordstat and Webmaster into one agent, with a setup wizard and opt-in write operations
Yandex Metrika + Direct MCP Server
Яндекс.Метрика + Директ MCP Server
A 30-tool MCP server for Metrika and Direct: reports, bids, ads, negative keyword management and Wordstat
An MCP server for Yandex Direct, Metrica, Wordstat and Audience analytics: raw reports, data joins and an HTML dashboard
Five MCP servers for Yandex Search, Wordstat, Webmaster, Metrika and Direct, bundled as a Claude Code plugin with two skills
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Direct, Metrika, Wordstat and Webmaster MCP server (this card) | no | API key | 0 | |
| Yandex Direct MCP, CLI and models with action search | no | API key | 1 | 79 actions |
| yandex-direct-mcp | no | API key | 0 | campaigns, reports |
README in short
The English README (with a README.ru.md counterpart) lists all 141 tools across four APIs, grouped into campaigns, ads, bids, retargeting and feeds among others, gives environment variables for separate Direct and Metrika tokens, example user phrasing, three run methods including Docker, and a security section advising sandbox use and minimum token scopes.