SkillFoxx

MCP server bundle for Russian-market ads and SEO

MCP Servers (SergeyKrin9)

Seven independent MCP servers in one repository: Yandex Direct, Yandex Webmaster, VK, Telegram, Click.ru, Search Console and YouTube

  • 2 ★ on the repository
  • Last commit
MCP server

Broad access

Why this level

  • The yadirect server creates and pauses ad campaigns with a real budget
  • The vk and edaru-telegram servers publish posts on behalf of the community and channel with no platform-side preview
All reasons and checks
Russian stack

sergeykrin9/mcp-serversAuthor:Sergey Krinitsyn

Install

Manual install

{
  "mcpServers": {
    "yandex-direct": {
      "command": "/abs/path/to/mcp-servers/yadirect/.venv/bin/python3",
      "args": ["/abs/path/to/mcp-servers/yadirect/server.py"],
      "env": { "YANDEX_DIRECT_TOKEN": "your-token" }
    }
  }
}

Example for one server in the set, yadirect; the others connect the same way from their own folder.

Access and checks

How we review

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

  • The yadirect server creates and pauses ad campaigns with a real budget
  • The vk and edaru-telegram servers publish posts on behalf of the community and channel with no platform-side preview

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

What it does

The repository bundles seven separate Python servers, each in its own folder with its own server.py and env vars: yadirect for Yandex Direct campaigns, keywords and bids, yandex-webmaster for indexing and top queries, vk for posting to a group wall, edaru-telegram for publishing to a Telegram channel via the Bot API, clickru as a Click.ru proxy to Direct, VK Ads and Telegram Ads, plus gsc for Google Search Console and youtube for YouTube data. The servers are independent: any single one can be enabled without installing the rest. The author describes a typical flow where an agent cross-checks queries in Search Console and Webmaster, adds negative keywords to Direct, and publishes to VK and Telegram unattended.

Who it is for. For marketers and SMM specialists running Russian-market promotion across several channels who are willing to configure each server separately.

Good fit when

  • You only need one channel from the set, for example publishing to a Telegram channel via your own bot
  • You want to cross-check Search Console and Yandex Webmaster data and push negative keywords to Direct in one flow
  • You have a Click.ru account and want one proxy to Direct, VK Ads and Telegram Ads

Not a fit when

  • You want one single-server install: each component is deployed separately with its own venv
  • You need formal tests and CI: none are in the repository
  • You need Click.ru for agency clients with separate accounts rather than for yourself

Example request

Show the top 5 site queries from Google Search Console and Yandex Webmaster for the week, and suggest Direct negative keywords from the overlap

MCP

Transport
stdio
Authentication
API key

Environment variables

YANDEX_DIRECT_TOKEN required, secret
OAuth token for the yadirect server
VK_TOKEN required, secret
VK group access token with admin rights for the vk server
VK_GROUP_ID required
VK group id

Limitations

Each of the seven servers is installed and configured separately: its own venv, its own env vars and, where needed, its own requirements.txt. There are no formal tests or CI in the repository. The Telegram server is named after the author's personal project (edaru.su) and is built for one configured bot and channel. There is no catalogue slug for Click.ru yet.

How to disable. Remove the relevant server block, for example yandex-direct, from your MCP client config; the rest of the repository's components are unaffected.

FAQ

Do I need to install all seven servers at once?

No, each server is independent; you can run just one, such as vk or yadirect, without touching the other repository folders.

Is there a Yandex Metrica module?

Not yet, the README's Roadmap section lists it as a planned next addition.

Discussion

No questions or reviews yet.

All Yandex Direct tools
Russian stack

Monorepo of Yandex MCP servers: Direct, Metrica, Webmaster, Wordstat, Tracker, 360, Maps, SpeechKit, YandexGPT and AppMetrica

MCP serverBroad access14
Russian stack

An MCP server for Yandex Direct, Metrika, Wordstat and Webmaster: campaigns, ads, bids, reports and keyword research from chat

MCP serverBroad access58
Russian stack

An MCP server for Yandex Direct, Metrica, Audiences and Wordstat with read-only mode and change confirmation

MCP serverBroad access50
Russian stack

A ZAI.ONE MCP server bringing Direct, Metrika, search, Wordstat and Webmaster into one agent, with a setup wizard and opt-in write operations

MCP serverBroad access1
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

README in short

The README presents the repository as a one-of-a-kind MCP server bundle for the Russian market, gives a table of the seven servers and what each exposes to the agent, a three-step quickstart with Claude Desktop, Cursor and Windsurf configs, and a table of credentials needed per service. It ends with a roadmap: a native Telegram Ads MCP and real-time Yandex Metrica.

README badge

Report a problem