VK Ads MCP
Related Servers
Alternatives to VK Ads MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceMCP server for VK Ads API enabling management of campaigns, ads, statistics, targeting, and budgets through natural language.820 npm5MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for VK Ads API (myTarget v2) that allows AI agents to manage advertising accounts: create and modify campaigns, ads, upload creatives, and fetch statistics.145 npm6Apache 2.0
- AlicenseNot gradedqualityCmaintenanceLocal MCP server that integrates with VK Ads API and Core VK API, providing 128 tools for managing ad campaigns, audiences, creatives, statistics, and analyzing VK communities.1MIT
- AlicenseAqualityDmaintenanceRead-only MCP server for analyzing VK Ads campaigns, listing ad structures, retrieving statistics, and generating optimization recommendations.81MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Meta/Facebook Marketing API allowing you to view and manage ad accounts, campaigns, ad sets, ads, and creatives, as well as fetch insights and upload ad images.MIT
- AlicenseAqualityBmaintenanceMCP server that enables natural-language interaction with the Avito Ads advertising API, including campaign, ad group, and creative management, statistics retrieval, fund transfers, and ORD paperwork filing.26103 npm1MIT
TDQS
Scored across 23 tools
Most tools map cleanly to distinct resources and actions (auth lifecycle, account info, CRUD per campaign/group/banner, media, raw escape hatch). Minor overlap exists between auth_status and get_user_info (both expose token/account introspection) and between update_* and *_action tools, but descriptions explicitly clarify the split. An agent can reliably choose the right tool in practice.
All names use snake_case, but the verb patterns vary: list/create/update_<resource>, <resource>_action for status changes, get_* for reads, and standalone auth lifecycle verbs (start_login, finish_login, logout). The resource-action split is deliberate and readable, but the set isn't a uniform verb_noun convention throughout.
23 tools is on the heavy side of typical MCP servers, but the surface covers a genuinely large domain: auth lifecycle, account/balance/limits/regions, three hierarchical CRUD resources, media upload, and a raw API fallback. Each tool has a distinct role, though some account/support tools could arguably be consolidated.
The server covers full lifecycle operations for campaigns (ad_plans), ad groups, and banners (list/create/update/status actions), plus auth setup, balance, statistics, regions, throttling, media upload, and a raw_request escape hatch for anything unmapped. Minor omissions (e.g., banner content updates or single-object getters) are workable via list filters or raw_request.