Skip to main content
Glama
askads

VK Ads MCP

by askads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to VK Ads MCP

No user-submitted related servers found.

    Related Servers

    • vk-ads-mcp

      theYahia
      A
      license
      B
      quality
      B
      maintenance
      MCP server for VK Ads API enabling management of campaigns, ads, statistics, targeting, and budgets through natural language.
      8
      10 npm
      5
      MIT

    • vk-ads-mcp

      ai-hub-open
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP 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 npm
      6
      Apache 2.0

    • VK Ads MCP All in One

      sergeylopukhov
      A
      license
      Not graded
      quality
      C
      maintenance
      Local 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.
      3 npm
      MIT

    • vk-ads-mcp

      Qusto
      A
      license
      A
      quality
      D
      maintenance
      Read-only MCP server for analyzing VK Ads campaigns, listing ad structures, retrieving statistics, and generating optimization recommendations.
      8
      1
      MIT

    • facebook-ads-mcp-server

      HeroBrian389
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP 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

    • Avito Ads MCP

      A1-x-Tech
      A
      license
      A
      quality
      A
      maintenance
      MCP 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.
      26
      31 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 23 tools

    Disambiguation4/5

    Each resource (ad_plan, ad_group, banner) has a clear list/create/update/action split, and descriptions explicitly cross-reference the *_action tools for status changes so update vs action boundaries are documented. The only real overlap is raw_request, which intentionally duplicates every endpoint as an escape hatch, plus mild potential confusion between update_* and *_action for the same object.

    Naming Consistency3/5

    Everything is snake_case, but verb conventions vary: three different patterns are used for the same resource (list_ad_plans, create_ad_plan, update_ad_plan, ad_plan_action). Bare verbs (logout, raw_request) and noun-style names (auth_status, *_action) mixed with verb_noun reduce predictability, though it stays readable.

    Tool Count4/5

    23 tools is on the heavy side, but the surface maps cleanly onto three resource types (each with list/create/update/action), plus media upload, statistics, auth lifecycle, and admin helpers. No obvious filler tools; each earns a place for a real ads platform.

    Completeness4/5

    Core lifecycle is covered: list/create/update/status-change for campaigns, groups, and banners, plus stats, image upload, throttling, auth, and balance. Minor gaps exist (no dedicated get-single calls, only regions for targeting enumerations like interests/packages, no audience or keyword management), but raw_request lets agents reach uncovered endpoints.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources