SkillFoxx

VK Ads MCP server on top of the myTarget API v2

vk-ads-mcp

A VK Ads MCP server built on the myTarget API v2 with 49 to 55 tools: campaigns, remarketing, lookalikes, product feeds and agency access

  • 3 ★ on the repository
  • Last commit
  • MIT
MCP server

Broad access

Why this level

  • Creates and changes real campaigns, groups and banners with no sandbox
  • Uploads user lists by email and phone for remarketing audiences
All reasons and checks
Russian stack

lexamarketolog/vk-ads-mcpAuthor:lexamarketolog

Install

Services

Manual install

git clone https://github.com/lexamarketolog/vk-ads-mcp.git && cd vk-ads-mcp && uv sync

Install from the README; the key goes in .env as VK_ADS_ACCESS_TOKEN.

Access and checks

How we review

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

  • Creates and changes real campaigns, groups and banners with no sandbox
  • Uploads user lists by email and phone for remarketing audiences

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

What it does

The server wraps the myTarget API v2 that VK Ads technically runs on into tools for campaigns, ad groups, banners, content upload, statistics (daily, summary, broken down by age, gender, region, placement, OS and device, including async reports), remarketing groups, pixels, custom audience lists from hashed emails and phones, lookalikes, product feeds and agency access to client accounts. It separately explains a terminology trap: what the new ads.vk.com UI calls "Campaign" is ad_plan in the API, while "Ad group" is campaign, and warns that a campaign created without an ad_plan_id becomes an invisible orphan in the new UI.

Who it is for. For developers and agencies that need a broader VK Ads toolset than basic servers, including remarketing and product feeds.

Good fit when

  • You need remarketing, pixels and lookalikes, not just campaigns and stats
  • You need product feeds for dynamic ads
  • You need agency access to several client accounts through one server

Not a fit when

  • The gap between UI terms and API terms is a dealbreaker for you: you need to read the server's docs carefully, or you can easily create an invisible orphan group
  • You need a stable release: the README itself calls the project v0.4-dev

Example request

Create a lookalike audience from a customer list and set up a remarketing pixel for the site

MCP

Transport
stdio
Authentication
key is optional

Environment variables

VK_ADS_ACCESS_TOKEN secret
Ready access token from the ads.vk.com account, auth option A.
VK_ADS_CLIENT_ID
Client id of a registered VK app for OAuth2 client credentials, option B.
VK_ADS_CLIENT_SECRET secret
Client secret for option B.
VK_ADS_AGENCY_CLIENT_NAME
Client login for agency access, option C.

Limitations

The project is at v0.4-dev status by the README's own description. A campaign entity created without an ad_plan_id succeeds but becomes invisible in the new ads.vk.com UI, an easy mistake to make. The three auth options (a ready token, OAuth2 client credentials, agency access) are easy to mix up.

How to disable. Remove the server from your MCP client config.

FAQ

Why did an ad group disappear from the UI?

It was likely created via the campaign tool without an ad_plan_id and became an orphan; the README advises always creating through create_ad_plan with a nested campaigns array.

Which auth method is simplest?

A ready access token from the ads.vk.com account, Settings profile, API section, option A in the README, needs no app registration.

How is the VK Ads MCP different from other VK Ads servers?

The server is built on myTarget API v2, which VK Ads technically runs on, and gives 49–55 tools: campaigns, ad groups, banners, content upload, statistics, remarketing, look-alike, product feeds and agency access.

Why did an ad group disappear from the interface and which auth is simplest?

Groups removed through the API may not show in the interface, check status through the statistics tool. Starting with a client token is simplest, other ways are in the README. Install with git clone and run per the instructions. It works in Claude Desktop, Claude Code and Cursor. Risk is high.

Discussion

No questions or reviews yet.

All VK tools

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 access13
Russian stack

A read-only MCP server for VK Ads: statistics, campaign structure, top objects by metric and CSV export

MCP serverExtended access1
Russian stack

A VK Ads MCP server with a turnkey installer: 136 tools, VK community research and a skill for several agents at once

MCP serverBroad access
Russian stack

A hardened VK Ads MCP fork: read-only by default, mutations gated by VK_ADS_ENABLE_WRITES, and SSRF protection on file uploads

MCP serverBroad access
Russian stack

A VK API MCP server for business: community shop, posts, ads, stats, messages and lead forms with write confirmation

MCP serverBroad access3
Russian stack

A skill that walks an agent through the full VK Ads campaign path: from competitors and audiences to banners and a paused account structure

SkillExtended access3

README in short

The English README has a dedicated section on the VK Ads UI-versus-API terminology mismatch, with a mapping table and an explicit warning about orphan groups, states the v0.4-dev status with tool and test counts, three ways to get a token, and a full tool list by topic: campaigns, groups, banners, content, statistics, remarketing, pixels, user lists, lookalikes, product feeds, agency access.

README badge

Report a problem