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
- 0 ★ on the repository
- Last commit
Extended access
Why this level
- Runs a Node.js server that reads Yandex Direct campaigns and reports with an OAuth token
- In HTTP mode the secret is passed in the URL path, so keep the address private
clientssukach-lang/yandex-direct-mcp-server
A similar tool with a larger community: Yandex Direct MCP server in Ruby, 6 ★ on the repository
Install
- Works in
- Services
Manual install
node server.jsThe DIRECT_OAUTH_TOKEN and optional DIRECT_CLIENT_LOGIN environment variables must be set before running.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Runs a Node.js server that reads Yandex Direct campaigns and reports with an OAuth token
- In HTTP mode the secret is passed in the URL path, so keep the address private
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 weekMCP
- Transport
- http, stdio
- Authentication
- API key
Environment variables
DIRECT_OAUTH_TOKENrequired, secret- Yandex Direct OAuth token
DIRECT_CLIENT_LOGIN- Client login, needed if the token was issued for an agency account
Limitations
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.
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.
Discussion
No questions or reviews yet.
Related
All Yandex Direct toolsDependency-free Node MCP for Yandex Direct
yandex-direct-mcp
A single-file, dependency-free Node.js Direct API v5 MCP server with a universal direct_call tool and a read-only mode
Yandex Direct MCP server (npm)
@theyahia/yandex-direct-mcp
A TypeScript MCP server with an npm package: 20 tools for Yandex Direct campaigns, bids and negative keywords, with money always in rubles
Yandex Direct MCP server in Ruby
yandex-direct-mcp
A dependency-free, pure Ruby MCP server with 30 tools for Yandex Direct campaigns, ad groups, ads, keywords and reports
A 155-tool MCP server for Yandex Direct, Metrika, Wordstat and Webmaster, with self-setup OAuth and read-only and confirm modes
Yandex Direct MCP with dry-run by default
Yandex Direct MCP Server
20 Yandex Direct tools where every edit shows the plan by default and needs confirm=True to actually send anything
Yandex Direct MCP: hardened fork
yandex-direct-mcp
A fork of a popular Yandex Direct MCP server that defaults to read-only, with explicit flags for writes and finance
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.