Other · Local MCP server
Yandex Direct
MCP server for Yandex Direct API v5 - campaigns, ads, keywords, bids, audiences.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.dontsovcmc/yandex-direct- Version
- 0.3.0
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-05-11
- Updated
- 2026-05-11
- Publisher
- dontsovcmc (GitHub) · 6 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/dontsovcmc) · how
- Repository
- github.com/dontsovcmc/mcp-server-yandex-direct
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | mcp-server-yandex-direct | 0.3.0 | stdio |
How to connect Yandex Direct
Yandex Direct runs locally from a Python package published to PyPI: mcp-server-yandex-direct version 0.3.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx mcp-server-yandex-direct. It reads these environment variables: YD_TOKEN (required, secret), YD_CLIENT_LOGIN, YD_LANG, YD_TIMEOUT and YD_FILE_TIMEOUT; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"yandex-direct": {
"command": "uvx",
"args": [
"mcp-server-yandex-direct"
],
"env": {
"YD_TOKEN": "<secret>",
"YD_CLIENT_LOGIN": "<value>",
"YD_LANG": "<value>",
"YD_TIMEOUT": "<value>",
"YD_FILE_TIMEOUT": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from dontsovcmc (GitHub)
| Server | Runs |
|---|---|
| CdekMCP server for CDEK delivery service API - create orders, track shipments, search delivery points. | Local · stdio |
| Ozon SellerMCP server for Ozon Seller API - products, FBS/FBO, finance, analytics, returns. | Local · stdio |
| WildberriesMCP server for Wildberries Seller API - products, orders, supplies, analytics, advertising. | Local · stdio |
| Yandex Market SellerMCP server for Yandex Market Partner API - orders, offers, prices, stocks, analytics. | Local · stdio |
| Yandex MetrikaMCP server for Yandex Metrika API - counters, goals, reports, segments, logs. | Local · stdio |
More other servers
| Server | Runs |
|---|---|
| YahooslurpValidate Yahoo. Slurp IP addresses. Remote MCP validate_ip tool. | Remote · HTTPLive check: ✓ handshake |
| Yaml MCPParse, stringify, and validate YAML locally. No network and no key. | Local · stdio |
| YAML WorkflowExpose declarative YAML-defined workflows as MCP tools over stdio. | Local · stdio |
| Yandex Delivery MCPMCP server for the Yandex Delivery B2B API: express claims, tracking, NDD/pickup-point orders. | Local · stdio |
| Yandex Direct MCPMCP server for Yandex Direct API: campaigns, ads, keywords, bids, reports. Click.ru or OAuth. | Local · stdio |
| Yandex Merchants MCPMCP server for the Yandex Merchants partner API: feeds, offer prices, discounts, hide/unhide. | Local · stdio |
| Yandex Metrika MCPRead-only Yandex Metrika MCP. Query visits, sources, geo, devices and more in plain language. | Remote · HTTPLive check: ✗ no handshake |
| Yandex Webmaster MCPQuery Yandex Webmaster indexing, queries, diagnostics and backlinks, and recrawl, via an AI agent. | Local · stdio |