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
      19 npm
      4
      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
      A
      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.
      5 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
      60 npm
      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 22 tools

    Disambiguation4/5

    Tools are largely distinct by resource (auth, throttling, regions, ad plans, groups, banners, statistics, raw). The action tools (create/update/delete) for each resource are clearly separated. Slight ambiguity between raw_request and the specific tools, but raw_request is explicitly a fallback, making the boundary clear.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (get_, list_, create_, update_, action). However, there are deviations: 'auth_status', 'start_login', 'finish_login', 'logout' use a different style, and 'get_throttling' and 'get_regions' are fine but 'ad_plan_action' could be more consistent as 'update_ad_plan_status'. Minor inconsistencies, but overall predictable.

    Tool Count4/5

    With 22 tools, the server is on the heavier side but still reasonable for a full ad management platform. Each tool maps to a distinct entity or workflow, covering auth, config, and core CRUD plus statistics and a raw fallback. Slightly beyond the ideal 15, but not excessive for the scope.

    Completeness4/5

    The server covers the full lifecycle for ad plans, ad groups, and banners (list, create, update, status action, delete via action). It also includes statistics and a raw request for edge cases. Minor gaps like missing budget adjustment standalone or reporting endpoints are covered by raw_request, making the surface reasonably complete.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources