Skip to main content
Glama

Related Servers

Alternatives to adops-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Hosted remote MCP for Google Ads, Meta Ads (Facebook and Instagram), GA4 and Google Search Console. Connect Claude, ChatGPT, Cursor, Claude Code or Grok with a Google or Facebook login: audits, search terms, GAQL and Insights reports, keyword research, AI-referral traffic, and approved changes to budgets, bids and negatives. OAuth 2.1, no API keys, free.
      1,870
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for managing Google Ads, Meta Ads, LinkedIn Ads, and TikTok Ads via AI. 210+ tools including account audits, wasted spend detection, and PMax insights.
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Meta Ads providing 30 tools for account discovery, campaign management, targeting research, and insights. Designed with LLM-friendly outputs and productivity features like cloning and bulk operations.
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server for managing and analyzing Meta Ads (Facebook/Instagram) with over 80 natural-language tools for AI agents like Claude Desktop.
      -
    • 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
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Google Ads API — 22 tools for campaigns, keywords, RSAs, assets, audiences, geo/device performance, impression share, auction insights, and budget pacing. Community edition with B2B/agency-focused tooling beyond the official Google MCP.
      22
      30 npm
      1
      MIT

    TDQS

    A4/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools map to clearly distinct workflows—reporting, budget analysis/execution, A/B testing, forecasting, anomaly detection—and the descriptions reinforce those boundaries. The main residual ambiguity is between campaign_update and campaign_pause_resume, both of which can change status, though their batch vs. single-campaign roles are reasonably clear.

    Naming Consistency3/5

    Names are readable and often follow an object-first style like campaign_create, budget_analyze, and anomaly_detect. However, the pattern is inconsistent: campaign_list and ads_report are noun phrases, forecast_spend reverses the order, and ad_csv_import / ad_demo_seed mix objects, formats, and verbs in unpredictable ways.

    Tool Count4/5

    Seventeen tools is slightly above the ideal 3–15 range, but the broad ad-ops scope justifies the count: ingestion, setup, campaign management, reporting, analysis, forecasting, and exportable recommendations all earn their place. It feels comprehensive rather than bloated.

    Completeness4/5

    The tool surface covers data import, account registration, campaign lifecycle management, reporting, budget analysis and execution, forecasting, anomaly detection, A/B testing, benchmarking, and exportable recommendations—so core workflows have no dead ends. Missing pieces like single-campaign detail retrieval, account disconnection, and ad-group-level management are minor relative to the stated campaign-level purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues