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
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
- Creates and changes real campaigns, groups and banners with no sandbox
- Uploads user lists by email and phone for remarketing audiences
Install
Manual install
git clone https://github.com/lexamarketolog/vk-ads-mcp.git && cd vk-ads-mcp && uv syncInstall from the README; the key goes in .env as VK_ADS_ACCESS_TOKEN.
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 siteLimitations
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.
MCP
- Transport
- stdio
- Authentication
- API key
| 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. |
Security check
- Creates and changes real campaigns, groups and banners with no sandbox
- Uploads user lists by email and phone for remarketing audiences
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.
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.
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