Яндекс Директ API v5 runs on your own machine — the client starts it, so there is no endpoint to ping. 64 installs a week from npm. Last commit 10 Sep 2026.
MCP server for Yandex Direct API v5: 113 methods from the machine-readable schema
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const out = execFileSync(process.execPath, [join(root, 'tools/measure-surface.mjs')], {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add yandex-direct-api-mcp -e 'YANDEX_DIRECT_TOKEN=<YANDEX_DIRECT_TOKEN>' -- npx -y yandex-direct-api-mcp
{
"mcpServers": {
"yandex-direct-api-mcp": {
"command": "npx",
"args": [
"-y",
"yandex-direct-api-mcp"
],
"env": {
"YANDEX_DIRECT_TOKEN": "<YANDEX_DIRECT_TOKEN>"
}
}
}
}
[mcp_servers.yandex-direct-api-mcp]
command = "npx"
args = ["-y", "yandex-direct-api-mcp"]
env = { YANDEX_DIRECT_TOKEN = "<YANDEX_DIRECT_TOKEN>" }
{
"mcpServers": {
"yandex-direct-api-mcp": {
"command": "npx",
"args": [
"-y",
"yandex-direct-api-mcp"
],
"env": {
"YANDEX_DIRECT_TOKEN": "<YANDEX_DIRECT_TOKEN>"
}
}
}
}
{
"servers": {
"yandex-direct-api-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"yandex-direct-api-mcp"
],
"env": {
"YANDEX_DIRECT_TOKEN": "<YANDEX_DIRECT_TOKEN>"
}
}
}
}
Put your own value in place of
<YANDEX_DIRECT_TOKEN> (OAuth-токен Яндекса со scope direct:api (https://oauth.yandex.ru/)).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
YANDEX_DIRECT_LOGIN (Логин кабинета для заголовка Client-Login. Нужен агентствам и представителям; для собственного кабинета не задаётся), DIRECT_PROFILE (Набор объявляемых инструментов: core — узкий набор по умолчанию, read — все читающие, all — вся поверхность), DIRECT_TOOLS (Явный список инструментов или служб через запятую. Побеждает DIRECT_PROFILE), DIRECT_ALLOW_WRITES (Разрешить изменяющие методы (add/update/delete). Пока выключено, они не объявляются вовсе. Значения: 1, true, yes), DIRECT_API_VERSION (Версия пути API. Разные версии отдают разные наборы полей одной и той же кампании), DIRECT_SANDBOX (Отправлять запросы в песочницу Директа вместо боевого кабинета. Значения: 1, true, yes), DIRECT_MAX_OUTPUT_CHARS (Потолок размера ответа инструмента в символах; сверх него ответ усекается с пометкой).
MCP server for Yandex Direct API v5 — campaigns, ads, keywords, reports
MCP server for the Rise of Machine AI tools directory.
MCP server for Yandex Direct API v5 — campaigns, ads, keywords, bids, audiences
MCP server for Yandex.Metrica Stat API (read-only).
MCP server for Yandex Direct API v5: manage PPC campaigns, ads, keywords, and statistics.
MCP server for Yandex Direct API v5: manage PPC campaigns, ads, keywords, and statistics.
MCP server for Yandex Tracker API.
MCP server for Yandex Tracker API.
Answers built from our own checks of this server.