Read-only Yandex Direct MCP server
yandex-direct-mcp-server
A single-file, read-only MCP server for the Yandex Direct API, with a /healthz config check
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- Per its own code description, the server reads Direct data and performs no write requests
Install
Manual install
node server.jsThe DIRECT_OAUTH_TOKEN and optional DIRECT_CLIENT_LOGIN environment variables must be set before running.
This is third-party code. Review the repository files before installing.
What it does
The Node.js server is deliberately kept in a single server.js file so it is easier to edit right in the GitHub web UI. Per the author's own comment, the architecture mirrors their yandex-metrika-mcp-server: Express with streamable HTTP transport, a secret in the URL path, and a /healthz endpoint that always returns 200 and lists config problems. The server only reads Direct data, tracks the API's Units quota from the response header, and can poll offline report readiness within a time budget.
Who it is for. For marketers who want safe, read-only agent access to Yandex Direct campaign structure and stats.
Good fit when
- You want to view Direct campaigns, ads and reports without any risk of changing them
- You want a simple single-file server that is easy to read and tweak
Not a fit when
- You need to manage bids or pause and create campaigns: the server is read-only
- You need proper documentation: there is no README, and Russian code comments only partly substitute for one
Example request
Show Yandex Direct campaign stats for last weekLimitations
The repository has no README. The project is maintained by one author, with no stars. It needs a Yandex Direct OAuth token, plus a client login for agency accounts.
How to disable. Stop the server process and remove it from your MCP client config.
MCP
- Transport
- http, stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| DIRECT_OAUTH_TOKEN required, secret | Yandex Direct OAuth token |
| DIRECT_CLIENT_LOGIN | Client login, needed if the token was issued for an agency account |
Security check
- Per its own code description, the server reads Direct data and performs no write requests
README in short
The repository has no README. All the explanation is in Russian comments at the top of server.js: the server's purpose, the reason for the single-file structure, a reference to the sibling yandex-metrika-mcp-server architecture, and the DIRECT_API_BASE_URL, DIRECT_API_VERSION, DIRECT_OAUTH_TOKEN and DIRECT_CLIENT_LOGIN environment variables.
FAQ
Can the server change bids or pause campaigns?
No, the comment at the top of server.js explicitly states the server is read-only.
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