DirectAI MCP: a local server for Yandex Direct
DirectAI MCP
A local Windows MCP server that works with Yandex Direct through the official API: 57 read actions and 25 write actions with a mandatory preview
- 0 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The agent can change bids, budgets, the schedule and ads in a live account, which means spending ad money
- The Direct token opens account data, though every write requires confirmation
Install
- Works in
- Services
Manual install
uv tool install --editable . && directai-mcp initRun in the folder of the cloned repository on Windows 11, then `directai-mcp set-token --login <login>`.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent can change bids, budgets, the schedule and ads in a live account, which means spending ad money
- The Direct token opens account data, though every write requires confirmation
This is third-party code. Review the repository files before installing.
What it does
The server runs on your computer for a single user and exposes nothing to the internet. It reads impressions, clicks, spend and conversions across accounts, campaigns, groups, ads, phrases, queries, regions and devices, compares periods and builds reports. Yandex Metrika, Wordstat, retargeting and audiences can be connected, and a campaign audit returns an improvement plan. Writing covers campaigns, groups, ads, phrases, bids, adjustments, negative phrases, goals, the daily budget and the display schedule. Any edit goes through `plan_write` with a "was, will be" preview, then your confirmation and `apply_write`, so there are no direct changes. The token lives in the Windows Credential Manager, changes are written to `journal.sqlite`, and manual edits in the cabinet show up through `changes_check`.
Who it is for. PPC specialists and ad account owners on Windows who want to hand audits and routine campaign edits to an agent under control.
Good fit when
- You need spend, clicks and conversions across all accounts compared with the previous week
- An agent is asked to review a campaign: what changed over the month, where the losses are and what to improve
- The display schedule changes point by point, for example only Saturday from 12 to 13
- Direct spend must be tied to Metrika leads and CPA calculated
Not a fit when
- macOS and Linux: the author did not test them, the server targets Windows 11 and PowerShell
- There is no approved Direct API access request: without it the server cannot reach the account
- You need a shared server for a team: this one works for one user on one computer
Example request
Show spend, clicks and conversions across all accounts for the last 7 days and compare with the previous weekMCP
- Transport
- stdio
- Authentication
- OAuth
Environment variables
DIRECT_TOKENsecret- Direct OAuth token, stored in the Windows Credential Manager by default
Limitations
Windows 11 and PowerShell are supported, and macOS and Linux were not tested. It needs an approved Direct API access request, which takes up to several days, an app at oauth.yandex.ru and installed Git and uv. Tokens for Metrika, Webmaster and Wordstat are issued separately. A guard layer block means protection and must not be bypassed. The server is free, MIT license, the last commit in November 2026, no stars.
How to disable. Remove the `directai-mcp` entry from MCP client settings, run `uv tool uninstall directai-mcp` and delete the token from the Windows Credential Manager.
FAQ
How do edits reach the account?
Through `plan_write` with a "was, will be" preview, then your explicit consent and `apply_write`. There are no direct changes without a plan.
Where is the token stored?
In the Windows Credential Manager or an environment variable. It never reaches logs or URLs and must not be typed into chat.
What do `check` and `probe` verify?
`check` calls the Direct API and shows `OK` for each account. `probe` checks MCP locally without touching the advertising API and spends no points.
Which clients does the server work with?
With OpenCode, Codex, Claude Code, Claude Desktop and Hermes: the `directai-mcp` command runs over stdio everywhere. Configs are in `examples/harness-configs.md`.
How many actions are available?
57 read actions and 25 write actions, the full list is in `docs/actions.md`. Writing retargeting and audiences is off by default.
Discussion
No questions or reviews yet.
Related
All Yandex Direct toolsA ZAI.ONE MCP server bringing Direct, Metrika, search, Wordstat and Webmaster into one agent, with a setup wizard and opt-in write operations
Yandex Metrika + Direct MCP Server
Яндекс.Метрика + Директ MCP Server
A 30-tool MCP server for Metrika and Direct: reports, bids, ads, negative keyword management and Wordstat
An MCP server for Yandex Direct, Metrika, Wordstat and Webmaster: campaigns, ads, bids, reports and keyword research from chat
An MCP server for Yandex Direct, Metrica, Wordstat and Audience analytics: raw reports, data joins and an HTML dashboard
Monorepo of Yandex MCP servers: Direct, Metrica, Webmaster, Wordstat, Tracker, 360, Maps, SpeechKit, YandexGPT and AppMetrica
A 155-tool MCP server for Yandex Direct, Metrika, Wordstat and Webmaster, with self-setup OAuth and read-only and confirm modes
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| DirectAI MCP: a local server for Yandex Direct (this card) | no | OAuth | 0 | |
| Yandex Direct MCP server in Ruby | no | API key | 6 | writes go only through a plan with a preview and an edit journal, plus Metrika and Wordstat |
| Yandex Direct MCP | no | not required | 14 | a separate local Windows server with an edit journal and a manual change check |
README in short
The README covers capabilities, a quick start with installation, accounts and a token, checks, connecting to agents, example requests, the safety layer and the documentation index.