Skip to main content
Glama
dhawalshah

meta-ads-mcp

Related Servers

Alternatives to meta-ads-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • 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
      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
    • 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.
      -
    • F
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that pulls Meta Ads campaign, ad-set, and ad performance data to help users spot problems and adjust them in Ads Manager.
      6
      -

    TDQS

    A3.5/5.0

    Scored across 41 tools

    Disambiguation4/5

    Most tools target a distinct resource and action level (account, campaign, ad set, ad, creative, audience, page), and the detailed descriptions make selection feasible. A few pairs could still be confused, such as get_ad_creative_by_id vs. get_ad_creatives_by_ad_id and get_reach_estimate vs. get_delivery_estimate, but overall the boundaries are mostly clear.

    Naming Consistency3/5

    The dominant pattern is get_<resource>_by_<selector> or get_<resource>_insights, which is readable. However, naming is inconsistent: list_pages and list_ad_accounts break the get_ convention, and 'adaccount' appears without an underscore in some tools (get_adaccount_insights, get_ads_by_adaccount) while 'ad_account' appears in others (get_details_of_ad_account, list_ad_accounts).

    Tool Count2/5

    41 tools is excessive for a tool surface and makes selection harder. Many tools are near-duplicate per-parent retrieval variants, such as get_ads_by_adaccount, get_ads_by_campaign, and get_ads_by_adset, as well as four separate insights tools that could arguably be consolidated.

    Completeness2/5

    The server is entirely read-only: there are no create, update, delete, or status-change tools for campaigns, ad sets, ads, audiences, or creatives. It also lacks some obvious read endpoints such as listing all creatives for an account or fetching a single audience by ID. This is a significant gap for a server named meta-ads-mcp if any management workflow is expected.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues