Ads MCP on Cloudflare Workers: Direct and VK Ads

ads-mcp

A remote MCP server on Cloudflare Workers that combines Yandex Direct and VK Ads in one connector

  • 0 ★ on the repository
  • Last commit
MCP server

Broad access

Why this level

  • The generic direct_request and vk_ads_request tools can call any API method, including changing campaigns
  • Ad tokens are stored as Cloudflare Workers secrets
  • Server access is protected only by a secret in the URL path
All reasons and checks
Russian stack

igor1000rr/ads-mcp

Install

Manual install

{
  "mcpServers": {
    "ads-mcp": {
      "url": "https://ads-mcp.<account>.workers.dev/<MCP_SECRET>/mcp"
    }
  }
}

The address of your own deployed Worker with the secret in the path.

Access and checks

How we review

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

  • The generic direct_request and vk_ads_request tools can call any API method, including changing campaigns
  • Ad tokens are stored as Cloudflare Workers secrets
  • Server access is protected only by a secret in the URL path

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

What it does

The server deploys to Cloudflare Workers and answers JSON-RPC 2.0 over HTTP POST, with the access secret baked into the URL path. For Yandex Direct it exposes a campaign list, keyword list, a stats report via the Reports API, and a generic call to any API v5 method. For VK Ads it has daily stats for impressions, clicks and spend and the same kind of generic API call. A Google Ads block exists in the code, but the google_ads_status tool honestly reports that without Google's developer token moderation the other tools return an error.

Who it is for. For people running ads in both Yandex Direct and VK Ads who want one remote connector for both.

Good fit when

  • You want one MCP connector for Direct and VK Ads without a local install
  • You are fine deploying to your own Cloudflare Workers account
  • A generic API call is enough instead of a full set of narrow tools

Not a fit when

  • You need Google Ads right now: those tools are unavailable without an approved developer token
  • You do not want ad tokens passing through Cloudflare Workers
  • You need ready-made narrow tools for complex Direct scenarios rather than the generic direct_request

Example request

Show yesterday's spend and clicks for VK Ads campaigns and the active Direct campaigns

MCP

Transport
http
Authentication
API key

Environment variables

YANDEX_DIRECT_TOKEN required, secret
Yandex Direct OAuth token
YANDEX_DIRECT_LOGIN
Client login for agency-style access
VK_ADS_TOKEN required, secret
ads.vk.com API token
MCP_SECRET required, secret
The connector's path secret, generated at deploy time

Limitations

Google Ads is present in the code but does not actually work without Google's moderation, which takes time; until approved the tool honestly returns an error. API secrets live in Cloudflare, and deployment is documented only via GitHub Actions. No license file in the repository.

How to disable. Remove the MCP connector from your client settings and, if the server is no longer needed, delete the Worker in the Cloudflare dashboard.

FAQ

Does Google Ads work right after install?

No, the Google developer token goes through moderation; until approved, all Google Ads tools except google_ads_status return a clear error.

How is access to the server protected?

By a secret baked into the URL path: any other path returns 404, there is no separate auth layer.

Discussion

No questions or reviews yet.

Russian stack

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

MCP serverBroad access51Repository stars
Russian stack

A local MCP server for advertising: Yandex Direct, Avito, VK through Click.ru and Telegram Ads in one SQLite store, changes only with confirmation

MCP serverBroad access1Repository stars

VK Ads MCP server

VK Реклама MCP

Russian stack

An MCP server for VK Ads: campaigns, groups, banners, statistics and balance through chat, with in-chat account connection instead of manual OAuth

MCP serverBroad access13Repository stars
Russian stack

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

MCP serverBroad access2Repository stars

README in short

The README covers deployment to Cloudflare Workers via GitHub Actions, the connector URL format with a secret in the path, three tool tables per service with parameters, and a list of secrets with where to get them. It separately explains that until the Google developer token is approved, secrets are stubbed and the deploy stays green.

README badge

Report a problem