yandex-direct-metrica-mcp
An MCP server for Yandex Direct, Metrica, Wordstat and Audience analytics: raw reports, data joins and an HTML dashboard
- 9 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- Uses ad account OAuth tokens
- The public build only reads data but exports it to local files
Install
- Works in
- Services
Manual install
python3 scripts/setup.pyInteractive wizard inside a repository clone.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Uses ad account OAuth tokens
- The public build only reads data but exports it to local files
This is third-party code. Review the repository files before installing.
What it does
The server gives an agent two tool layers. Low-level calls return near-raw data from the Direct, Metrica, Wordstat, Audience and Search APIs. High-level tools help with common reports, join Direct spend with Metrica visits via UTM and yclid, suggest keywords and build a self-contained HTML and JSON dashboard, including across several accounts. The public build is read-only and does not change campaigns, goals or segments.
Who it is for. For marketers, analysts and agencies who need reports across several Yandex ad accounts through an agent.
Good fit when
- You need a spend and conversion dashboard across all accounts for a month
- You need to link Direct spend to Metrica visits and goals
- You need raw data for your own analysis without risking campaign changes
Not a fit when
- You need to create or edit campaigns: the public version is read-only
- You have no Docker and do not want to build an image
Example request
Generate a dashboard for all accounts for the last 30 days up to yesterday and give me the HTML pathMCP
- Transport
- stdio
- Authentication
- OAuth
Environment variables
YANDEX_ACCESS_TOKENrequired, secret- Direct and Metrica OAuth token, or YANDEX_REFRESH_TOKEN
MCP_ACCOUNTS_FILE- Path to accounts.json listing accounts
MCP_CONTENT_MODE- json for raw data analysis
Limitations
Requires Direct and Metrica OAuth tokens, plus separate credentials for Audience and Wordstat. The main way to run it is Docker with a state folder and accounts.json. BI data sync is in a paid private plugin. Today's data is usually incomplete, so the author suggests ending periods yesterday.
How to disable. Remove the server with claude mcp remove yandex-direct-metrica-mcp and delete the state folder with .env.
FAQ
What does read-only mean?
The server does not create, change or delete campaigns, goals or segments. Wordstat report requests and Metrica Logs API exports are still allowed.
Can I manage several clients?
Yes, list accounts in accounts.json with Direct login and Metrica counters, and the dashboard covers all of them.
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 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
Yandex Metrika + Direct MCP Server
Яндекс.Метрика + Директ MCP Server
A 30-tool MCP server for Metrika and Direct: reports, bids, ads, negative keyword management and Wordstat
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
An MCP server for Yandex Direct, Metrica, Audiences and Wordstat with read-only mode and change confirmation
README in short
The README offers a setup wizard for Claude Code, Claude Desktop, Cursor, Codex CLI, OpenCode and Gemini CLI plus a manual Docker path using a GHCR image. It explains what read-only mode allows, describes two tool layers and a paid BI plugin. Environment variables are listed, and Russian docs are on the project site. Apache 2.0 licensed.