Yandex Direct For All plugin
A Codex and Claude Code plugin with skills and MCP for Yandex Direct, Metrika, Wordstat v2, Roistat, amoCRM and Yandex Search API
- 21 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Can change ad campaigns with budget after approval
- Stores OAuth tokens for Direct, Metrika and amoCRM
- Paid Search API requests cost money
Install
- Works in
- Services
Manual install
bash plugins/yandex-direct-for-all/scripts/install_bundle.sh --target both
bash plugins/yandex-direct-for-all/scripts/install_bundle.sh --target both --applyRun from a repository clone. The first command only shows the plan, the second applies it. Target can be codex, claude or both.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Can change ad campaigns with budget after approval
- Stores OAuth tokens for Direct, Metrika and amoCRM
- Paid Search API requests cost money
This is third-party code. Review the repository files before installing.
What it does
The bundle combines a single entry skill, yandex-direct-unified, skills for Wordstat, Roistat and amoCRM, and services for Direct, search and Wordstat. It ships shared Direct and Metrika authorization apps, so users do not need their own OAuth app. Reads are separated from writes: campaign changes need explicit permission, an exact change package, a snapshot before and a read after. Wordstat request limits are tracked across processes, and the paid Search API is off by default. Scripts collect Direct, Metrika, Roistat, SERP and Wordstat data for reports.
Who it is for. For PPC specialists and marketers running campaigns in Yandex Direct.
Good fit when
- You need to review Direct campaigns read-only and prepare a proposal package
- You need keyword research via Wordstat v2 with quota control
- You need to reconcile Roistat and amoCRM leads with ad sources
Not a fit when
- You need a simple report from one service and a multi-component bundle is overkill
- The agent must not get access to an ad account with budget
Example request
Review my Direct campaigns without writing anything and prepare a package of negative keyword proposalsLimitations
Installation is a script run from a repository clone, with no marketplace listing. Wordstat v2 goes through Yandex Cloud and needs an api_key and folder_id, and Search API is paid. Roistat and amoCRM need their own keys and integrations. Docs and skills are Russian only.
How to disable. When run with --apply the installer prints a RUN_ID and an exact rollback command that restores the agent directories.
FAQ
Do I need my own Yandex app?
Not for Direct and Metrika, the bundle includes shared authorization apps. The token is verified by a read after exchange.
What happens on reinstall?
Only untouched managed directories are updated. If you edited files, the installer stops before writing.
Discussion
No questions or reviews yet.
Related
All Yandex Direct toolsYandex 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
Five MCP servers for Yandex Search, Wordstat, Webmaster, Metrika and Direct, bundled as a Claude Code plugin with two skills
A ZAI.ONE MCP server bringing Direct, Metrika, search, Wordstat and Webmaster into one agent, with a setup wizard and opt-in write operations
Yandex Direct full-cycle skill
yandex.direct
A skill for running Direct: Wordstat demand research, Unified Performance Campaigns, combinatorial ads, moderation, Metrika and safe dry-run API payloads
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
README in short
The README briefly lists the bundle contents and principles: a single entry skill, shared auth apps, reads separated from writes and the paid search off by default. Installation is install_bundle.sh with a plan preview, then --apply for Codex, Claude or both. The first run covers release_gate.sh, authorization and a protected Wordstat key file. Details are in QUICKSTART.md and docs. MIT license.