Yandex Ads MCP Server
An MCP server for Yandex Direct, Metrica, Audiences and Wordstat with read-only mode and change confirmation
- 47 ★ on the repository
- Last commit
Broad access
Why this level
- Creates campaigns and changes bids and budgets in the live account, spending money
- Uploads customer CRM data such as emails and phones to Audiences
- Safety modes are off by default
Install
- Works in
- Services
Manual install
git clone https://github.com/Yurich-ru/yandex-ads-mcp.git
cd yandex-ads-mcp
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txtAfter install copy .env.example to .env and fill in the tokens.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Creates campaigns and changes bids and budgets in the live account, spending money
- Uploads customer CRM data such as emails and phones to Audiences
- Safety modes are off by default
This is third-party code. Review the repository files before installing.
What it does
The server covers the Yandex advertising cycle from one place. In Direct the agent creates and changes campaigns, ad groups, ads including responsive ones, keywords and autotargeting, bids, bid modifiers, negative keywords and extensions, and pulls reports. Metrica offers counters, goals, segments, reports and uploads of offline conversions and costs; Audiences builds segments from CRM data, lookalikes and geo segments; Wordstat gives volumes, trends and regions. For live accounts it has read-only mode, a preview mode that requires confirmation, a client login allowlist and multi-account support.
Who it is for. For PPC specialists and agencies running Yandex Direct campaigns.
Good fit when
- You need to bulk-create ad groups, ads and keywords in Direct from a plan
- You want Direct costs matched against Metrica goals in one report
- An agency needs to work across several client accounts with restricted access
Not a fit when
- You only need Wordstat without ad account access
- You are not ready to enable YD_READONLY or YD_CONFIRM on a live account
Example request
Show last week's Direct costs and conversions by campaign and suggest where to lower bids without changing anything until I confirmMCP
- Transport
- stdio
- Authentication
- OAuth
Environment variables
YD_OAUTH_TOKENrequired, secret- OAuth token with Direct, Metrica, Audiences and Yandex Cloud access
YC_FOLDER_ID- Yandex Cloud folder ID for Wordstat
YC_API_KEYsecret- Service account API key for Wordstat
YD_READONLY- true blocks all write tools
YD_CONFIRM- true requires confirmation for each change
YD_ALLOWED_LOGINS- Allowlist of agency client logins
YD_SANDBOX- true enables the Direct sandbox
Limitations
Requires your own Yandex OAuth app with Direct, Metrica, Audiences and Yandex Cloud access, plus an approved Direct API application. Wordstat needs a Yandex Cloud billing account with a folder and the search-api.webSearch.user role, and newer tokens also need a service account API key. There is no package; install from a clone into a Python virtualenv. Safety modes are off by default, and the repository has no license file.
How to disable. Remove the yandex-ads block from ~/.claude.json or the client config and revoke the OAuth token in Yandex ID settings.
FAQ
How do I stop the agent from changing a live campaign by accident?
Set YD_READONLY=true to block write tools before any network call, or YD_CONFIRM=true so each change first returns a preview and runs only with confirm=true.
What if Direct and Metrica are in different accounts?
Issue a token in each account and set YD_OAUTH_TOKEN for Direct and YD_METRIKA_TOKEN and YD_AUDIENCE_TOKEN for Metrica and Audiences.
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
An MCP server for Yandex Direct, Metrica, Wordstat and Audience analytics: raw reports, data joins and an HTML dashboard
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
A ZAI.ONE MCP server bringing Direct, Metrika, search, Wordstat and Webmaster into one agent, with a setup wizard and opt-in write operations
A 155-tool MCP server for Yandex Direct, Metrika, Wordstat and Webmaster, with self-setup OAuth and read-only and confirm modes
Monorepo of Yandex MCP servers: Direct, Metrica, Webmaster, Wordstat, Tracker, 360, Maps, SpeechKit, YandexGPT and AppMetrica
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Yandex Ads MCP Server (this entry) | no | OAuth | 47 | |
| Yandex Direct MCP: hardened fork | no | OAuth | 0 | a fork read-only by default with write flags |
| Yandex Direct, Metrica and Wordstat MCP: fork with responsive ads | no | OAuth | 0 | combinatorial ads |
README in short
The Russian README covers installing from a clone into a virtualenv and connecting to Claude Code. It details getting an OAuth token, applying for Direct API access and setting up Yandex Cloud for Wordstat. It includes an environment variable table, a section on safety modes and multi-account use, and a full tool list per service with parameter examples for complex calls.