MCP Tools Directory
← Browse integrations

Developer tools

yandex-direct-mcp

Free account · sign-in required

Contact yandex-direct-mcp

Loading secure sign-in…

Tools for autonomous AI agents

About this integration

MCP server for Yandex Direct — PPC campaigns, ads, keywords, statistics (Russia)

Transport
stdio
Authentication
oauth
Initial setup
user-authorization
Runtime
unattended
Evidence
documented
Version
3.0.2
Package
@theyahia/yandex-direct-mcp
Last compatibility test
Not independently tested

Connect your agent

@theyahia/yandex-direct-mcp

Publisher documentation and the package manifest were reviewed; neither the package nor Yandex Direct was executed. Documented write operations can change campaigns and spend money, so provider-side scopes and sandbox use remain operator responsibilities.

Capabilities: Manage advertising campaigns, groups, and ads, Manage keywords, bids, and negative keywords, Retrieve advertising statistics and account balance, Use a sandbox or agency client login

Connected profiles

Additional details

Registry identifier

io.github.theYahia/yandex-direct-mcp

Source ↗ · Checked 2026-09-17
Published version

3.0.2

Source ↗ · Checked 2026-09-17
Metadata license

CC0-1.0; package licenses are separate

Source ↗ · Checked 2026-09-17
Package ecosystem

npm

Source ↗ · Checked 2026-09-17
Source artifact

@theyahia/yandex-direct-mcp

Source ↗ · Checked 2026-09-20
Source manifest version

4.0.1

Source ↗ · Checked 2026-09-20
Unattended configuration

The publisher documents a client-launched npx MCP process configured with a Yandex Direct OAuth token.

Source ↗ · Checked 2026-09-20
Authentication and prerequisites

A Yandex OAuth token is issued for a registered application with Direct API access and supplied through YANDEX_DIRECT_TOKEN; agency tokens may also require YANDEX_DIRECT_LOGIN.

Source ↗ · Checked 2026-09-20
Connection configuration

The reviewed connection invokes npx -y @theyahia/yandex-direct-mcp as a local MCP subprocess with YANDEX_DIRECT_TOKEN.

Source ↗ · Checked 2026-09-20
Review scope

Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.

Source ↗ · Checked 2026-09-20