Skip to main content
Glama
mikusnuz

meta-ads-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to meta-ads-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • meta-ads-mcp-patched

      Green-pep
      A
      license
      B
      quality
      F
      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

    • Meta Ads MCP

      AbnerZx
      A
      license
      C
      quality
      F
      maintenance
      MCP server for the Meta Marketing API with 118 typed tools across ads, insights, pixels/CAPI, pages, Instagram, WhatsApp, catalogs, audiences, leads, and billing, featuring secure token storage and a confirmation gate on destructive calls.
      100
      1
      MIT

    • Meta Ads MCP Server

      gabe-almeida
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for programmatic management of Meta (Facebook/Instagram) advertising campaigns through AI assistants. It enables campaign creation, ad set management, creative upload, analytics, audience management, and conversion tracking.
      236 npm
      4
      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

    B3.2/5.0

    Scored across 134 tools

    Disambiguation3/5

    Many tools have clearly distinct purposes (e.g., create_campaign vs create_adset), but the sheer number (134) creates inevitable overlap among lead-related tools (get_lead, get_campaign_leads, get_adset_leads, get_form_leads), targeting search tools (search_targeting, search_targeting_map), and business/account listing tools. Descriptions help, but similar naming patterns and volume increase misselection risk.

    Naming Consistency5/5

    All tool names use consistent snake_case with a verb_noun pattern (list_campaigns, create_campaign, delete_campaign, get_campaign_insights). Even compound names like add_users_to_audience and remove_from_block_list follow a predictable verb_object structure, with no mixing of conventions.

    Tool Count1/5

    134 tools is far beyond the typical well-scoped range (3–15) and constitutes an extreme mismatch for a single MCP server. Even a comprehensive API surface could be organized into fewer, more focused tools or resources; the large count makes discovery and correct selection difficult.

    Completeness4/5

    The server covers an extensive range of Meta Ads operations including campaigns, ad sets, ads, creatives, audiences, catalogs, rules, and business management. However, some lifecycle gaps exist (e.g., no delete for creatives, catalogs, product sets, or saved audiences), though agents can often work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources