Yandex Direct MCP server: scoped Yandex Direct access for every agent

Advertising review begins with account identity, campaign IDs and a date range. Ask for observed spend, campaign status and report parameters before proposing changes. A performance summary is not authorization to increase bids or create ads.

Agency tasks can specify Client-Login where the provider method supports it; agencyclients methods are an exception. The agent should show the advertiser context rather than assuming one OAuth session means one advertiser. Provider permissions and approval remain the outer access boundary.

This adapter uses production API v501 and sandbox v5. Keep testing and live advertising separately identified. A validated sandbox request can teach the request format, but it does not make the same mutation appropriate for a live campaign.

Yandex Direct MCP server options

The official Direct API documentation governs authentication, account context and method limits. askads/mcp-yandex-direct and yandex-mcp are separate community options. This page does not claim Yandex publishes an official MCP server.

A fixed reporting script can be simpler than an agent gateway. AIPx adds credential handling and request processing in exchange for flexible agent access alongside other sources, but it does not remove API approval or advertising account restrictions.

Connect Yandex Direct to Claude, Claude Code, Cursor or Codex

Authorize Yandex Direct with the direct:api scope. Advertiser API access approval is required separately; agency requests need the appropriate Client-Login context.

1. Open the AIPx dashboard, choose Yandex Direct under Integrations and complete its connection form or authorization.
2. Create an MCP agent, enable that connection and choose the tools this particular agent needs. Save the rules before opening your AI client.
3. Copy the agent’s complete URL. The examples below use AGENT_ID; replace it with the actual value from your dashboard.

An endpoint identifies the AIPx agent, not a provider API key. Client authentication to AIPx is separate from connecting Yandex Direct; adding the URL does not grant extra provider permissions. Our MCP gateway guide explains how several approved connections can share that endpoint.

Connect Claude to Yandex Direct

In Claude, open Customize → Connectors and add a custom connector with your AIPx URL. Continue through AIPx sign-in, then check the tools available in a conversation. Custom connector access depends on account and workspace policy; administrators can restrict it. The Claude MCP setup guide covers the current controls. A direct vendor connection can be simpler when Yandex Direct is the only service you need.

Yandex Direct MCP in Claude Code

claude mcp add --transport http aipx https://dash.aipx.run/mcp/AGENT_ID

Use /mcp to authorize, then read campaign IDs for the intended advertiser before requesting a report. Keep bid-setting hidden for analysis. Claude Code MCP setup explains registration and login.

Yandex Direct MCP in Cursor

Add this server to .cursor/mcp.json for the project or ~/.cursor/mcp.json for your user:

{
  "mcpServers": {
    "aipx": { "url": "https://dash.aipx.run/mcp/AGENT_ID" }
  }
}

After Cursor sign-in, confirm advertiser context and Client-Login where required. Read campaign state before drafting a mutation. See Cursor MCP setup for server configuration and approval controls.

Yandex Direct MCP in Codex

codex mcp add aipx --url https://dash.aipx.run/mcp/AGENT_ID
codex mcp login aipx
codex mcp list

Codex uses the HTTP endpoint and browser OAuth; it does not need a copy of the Yandex Direct credential in its config. See Codex MCP setup for TOML configuration and project trust requirements.

ChatGPT custom MCP can use the Direct agent when workspace and account access allow it. Reporting does not authorize spending changes. The ChatGPT MCP guide explains current connector and administrator requirements.

Scope advertising reads and spending changes

A reporting agent can have campaign, ad, group and bid reads plus report generation on Allow. Hide campaign creation, updates, ad mutations and bid-setting operations. A separate operator may use selected mutations on Confirm, with target advertiser, IDs and proposed values shown for client approval.

Reports are read tools despite their POST transport. Conversely, a mutation cannot become safe merely because a task calls it optimization. Confirm relies on client behavior; Hide is the restriction for an agent that must never alter advertising. See MCP access control.

Use Google Sheets for a reviewed report and Notion for the approved campaign brief. X is a separate publishing connection, while Exa can help research primary sources without changing campaigns.

Direct API units, reports and advertiser limits

API units and provider limits still apply, including report processing behavior. Keep report parameters explicit and distinguish a requested report from returned data. A failed or pending response should be shown as such rather than filled with guessed performance numbers.

Agency account context deserves special care because the same session may authorize several advertisers. AIPx tool modes do not create an arbitrary advertiser-level filter inside every operation. Use correct provider access and inspect Client-Login support for the selected method.

Browse all MCP integrations to choose another connection for this agent.

The Yandex Direct connection can use AIPx Free with 3 active accounts and 1 agent; check AIPx pricing for gateway plans and keep provider or client charges separate.