Skip to main content
Glama
meta-ads-mcp-server

meta-ads-mcp-server

Related Servers

Alternatives to meta-ads-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that exposes Meta Marketing API to Claude, enabling analysis and management of Facebook/Instagram ad accounts, including campaigns, insights, and budget adjustments with safety confirmations.
      808 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server to manage Meta Ads (Facebook/Instagram) campaigns, ad sets, insights, and audiences from Claude Code using natural language.
      9
      8 npm
      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
      B
      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.
      31
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted MCP server that gives Claude read and write access to Google Ads, Meta Ads, GA4, Search Console and Microsoft Clarity through roughly 216 tools, covering reporting, campaign building, audiences, keyword and search-term analysis, and raw API queries. Every account-changing call is preview-first: it validates and returns a preview by default and only applies the change once explicitly confirmed, with new Meta campaigns, ad sets and ads created paused.
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      A platform-agnostic MCP server that connects Claude to campaign data, institutional knowledge, and historical performance for paid media teams, enabling automated analysis, reporting, and debugging.
      73
      -

    TDQS

    A3.9/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct data view: account listing, campaign list, campaign performance, creative performance, audience breakdown, budget, ad sets, ads, creatives, and debug insights. The parallel performance tools are clearly separated by level or dimension.

    Naming Consistency5/5

    All tools follow a consistent get_ prefix with a readable resource or metric descriptor. Plural nouns are used for list endpoints and entity_metric patterns for analytics endpoints, with only get_debug_insights as a mild outlier.

    Tool Count5/5

    Ten tools is well within the ideal range and each one serves a clear purpose in a read-only Meta Ads workflow. There is no obvious redundancy or unnecessary bloat.

    Completeness4/5

    The read-only surface covers the full account → campaign → ad set → ad → creative hierarchy plus performance, budget, audience breakdown, and debug insights. Minor gaps exist such as no ad-set-level or ad-level performance endpoint and no write/management operations, but the tool set appears intentionally observational.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues