Skip to main content
Glama
AbnerZx

Meta Ads MCP

by AbnerZx

Related Servers

Alternatives to Meta Ads MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the Meta Marketing API enabling ad performance reports and operational adjustments like pause/resume and budget changes on client ad accounts, with strict allowlist and read-only safeguards.
      -
    • 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
    • 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
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for Meta Ads (Facebook Ads) that provides tools for account discovery, campaign/adset/ad creation, custom audiences, status updates, performance reporting, and A/B testing.
      36
      Business Source 1.1
    • A
      license
      Not graded
      quality
      C
      maintenance
      Unified MCP server for managing Meta Ads, LinkedIn Ads, Google Ads, GA4, and Search Console with 89 read/write tools, multi-account support, OAuth setup, and safe dry-run mutations.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      An MCP server for managing Meta Ads campaigns, ad sets, lead forms, and media uploads, patched to support Meta Marketing API v25 requirements.
      100
      MIT

    TDQS

    C2.9/5.0

    Scored across 118 tools

    Disambiguation3/5

    The domain prefixes help, but several tools have fuzzy boundaries: insights_get overlaps with insights_get_account_summary and billing spend tools, ads_get_ad_preview overlaps with creatives_preview, and catalog_list is easy to mistake for catalog_list_products. Descriptions usually clarify the intended entity, but the agent has to rely on reading closely rather than clear separation.

    Naming Consistency4/5

    Most tools follow a consistent domain_prefix + verb_noun pattern (ads_list_campaigns, ads_create_campaign, ads_pause_adset, wa_send_text_message). There are a few deviations like billing_summary_all_accounts (missing verb), bare catalog_list/creatives_list, and the generic insights_get, but these are minor against the overall predictable structure.

    Tool Count1/5

    118 tools is far beyond the extreme threshold and makes the server unwieldy for an agent to navigate. The broad coverage across Ads, Catalogs, Creatives, IG, Pages, WhatsApp, Leads, Pixels, Billing, and Graph API would be much better scoped as several smaller, focused servers.

    Completeness3/5

    The core ads lifecycle—campaigns, ad sets, ads, creatives, insights—is well covered. However, several included subdomains are incomplete: catalogs and product sets can be created but not updated/deleted, custom audiences are read-only, and creatives have no update path, which are notable gaps that could block agents working outside the main campaign path.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive