MCP 服务器

SergeyKrin9/mcp-servers

Russian-market marketing & ops MCP toolkit. 7 unified servers for Yandex.Direct, Yandex.Webmaster, Google Search Console (RU), YouTube Data API, VK Wall, Telegram publishing, and Click.ru (Telegram Ads + VK Ads + Yandex.Direct unified). The only complete RU-platform bundle for AI agents.

README

<sub>🐍 Python · 🇷🇺 Russian market · 🎖️ The only unified RU-platform MCP bundle · 🤖 7 servers</sub>

</div>

[!IMPORTANT] The only unified MCP toolkit for Russian-market platforms. Yandex.Direct, Yandex.Webmaster, Yandex.Metrika (via energyboost), Google Search Console, YouTube, VK, Telegram, Click.ru. No equivalent exists in awesome-mcp-servers. If you do SEO/SMM/PPC for a Russian audience and use Claude — this is your missing kit.

A collection of 7 custom Model Context Protocol (MCP) servers that wire marketing platforms into LLM-agent loops. Built so an agent (Claude Code, Claude Desktop, Cursor, Windsurf) can run ad campaigns, read analytics, publish posts, and check SEO health directly — without humans clicking buttons.

If you don't know what MCP is, start here — it's Anthropic's open protocol for plugging tools into LLM apps.

What's inside

Server	What it exposes to the agent
`clickru/`	Click.ru API — Telegram Ads, VK Ads, Yandex.Direct campaigns, balances, reports, bid manager
`yadirect/`	Yandex.Direct — create/pause campaigns, manage keywords, bids, ad copy
`yandex-webmaster/`	Yandex.Webmaster — indexing, top queries, sitemap, recrawl, problem detection
`gsc/`	Google Search Console — top queries, pages, country breakdown, indexed status
`youtube/`	YouTube Data API — videos, channels, comments, transcripts, trending
`vk/`	VK Wall API — publish, edit, pin posts, upload photos, stats
`edaru-telegram/`	Telegram Bot API — publish/edit/delete/pin posts in configured channels

Together they cover the full growth stack for a typical Russian-market product: paid ads (Direct + Telegram Ads + VK Ads via Click.ru), organic search (Yandex Webmaster + GSC), and content distribution (VK + Telegram).

Why this matters

In 2026 the bottleneck of growth isn't "what to do" — agents can plan. It's the glue between AI plans and platform APIs. These servers are that glue.

A typical workflow an LLM-agent can now run unattended:

gsc.get_top_queries('edaru.su') → see which keywords are climbing
yandex-webmaster.get_top_queries('edaru.su') → cross-check on Yandex
yadirect.get_keywords('campaign_id=...') → see which keywords we already bid on
Decide on new keywords to add → yadirect.add_negative_keywords(...), adjust bids
vk.post_to_wall(...) and edaru-telegram.publish_post(...) to push fresh content
Next day: clickru.get_campaign_stats(...) to see what worked

All without a marketer touching the console.

⚡ Quickstart (3 steps)

1. Clone & install:

git clone https://github.com/SergeyKrin9/mcp-servers.git
cd mcp-servers/yadirect            # or any other server
python3 -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt    # if present
cp .env.example .env               # fill in your credentials

2. Wire into your AI host:

<details> <summary><strong>Claude Desktop / Claude Code</strong> (<code>~/Library/Application Support/Claude/claude_desktop_config.json</code>)</summary>

{
  "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" }
    }
  }
}

</details>

<details> <summary><strong>Cursor</strong> (<code>~/.cursor/mcp.json</code>) — same JSON shape</summary>

{
  "mcpServers": {
    "vk": {
      "command": "/abs/path/to/.venv/bin/python3",
      "args": ["/abs/path/to/mcp-servers/vk/server.py"],
      "env": { "VK_TOKEN": "your-token", "VK_GROUP_ID": "123456" }
    }
  }
}

</details>

<details> <summary><strong>Windsurf</strong> (Settings → MCP Servers → Add) — same JSON shape</summary>

Identical config — Windsurf uses the same MCP server format. </details>

3. Test the loop. Open a fresh Claude chat and ask:

"Show me the top 5 search queries for edaru.su from Google Search Console for the last 7 days, then check the same in Yandex.Webmaster, then queue new keywords matching the gaps to my Yandex.Direct campaign."

If everything's wired right, Claude will run gsc.get_top_queries → yandex-webmaster.get_top_queries → yadirect.add_keywords in one tool loop — without you opening a single dashboard.

Credentials needed

Server	What to get
`clickru`	Click.ru API key + account ID (in the Click.ru dashboard)
`yadirect`	Yandex.Direct OAuth token via oauth.yandex.ru
`yandex-webmaster`	Same OAuth flow as Direct, with `webmaster:hostinfo,webmaster:verify` scopes
`gsc`	Google service account JSON with Search Console access
`youtube`	YouTube Data API v3 key (Google Cloud Console)
`vk`	VK group access token (admin rights)
`edaru-telegram`	Telegram bot token (BotFather) + chat ID

yandex-webmaster/oauth_helper.py includes a working OAuth flow if you want to grab tokens locally.

Tech stack

Python 3.10+ · stdlib + requests
mcp Python SDK
One process per platform — easy to enable/disable independently

Roadmap

Telegram Ads MCP (independent of Click.ru, native API)
Plausible / Yandex.Metrika real-time MCP (currently only reports)
One-shot CLI wrappers so you can call any of these without an MCP host

⭐ Star history

📚 Related work

agnis-workflow — the methodology that uses these MCP servers as first-class tools
broker-reels — production application: AI text-to-video for real estate marketing
awesome-mcp-servers — the canonical MCP catalog (no Russian-market entries yet — PR welcome)

Author: Sergey Krinitsyn · sergeykrin98@gmail.com · GitHub

<sub>If you ship to a Russian audience and use Claude — drop a ⭐. It tells me to keep adding servers.</sub>

</div>