Meta Ads MCP
Related Servers
Alternatives to Meta Ads MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA Model Context Protocol server that lets AI assistants run your Meta Ads end to end — launch campaigns, upload creatives, update budgets, and dig into performance through natural conversation. Works across Facebook, Instagram, and other Meta surfaces.Business Source 1.1
- AlicenseNot gradedqualityBmaintenanceA self-hosted Model Context Protocol (MCP) server that gives AI agents secure, multi-tenant access to the Meta Marketing API for Facebook Ads and Instagram Ads. It enables campaign management, audience targeting, insights, lead management, and more across multiple ad accounts.MIT
- AlicenseAqualityCmaintenanceA Model Context Protocol server for the Meta (Facebook) Ads API, providing 54 tools to manage ad accounts, campaigns, ad sets, ads, creatives, media, insights, targeting, and more via the Meta Graph API.35236 npm16MIT
- AlicenseNot gradedqualityDmaintenanceAn 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 npm4MIT
- AlicenseCqualityCmaintenanceA local Model Context Protocol server that enables interaction with the Meta Marketing API to manage ad accounts, campaigns, and creatives. It provides tools for targeting research, insight reporting, and campaign management through local MCP clients like Claude Code and Cursor.4075AGPL 3.0
- FlicenseNot gradedqualityDmaintenanceA comprehensive MCP server for managing and analyzing Meta Ads (Facebook/Instagram) with over 80 natural-language tools for AI agents like Claude Desktop.-
TDQS
Scored across 35 tools
Most tools map to a distinct entity and action, and the list/detail pairs (get_campaigns vs get_campaign_details, get_ads vs get_ad_details) are clearly separated by singular vs plural/id target. A few pairs could be confused—get_account_pages vs search_pages_by_name when no search term is provided, and get_ad_creatives vs get_creative_details—but the descriptions generally clarify which ID type is needed.
All 35 tools follow a predictable snake_case verb_noun pattern: get/create/update for entities, search_ for targeting and archive lookups, and upload/compute/estimate for supporting operations. The campaign/adset/ad/creative hierarchy is mirrored exactly in names, so an agent can infer the purpose of each tool from its name alone.
35 tools is well above the ideal 3-15 range and even above the 16-25 range that already feels heavy. The Meta Ads domain is broad and most tools have a distinct workflow purpose, but creative retrieval variants and targeting search helpers could be consolidated to reduce selection overhead.
Core lifecycle coverage is strong: create/read/update exist for campaigns, ad sets, ads, and creatives, plus insights, targeting estimation, budget schedules, and ads-archive search. Notable gaps are the absence of delete operations for any entity, no way to list all creatives in an account, and get_insights referencing a bulk_get_insights tool that is not actually in the server.