Yandex Direct MCP, CLI and models with action search
mcp-server-yandex-direct
A Yandex Direct API v5 MCP server, CLI tool and Pydantic models: 79 actions through two tools instead of 79 separate ones
- 1 ★ on the repository
- Last commit
Broad access
Why this level
- The 79 actions cover creating, changing and archiving campaigns, ads and keywords
- Runs against the live account; no built-in dry-run is described in the README
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/mcp-server-yandex-directDetects 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.
- The 79 actions cover creating, changing and archiving campaigns, ads and keywords
- Runs against the live account; no built-in dry-run is described in the README
This is third-party code. Review the repository files before installing.
What it does
The project gives three ways to work with the Direct API v5 on top of one typed Pydantic model library: an MCP server for Claude Code and other clients, a CLI tool for the terminal and scripts, and the model library itself for custom Python programs. Instead of 79 separate tools, one per action, the server uses a search-plus-execute pattern: yd_search finds the right action by natural-language description and returns its parameter schema, and yd_execute runs it by id. The 79 actions are grouped into 16 domains: campaigns, ad groups, ads, keywords, bids, audiences, feeds, creatives, leads, change tracking, account, turbo pages and reports. All data stays on the user's machine, and the token goes nowhere except the Yandex API.
Who it is for. For developers who want an MCP server for an agent, a CLI for scripts and typed API v5 models for their own Python code, all in one package.
Good fit when
- You need both an agent MCP server and a plain CLI for automation without a model
- You need typed Pydantic models of the Direct API for your own Python scripts
- The model gets confused by dozens of tools: searching for an action by description beats holding all 79 in context
Not a fit when
- You want separate named tools per action rather than description-based search
- You do not write Python and have no use for the model library
- You need a built-in dry-run guard: the README does not describe one
Example request
Find the action to suspend campaigns and suspend campaign 12345MCP
- Transport
- stdio
- Authentication
- API key
Environment variables
YD_TOKENrequired, secret- Yandex Direct OAuth token
Limitations
Needs your own OAuth token from the Settings, API section of the Direct dashboard. The search-plus-execute pattern needs the model to find the action first and call it second: two steps instead of one direct tool. The repository's license is not explicitly set at the GitHub API level.
How to disable. Run claude mcp remove yandex-direct in Claude Code or remove the yandex-direct block from your client config.
FAQ
How does the model find the right action among 79?
The yd_search tool takes a natural-language task description, e.g. 'suspend campaigns,' and returns matching actions with a parameter schema for yd_execute.
Can it be used without MCP, just from the terminal?
Yes, the package includes a separate CLI utility for the same 79 actions and a Pydantic model library for your own Python code.
Discussion
No questions or reviews yet.
Related
All Yandex Direct toolsYandex 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
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 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 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
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
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
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Yandex Direct MCP, CLI and models with action search (this card) | no | API key | 1 | |
| Direct, Metrika, Wordstat and Webmaster MCP server | no | API key | 0 | Metrika, Webmaster |
| yandex-direct-mcp | no | API key | 0 | campaigns, reports |
README in short
The README describes the search-plus-execute architecture with an example search-and-run dialogue, a table of 16 domains with action counts and links to detailed docs, and three separate install sections: MCP server, CLI tool and model library, each with its own examples. It separately stresses that all data stays local and the token goes nowhere else.