Bun-based Yandex Direct MCP with Unified Performance and Click.ru proxy
Yandex Direct MCP
A Bun-based Direct API v5 MCP server with 50 tools, Unified Performance support, and connection via your own token or a Click.ru proxy with no OAuth
- 0 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- Creates and changes campaigns, including Unified Performance ones, with a real budget
- Forecasts and changes bids, which directly affects spend
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/alexf81xxx-yandex-direct-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Creates and changes campaigns, including Unified Performance ones, with a real budget
- Forecasts and changes bids, which directly affects spend
This is third-party code. Review the repository files before installing.
What it does
This Bun and TypeScript server gives 50 Direct API v5 tools: campaigns including Unified Performance Campaigns with bid strategies and Metrica goals, ad groups, text and combinatorial ads, extensions like sitelinks and callouts, images, bids and click-price forecasting, bid adjustments, keywords, reports and dictionaries. There are two connection modes: direct with your own Yandex Direct OAuth token, or through a Click.ru proxy, using a click.ru profile API token and the login of an account already connected there instead of a Yandex token. It defaults to API version v501, required for Unified Performance. There is an HTTP mode requiring MCP_AUTH_TOKEN, and releases are authorized through a trusted GitHub OIDC publisher with no long-lived secrets.
Who it is for. For people running Unified Performance Campaigns in Direct, or already working through Click.ru, who want to manage ads without getting a separate Yandex OAuth token.
Good fit when
- You need to work with a Unified Performance Campaign, not just a text one
- You already have a Click.ru account and do not want to register a separate Yandex OAuth app
- You need HTTP mode with your own auth token for remote access
Not a fit when
- You have neither your own OAuth token nor a Click.ru account: neither connection mode can be set up without one
- You need a sandbox together with the Click.ru proxy: it only works with production API
- You need guarantees around known sandbox limitations: some operations there are simply unverifiable
Example request
Create a Unified Performance Campaign with a Metrica goal and show the click-price forecast for the keywordsMCP
- Transport
- stdio, http
- Authentication
- key is optional
Environment variables
YANDEX_DIRECT_TOKENsecret- Yandex Direct OAuth token for direct mode
CLICK_RU_PROXY- true enables the Click.ru proxy mode instead of a direct token
CLICK_RU_TOKENsecret- API token from the click.ru profile
MCP_AUTH_TOKENsecret- Required in HTTP mode to authorize clients
Limitations
The Click.ru proxy only works with the production API; sandbox is unavailable through it. Yandex's own sandbox has confirmed limitations: uploading ads into a group is unverifiable, bidmodifiers.get always returns empty, and the sitelinks service is sometimes unavailable. These are documented and explicitly marked as skipped, not failed, in the e2e tests. HTTP mode requires MCP_AUTH_TOKEN.
How to disable. Remove the yandex-direct block from your project's .mcp.json or stop the server process.
FAQ
Do I need a Yandex token if I go through Click.ru?
No, in CLICK_RU_PROXY=true mode a click.ru profile API token and the login of a Direct account already connected there replace the Yandex token.
Does the sandbox work through the Click.ru proxy?
No, the proxy only works with Yandex's production API; sandbox is unavailable through it.
Discussion
No questions or reviews yet.
Related
All Yandex Direct toolsYandex 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
Dependency-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: 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
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
Python MCP for Yandex Direct and Wordstat
Yandex.Direct MCP
A Python MCP server with 48 Yandex Direct tools and Wordstat frequency lookup, switchable between sandbox and production
Yandex Direct MCP
yandex-direct-mcp
A Claude Code and Codex plugin for Yandex Direct: a 147-tool MCP server, OAuth, and skills for ad copy and stats analysis
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Bun-based Yandex Direct MCP with Unified Performance and Click.ru proxy (this card) | no | key is optional | 0 | |
| Yandex Direct MCP server (npm) | no | API key | 4 | 20 tools, money in rubles |
| Yandex Direct MCP with launch policies | no | API key | 2 | policies |
| Yandex Direct MCP with dry-run by default | no | API key | 0 | 20 tools, edits with dry-run by default |
README in short
The README gives two independent setup blocks: direct mode with YANDEX_DIRECT_TOKEN and Click.ru mode with its own variables, run commands for stdio and HTTP modes, a section on network-free mock tests and HTTP transport, and an honest list of known Yandex sandbox limitations reproduced in the e2e tests. It separately describes the release process: versions are checked in three places, and npm and MCP registry publishing goes through a trusted GitHub OIDC publisher.