Yandex Direct, Metrica and Wordstat MCP: fork with responsive ads
Yandex Direct MCP Server
A 120-tool fork of Yandex Ads MCP that adds responsive ad creation and IAM tokens from a service account key
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
- Creates, edits and deletes campaigns, ad groups, ads and bids, spending ad budget
- Uploads offline conversions and costs to Metrica
- Read-only and confirm safety modes are off by default
Install
Manual install
git clone https://github.com/guyfullin10-lgtm/yandex-direct-mcp.git
cd yandex-direct-mcp
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txtAfter installing, copy .env.example to .env and fill in the tokens.
This is third-party code. Review the repository files before installing.
What it does
The server combines Yandex Direct, Metrica and Wordstat: 77 tools for Direct campaigns, ad groups, ads, keywords, bids, feeds and reports, 43 for Metrica counters, goals and reports, and 5 for Wordstat volumes and trends. The fork adds creating, editing and deleting responsive ads (ResponsiveAd) through a working Direct API v501 JSON endpoint that the official docs list incorrectly. It also adds IAM tokens from a service account key in place of Passport tokens, which Yandex stopped letting new apps exchange, plus retries for Wordstat on HTTP 429. The safety layer includes a read-only mode, a confirm mode that previews changes first, and a client login allowlist.
Who it is for. For PPC specialists who need responsive ads and compatibility with Yandex's newer authorization rules.
Good fit when
- You need to create ResponsiveAd ads, which the original project cannot upload
- A fresh OAuth token stopped working with Wordstat after Yandex's rule change in June 2026
- You need one server for Direct, Metrica and Wordstat with live-account safeguards
Not a fit when
- Single TextAd ads are enough and responsive ads are not needed
- You have no Yandex Cloud billing account, which Wordstat requires
Example request
Build a responsive ad with three headlines and two body texts for ad group 12345Limitations
A single-author fork on top of Yurich-ru/yandex-ads-mcp, developed in the fork-main branch with upstream master untouched. Requires an OAuth app with Direct, Metrica and cloud:auth access, an approved Direct API application, and a Yandex Cloud billing account with the search-api.executor role for Wordstat. A project license is not documented in the README.
How to disable. Remove the yandex-ads block from your MCP client config and revoke the OAuth token in Yandex ID settings.
MCP
- Transport
- stdio
- Authentication
- OAuth
| Environment variables | |
|---|---|
| YD_OAUTH_TOKEN required, secret | OAuth token with direct:api, metrika:read, metrika:write, cloud:auth scopes |
| YC_FOLDER_ID | Yandex Cloud folder ID, needed for Wordstat |
| YD_READONLY | true blocks all write tools |
| YD_CONFIRM | true requires confirm=true to execute write calls |
| YD_ALLOWED_LOGINS | Comma-separated allowlist of client logins |
Security check
- Creates, edits and deletes campaigns, ad groups, ads and bids, spending ad budget
- Uploads offline conversions and costs to Metrica
- Read-only and confirm safety modes are off by default
README in short
The README first lists what the fork adds over the original project, linking to FORK.md for a line-by-line changelog, then continues with the original project's docs: venv install, getting an OAuth token and Yandex Cloud folder ID, an environment variable table and a full list of 120 tools across three services. A separate section covers read-only and confirm modes and the offline test_safety.py check.
FAQ
How does this differ from Yurich-ru/yandex-ads-mcp?
Responsive ResponsiveAd ads, IAM tokens from a service account key, Wordstat retries, and tools renamed to yandex_direct_* instead of yd_* for better semantic search in MCP clients.
Why did Wordstat stop working with an older token?
Yandex stopped allowing the exchange of Passport tokens issued after June 1, 2026; the fork works around this with service account IAM tokens.
Related
A skill that strips AI writing tells from text using Wikipedia's list, without adding invented facts
Marketing Skills for AI agents
Marketing Skills for AI Agents
About fifty skills for CRO, copywriting, SEO, analytics, ads and launches, built for coding agents
SendPulse MCP server
SendPulse MCP
SendPulse's official remote MCP server: statistics, campaigns and user data through an agent chat
Yandex Direct MCP generated from a machine-readable schema
yandex-direct-mcp
An MCP server and CLI covering all 113 Yandex Direct API v5 methods generated from WSDL, exposing 9 read tools by default and writes only on demand