SkillFoxx

Yandex Direct MCP as a Claude HTTP connector

ya-direct-mcp

A Streamable HTTP Yandex Direct MCP server, deployed on Railway and connected to Claude as a custom connector via a secret URL

  • 0 ★ on the repository
  • Last commit
MCP server

Broad access

Why this level

  • Leaking MCP_SECRET grants full account access, including irreversible campaign deletion
  • Creates, suspends and archives campaigns, groups, ads and keywords
All reasons and checks
Russian stack

dmburov/ya-direct-mcpAuthor:dmburov

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/ya-direct-mcp

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Leaking MCP_SECRET grants full account access, including irreversible campaign deletion
  • Creates, suspends and archives campaigns, groups, ads and keywords

This is third-party code. Review the repository files before installing.

What it does

Unlike most Direct servers that run locally over stdio, this one deploys as a cloud HTTP endpoint and connects to Claude via Settings, Connectors, Add custom connector, with no local install and no .mcp.json. It manages text campaigns: list, fetch, create, update, suspend, resume, archive and delete for campaigns, ad groups, ads and keywords, plus a report and account balance. Every tool accepts an optional client_login, so one deployed server can serve several advertisers at once. Client authorization runs through its own MCP_SECRET, baked into the URL path or passed as a header, while the Direct OAuth token lives only in the server's Railway environment and Claude never sees it.

Who it is for. For people who want to connect Yandex Direct to Claude as a cloud connector with no local install, and are willing to deploy their own server on Railway.

Good fit when

  • You need a Direct MCP server reachable from Claude with no local process on your machine
  • You need to serve several advertisers from one deployed server via client_login
  • You already have, or do not mind creating, a Railway account for a quick deploy

Not a fit when

  • You do not want an endpoint exposed to the internet: the only protection is the MCP_SECRET in the path or header
  • You need a local stdio install with no cloud hosting
  • You need accidental-delete protection on every method: only delete_campaign has a safety catch

Example request

Show account balance and suspend campaigns that spent over 5,000 rubles this week with no conversions

MCP

Transport
http
Authentication
API key

Environment variables

YD_TOKEN required, secret
Yandex Direct OAuth token
YD_LOGIN required
Default advertiser login
MCP_SECRET required, secret
The server's own secret protecting the HTTP endpoint, not the Yandex token

Limitations

The endpoint is exposed to the internet; the only protection is the MCP_SECRET, and leaking it means full access to the ad account, including deleting campaigns. Only delete_campaign has an exact-name confirmation safety catch; the other delete_* tools have none, and deletion is irreversible. Only TEXT_CAMPAIGN campaigns are supported, and deployment targets Railway.

How to disable. Remove the yandex-direct connector in Claude's settings and stop or delete the service on Railway.

FAQ

What do I do if the secret leaks?

Rotate MCP_SECRET in Railway's variables, the service restarts itself, then recreate the connector in Claude with the new URL.

Are all delete methods protected against a typo?

No, only delete_campaign requires an exact campaign-name match via confirm_name; the other delete_* tools run with no such check.

Discussion

No questions or reviews yet.

All Yandex Direct tools
Russian stack

A single-file, dependency-free Node.js Direct API v5 MCP server with a universal direct_call tool and a read-only mode

MCP serverBroad access

Yandex Direct MCP

yandex-direct-mcp

Russian stack

A Claude Code and Codex plugin for Yandex Direct: a 147-tool MCP server, OAuth, and skills for ad copy and stats analysis

PluginBroad access14
Russian stack

A dependency-free, pure Ruby MCP server with 30 tools for Yandex Direct campaigns, ad groups, ads, keywords and reports

MCP serverBroad access6
Russian stack

A fork of a popular Yandex Direct MCP server that defaults to read-only, with explicit flags for writes and finance

MCP serverBroad access

Yandex Direct MCP with launch policies

yamcp (Yandex Direct MCP Server)

Russian stack

A Yandex Direct MCP server for agencies: reports, campaign audits and safe campaign creation under fixed business policies

MCP serverBroad access2
Russian stack

20 Yandex Direct tools where every edit shows the plan by default and needs confirm=True to actually send anything

MCP serverBroad access

README in short

The README gives a step-by-step Railway deploy: New Project, environment variables, public domain generation and a /health readiness check. It separately covers connecting as a custom Claude connector via a URL with the secret in the path or header, and a security section that plainly names MCP_SECRET as the only protection and notes which delete method has a safety catch and which do not.

README badge

Report a problem