Other · Local MCP server
Yandex Direct MCP
MCP server for Yandex Direct API: campaigns, ads, keywords, bids, reports. Click.ru or OAuth.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.ai-hub-open/yandex-direct-mcp- Version
- 0.5.0
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-30
- Updated
- 2026-07-30
- Publisher
- ai-hub-open (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/ai-hub-open) · how
- Repository
- github.com/ai-hub-open/yandex-direct-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: bunx | @ai-hub-open/yandex-direct-mcp | 0.5.0 | stdio |
How to connect Yandex Direct MCP
Yandex Direct MCP runs locally from a Node.js package published to the npm registry: @ai-hub-open/yandex-direct-mcp version 0.5.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 Node.js; clients usually start it with npx - the usual command is npx -y @ai-hub-open/yandex-direct-mcp@0.5.0; the entry names bunx as the runtime. It reads these environment variables: CLICK_RU_PROXY, CLICK_RU_TOKEN (secret), CLICK_RU_CLIENT_LOGIN, YANDEX_DIRECT_TOKEN (secret) and YANDEX_DIRECT_SANDBOX; 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-mcp": {
"command": "npx",
"args": [
"-y",
"@ai-hub-open/yandex-direct-mcp@0.5.0"
],
"env": {
"CLICK_RU_PROXY": "<value>",
"CLICK_RU_TOKEN": "<secret>",
"CLICK_RU_CLIENT_LOGIN": "<value>",
"YANDEX_DIRECT_TOKEN": "<secret>",
"YANDEX_DIRECT_SANDBOX": "<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 ai-hub-open (GitHub)
| Server | Runs |
|---|---|
| Vk Ads MCPMCP server for VK Ads API: campaigns, audiences, budgets, stats. Click.ru, token or OAuth. | Local · stdio |
More other servers
| Server | Runs |
|---|---|
| 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 DirectMCP server for Yandex Direct API v5 - campaigns, ads, keywords, bids, audiences. | 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 |
| Yandex Wordstat MCPMCP server for Yandex Wordstat API: top & related queries, demand dynamics and regions. | Local · stdio |