Direct Manager: subscription MCP for Yandex Direct
Direct Manager
A paid connector service for Yandex Direct, VK and Avito with analytics, wasted-spend detection and an autopilot layer over the Direct API
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- Can pause campaigns and change budgets, bids and negative keywords in a live account
- The Yandex token and account data are stored on a third-party commercial service
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/direct-managerDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Assembled automatically, review before installing.
This entry is high risk, so there is no one-click install. Review the code and add the config by hand.
Run in a terminal
claude mcp add --transport stdio marketscore-direct-mcp -- npx -y marketscore-direct-mcpOr add to the file .mcp.json, in the project
{
"mcpServers": {
"marketscore-direct-mcp": {
"command": "npx",
"args": [
"-y",
"marketscore-direct-mcp"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"marketscore-direct-mcp": {
"command": "npx",
"args": [
"-y",
"marketscore-direct-mcp"
]
}
}
}If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.
Run in a terminal
code --add-mcp '{"name":"marketscore-direct-mcp","type":"stdio","command":"npx","args":["-y","marketscore-direct-mcp"]}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"marketscore-direct-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"marketscore-direct-mcp"
]
}
}
}If the file already exists, add the server inside the servers key.
Run in a terminal
codex mcp add marketscore-direct-mcp -- npx -y marketscore-direct-mcpOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.marketscore-direct-mcp]
command = "npx"
args = ["-y", "marketscore-direct-mcp"]If the file already exists, append the block to the end.
Add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"marketscore-direct-mcp": {
"command": "npx",
"args": [
"-y",
"marketscore-direct-mcp"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Add to the file ~/.config/devin/mcp_config.json, for all projects
{
"mcpServers": {
"marketscore-direct-mcp": {
"command": "npx",
"args": [
"-y",
"marketscore-direct-mcp"
]
}
}
}If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.
Formerly Windsurf.
Add to the file cline_mcp_settings.json, for all projects
{
"mcpServers": {
"marketscore-direct-mcp": {
"command": "npx",
"args": [
"-y",
"marketscore-direct-mcp"
]
}
}
}If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.
Add to the file .roo/mcp.json, in the project
{
"mcpServers": {
"marketscore-direct-mcp": {
"command": "npx",
"args": [
"-y",
"marketscore-direct-mcp"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
A fork of Roo Code, same .roo folders.
Add to the file opencode.json, in the project
{
"mcp": {
"marketscore-direct-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"marketscore-direct-mcp"
]
}
}
}If the file already exists, add the server inside the mcp key.
Add to the file ~/.config/zed/settings.json, for all projects
{
"context_servers": {
"marketscore-direct-mcp": {
"command": "npx",
"args": [
"-y",
"marketscore-direct-mcp"
]
}
}
}If the file already exists, add the server inside the context_servers key.
Add to the file .codeassistant/mcp.json, in the project
{
"mcpServers": {
"marketscore-direct-mcp": {
"command": "npx",
"args": [
"-y",
"marketscore-direct-mcp"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Sign up at app.marketscore.ru, add https://app.marketscore.ru/api/mcp in a URL-capable MCP client like Claude and complete OAuth login; for Cursor, VS Code and similar clients use the npx -y marketscore-direct-mcp bridge.
Other ways from the author
https://app.marketscore.ru/api/mcpRemote connector by URL, authorized via browser OAuth.
This is third-party code. Review the repository files before installing.
What it does
This repository is a thin npm bridge that connects local MCP clients like Cursor or VS Code to the remote Direct Manager service. The service itself, Direct API access and all logic live on marketscore.ru: users sign in via OAuth, and the Yandex token never reaches the assistant or the client config. Depending on the plan, the service exposes up to 116 tools: analytics and breakdowns by device, gender, geography and network placement, campaigns with ROAS below 1 or spend without conversions, control over pausing, budgets, strategies, negative keywords and bids, building campaigns from scratch, and AI outputs like a 30-day spend forecast and a one-call weekly brief. A separate second MCP address on the same account covers SEO: Webmaster, Search Console, Metrica and Topvisor.
Who it is for. For marketers and agencies willing to pay for ready-made analytics and an autopilot layer over Yandex Direct instead of setting up an open-source wrapper themselves.
Good fit when
- You want ready wasted-spend diagnostics without running your own server
- You want one login covering Direct, VK and Avito with no Yandex token stored in your config
- You need a portfolio view across all of an agency's client accounts at once
Not a fit when
- You need a free option: with no active plan the service returns 0 tools
- You need full control over the code and token with no third-party service in between
- A plain open-source Direct API wrapper without analytics or a subscription is enough
Example request
Where is my budget being wasted over the last 14 days, and what should I turn offLimitations
This is a proprietary paid service: 990 to 9,900 rubles per month depending on the plan, with the first 7 days of the Pro plan free. With no active subscription, tools are unavailable entirely. The Yandex token and data live on Direct Manager's servers, not locally. SEO tools need a separate subscription and connection address. Paid Topvisor operations like starting a position check are deliberately kept out of chat.
How to disable. Disable the connector in your AI application's settings, or revoke access in the Direct Manager dashboard; changing the account password revokes all issued MCP access.
MCP
- Transport
- http, stdio
- Authentication
- OAuth
Security check
- Can pause campaigns and change budgets, bids and negative keywords in a live account
- The Yandex token and account data are stored on a third-party commercial service
README in short
The README presents the Direct Manager connector with two MCP addresses: an ads one with 111 to 116 tools and a separate SEO one with 21 tools, gives a pricing table, an honest comparison against open-source wrappers, and a security model description via OAuth 2.1 and RF-hosted personal data. It separately lists exactly which tools write data and which only read.
FAQ
Where does the Yandex Direct token go?
It is issued to the Direct Manager service during OAuth connection and stored on its servers; the assistant and MCP client never see it.
How is this different from an open-source Direct API wrapper?
Per the README comparison: no own token or hosting needed, plus AI outputs, a web dashboard and an account portfolio, but it is a paid subscription rather than free self-hosting.
Related
A skill that strips AI writing tells from text using Wikipedia's list, without adding invented facts
Marketing Skills for AI agents
Marketing Skills for AI Agents
About fifty skills for CRO, copywriting, SEO, analytics, ads and launches, built for coding agents
SendPulse MCP server
SendPulse MCP
SendPulse's official remote MCP server: statistics, campaigns and user data through an agent chat
Yandex Direct MCP generated from a machine-readable schema
yandex-direct-mcp
An MCP server and CLI covering all 113 Yandex Direct API v5 methods generated from WSDL, exposing 9 read tools by default and writes only on demand