Skip to main content
Glama
pralayasimha23

meta-ads-mcp

by pralayasimha23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to meta-ads-mcp

No user-submitted related servers found.

    Related Servers

    • meta-ads-mcp-patched

      Green-pep
      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

    • mlg-meta-mcp

      iammalego
      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

    • 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

    • HBCA Meta Ads MCP

      jmbrader
      F
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server for querying Meta Ads accounts through Meta's Marketing API. It provides tools to retrieve ad accounts, campaigns, ad sets, ads, and performance insights.
      -

    • meta-ads-mcp

      dhawalshah
      A
      license
      A
      quality
      B
      maintenance
      Meta (Facebook/Instagram) Ads MCP server for ad performance reporting, audience analysis, and competitor ad research.
      41
      MIT

    • meta-ads-mcp

      fujioka0729
      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
      5 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 36 tools

    Disambiguation4/5

    Most tools target distinct resources and actions (e.g., get_campaigns vs get_campaign_details), but a few pairs like get_ad_creatives vs get_creative_details (one takes ad_id, the other creative_id) and search vs search_ads_archive could cause misselection if not read carefully. The detailed descriptions largely clear up these boundaries.

    Naming Consistency4/5

    The vast majority of tools follow a verb_noun snake_case pattern (get_campaigns, create_adset, update_ad), but there are minor deviations: bare verbs 'search' and 'fetch', 'get_login_link' with three components, and inconsistent use of 'details' vs 'info' (get_ad_details vs get_account_info). Overall the pattern is predictable.

    Tool Count2/5

    With 36 tools, this server is well beyond the 25-tool threshold that the rubric considers too many. While the Meta Ads API is broad, this large surface would be heavy for an agent to navigate and many tools could potentially be consolidated.

    Completeness4/5

    The core lifecycle for campaigns, ad sets, ads, and creatives is covered (create/read/update with status archiving serving as the delete mechanism). Minor gaps include no direct listing of creatives by account and a reference to a non-existent bulk_get_insights tool in get_insights, but agents can work around these via existing tools.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources