meta-ads-mcp-server
Related Servers
Alternatives to meta-ads-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables reading and managing Meta Ads campaigns, ad sets, ads, audiences, pages, and Business Manager using a long-lived access token and Facebook App ID. It provides 38 read/write tools and works with any MCP client over HTTP.MIT
- FlicenseNot gradedqualityDmaintenanceConnects AI assistants to Facebook's Ads API to enable natural language queries for campaign data, insights, and performance metrics. It allows users to manage ad accounts and retrieve detailed analytics like impressions, clicks, and spend through MCP-compatible interfaces.-
- FlicenseCqualityDmaintenanceEnables managing Facebook ads campaigns, ad sets, ads, creatives, insights, and audience targeting via Meta's Marketing API.39-
- FlicenseAqualityBmaintenanceA 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-
- FlicenseNot gradedqualityBmaintenanceA 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.-
- AlicenseBqualityAmaintenanceEnables MCP clients to read and analyze TikTok advertising data, with optional preview-first write tools for managing campaigns, ad groups, and budgets.3575 npmApache 2.0
TDQS
Scored across 41 tools
Several tool pairs overlap: meta_get_insights/get_insights_raw, meta_get_creatives/get_creative_assets, meta_get_page_posts/get_organic_content_enrichment, and the generic get_node_fields/list_edge_raw escape hatches can be confused with specialized readers. Descriptions do distinguish them, but the 41-tool surface still leaves meaningful ambiguity for an agent.
Almost all tools use a meta_verb_noun snake_case pattern (meta_get_*, meta_list_*, meta_search_*), which is predictable. Minor deviations like meta_health_check and meta_join_product_insights keep it from perfect consistency.
41 tools is excessive for an MCP surface, exceeding the 25+ threshold where count becomes a burden. Many are specialized read variants and raw escape hatches, making selection heavier than necessary even for a broad API.
For an explicitly read-only Meta Ads analytics/management-support server, coverage is broad: accounts, campaigns, adsets, ads, creatives, insights, audiences, catalogs, pages, videos, experiments, and raw reads. Raw node/edge/insights tools fill many schema gaps, though some niche read domains still rely on allowlisted raw access.