konquest-meta-ads-mcp
Related Servers
Alternatives to konquest-meta-ads-mcp
- AlicenseAqualityBmaintenanceA Model Context Protocol server that allows AI models to access, analyze, and manage Meta advertising campaigns, enabling LLMs to retrieve performance data, visualize ad creatives, and provide strategic insights for Facebook and Instagram platforms.371,252Business Source 1.1
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables users to create, manage, and monitor Meta (Facebook/Instagram) ad campaigns directly from Claude using natural language.11MIT
- AlicenseBqualityAmaintenance50 tools for Meta Ads campaign management, creative analysis, audience building, and conversion tracking, accessible to any MCP-compatible AI agent.6842712MIT
- AlicenseNot gradedqualityDmaintenanceManage Facebook and Instagram ad campaigns directly from Claude Code, enabling performance viewing, budget adjustments, and campaign control without opening Ads Manager.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to fetch and analyze Meta ad accounts, campaigns, ad sets, ads, and performance insights via the Meta Marketing API.1,054MIT
- AlicenseNot gradedqualityDmaintenanceConnects Claude with the Meta Marketing API to analyze and manage Facebook/Instagram ad campaigns, including retrieving insights, updating campaign status, and listing accounts.133MIT
- AlicenseNot gradedqualityCmaintenanceA Windows-ready MCP server to manage Meta Ads with Claude Code, providing ad creation, targeting checks, diagnostics, and safety gates for supervised ad operations.1MIT
TDQS
Scored across 57 tools
Most tools target distinct resources with clear get/create/update verbs, but there are overlapping creation paths (create_ad_from_manifest, create_multi_asset_ad, create_ad_creative) and two video upload tools serving the same purpose. Several pixel/tracking diagnostic tools also have blurry boundaries, requiring careful description reading to select correctly.
The overwhelming majority follow a verb_noun snake_case pattern like get_campaigns, create_adset, search_interests, and update_product_set. Minor inconsistencies exist, such as list_custom_audiences where list_ is used instead of get_, and a few longer composite names, but no mixed naming styles or chaotic conventions appear.
With 57 tools, the surface is far beyond the 3-15 range that typically indicates a focused, well-scoped server. The count is somewhat justified by the breadth of Meta Ads (campaigns, creatives, targeting, pixels, catalogs, insights), but it still feels heavy and will burden agent selection.
The core campaign/adset/ad lifecycle is well covered with create, read, and update operations, plus solid supporting tools for creatives, targeting, pixels, catalogs, and insights. Notable gaps include no way to delete a single ad or ad set (only entire campaign structures), no custom audience creation/update/delete, and no ad account update or catalog deletion.