Skip to main content
Glama
skynes

AdsMCP

by skynes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to AdsMCP

No user-submitted related servers found.

    Related Servers

    • yadirect-mcp

      Lermont
      A
      license
      A
      quality
      B
      maintenance
      A local MCP server that connects Yandex Direct advertising reports and safe campaign creation to AI agents, enabling natural-language analytics and protected campaign setup.
      8
      2
      MIT

    • flour-ads

      Wayy-Research
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for managing ad campaigns across Google Ads, Meta, and more. Enables deploying campaigns, checking performance, and managing budgets from terminal or AI assistants.
      MIT
    • Markifact MCP Server by markifact

      Markifact MCP Serverofficial

      markifact
      A
      license
      Not graded
      quality
      C
      maintenance
      A universal marketing MCP server that lets AI clients manage 20+ ad and marketing platforms (Google Ads, Meta, TikTok, etc.) with 500+ operations, including write actions with user approval.
      53
      MIT

    • safent-ads

      devwspito
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables self-hosted Google Ads and Meta Ads management through MCP, with human approval, hard spending limits, and audited writes; agents like Claude Code or Codex can connect to ad accounts while the server controls all credential access and platform writes.
      Apache 2.0
    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

    C2.8/5.0

    Scored across 143 tools

    Disambiguation2/5

    The set contains many near-overlapping tools, especially across Telegram Ads report/sync/API variants, Telegram action queues, public reply/post research, and multiple local catalog tools. Descriptions add context, but an agent can easily confuse names like ads_telegram_ads_report vs ads_telegram_ads_api_report or ads_telegram_ai_post_list vs ads_interest_research_post_list.

    Naming Consistency4/5

    All tools use an ads_ prefix and snake_case, giving a mostly predictable namespace. However, action ordering is uneven across compound names, there is a visible typo in ads_dashbord_start/stop, and similar concepts use inconsistent labels such as cards_get vs card_get and dstore vs tg_resource.

    Tool Count1/5

    143 tools is far too many for a coherent MCP surface. Even for a broad advertising automation server, the set spans many domains, providers, local catalogs, research workflows, networking, and messaging channels, making discovery and correct selection very difficult.

    Completeness3/5

    The surface is broad and covers many advertising, reporting, sync, outreach, and local analytics workflows, but lifecycle coverage is uneven. Some entities lack delete operations, several ad platforms are mostly read/sync-only, and write coverage is concentrated in specific providers such as Telegram, Yandex Direct, and Mastodon.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources