Yandex MCP
A ZAI.ONE MCP server bringing Direct, Metrika, search, Wordstat and Webmaster into one agent, with a setup wizard and opt-in write operations
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
- Direct supports controlled campaign changes when enabled
- Tests cover Metrika write scenarios, indicating write operations exist
- Wordstat and the Search API spend a metered Yandex Cloud quota
Install
Manual install
git clone https://github.com/zai-one/yandex-mcp.git
cd yandex-mcp
uv sync --frozen --extra standalone
uv run --frozen --extra standalone python scripts/configure.py
uv run --frozen --extra standalone yandex-mcp --config mcp.local.json --check-configInstall from source with the setup wizard, requires Python 3.12-3.14 and uv.
This is third-party code. Review the repository files before installing.
What it does
The server connects an agent to five Yandex API groups at once. Direct gives campaigns, available inventory and statistics, with changes enabled separately and subject to the service's permissions and the server's policy. Metrika gives counters, goals, filtered reports, period comparison and CSV export with sampling metadata. The Search API runs asynchronous Yandex search jobs with saved results. Wordstat shows top queries, demand trends, regional distribution and the region tree, via Yandex Cloud with explicit cost limits. Webmaster gives indexing and site diagnostics, query stats, sitemap handling and recrawl. Setup runs through the scripts/configure.py wizard, which creates a local configuration and stores secrets in private files per API group separately, starting with Metrika. Metrika Logs export and interactive in-chat OAuth setup are not included.
Who it is for. For digital agencies and specialists who juggle ads, analytics, SEO and search visibility on Yandex at the same time.
Good fit when
- You want data from several Yandex services in one agent instead of five separate servers
- You want a setup wizard that walks you through getting credentials for each service step by step
- You need a CSV export of Metrika reports with sampling metadata
Not a fit when
- You need fully open-source code: the LicenseRef-ZAI-ONE license explicitly is not open source, and use is permitted only for your own accounts
- You need raw Metrika log exports: the README explicitly states Metrika Logs export is not included
Example request
Show my Metrika counters, then for the one I pick compare visits and goal conversions over two equal periods and highlight the biggest changesLimitations
The LicenseRef-ZAI-ONE license is not open source and permits install and use only for your own accounts. Each API group needs its own credentials, obtained and configured separately per its own instructions. The Search API needs a separate worker and a Yandex Cloud folder ID, and Wordstat has explicit cost limits via Cloud. Interactive OAuth setup and Metrika Logs API export are not implemented.
How to disable. Remove the server from your MCP client config and delete the mcp.local.json file holding the saved secrets.
MCP
- Transport
- stdio, http
- Authentication
- API key
Security check
- Direct supports controlled campaign changes when enabled
- Tests cover Metrika write scenarios, indicating write operations exist
- Wordstat and the Search API spend a metered Yandex Cloud quota
README in short
The bilingual README presents the server as a way to bring Yandex advertising, analytics and search into one conversation with an agent. A table ties five API groups to tasks: Direct, Metrika, Search API, Wordstat, Webmaster. The quick start shows installing a ready package or building from source via uv and the scripts/configure.py wizard, which creates a local configuration and stores secrets separately per service. It gives an MCP client config example and a first verification request. The Access and limits section honestly lists what the server does not do: interactive OAuth setup and Metrika log exports. It states the LicenseRef-ZAI-ONE license, which is not open source, with the ZAI.ONE agency as author.
FAQ
Can the server be used without setting up all five services?
Yes, the setup wizard starts with Metrika; other API groups, including Direct, Webmaster and Yandex Cloud for Wordstat and search, are configured as needed.
Is the project open source?
No, the README explicitly states the LicenseRef-ZAI-ONE license is not open source, and use is permitted only for your own accounts.
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