MCP server for Meta Marketing API — Facebook & Instagram ad campaign management
MCPpedia last refreshed this data
io.github.mikusnuz/meta-ads is an MCP server that MCP server for Meta Marketing API — Facebook & Instagram ad campaign management. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 88/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"meta-ads": {
"env": {
"META_APP_ID": "your-app-id",
"META_PIXEL_ID": "your-pixel-id",
"META_APP_SECRET": "your-app-secret",
"META_BUSINESS_ID": "your-business-id",
"META_AD_ACCOUNT_ID": "123456789",
"META_ADS_ACCESS_TOKEN": "your-access-token"
},
"args": [
"-y",
"@mikusnuz/meta-ads-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for Meta Marketing API — Facebook & Instagram ad campaign management
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y '@mikusnuz/meta-ads-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @mikusnuz/meta-ads-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in marketing
Free Google Search Console MCP: your real GSC, Google Analytics and keyword data for AI agents.
DataForSEO API modelcontextprotocol server
Newsletters where you pay for the emails you send, not for dormant subscribers, at a fraction of the price of beehiiv and the like. Open source: self-host it, or use mailcheap.ai.
X/Twitter automation MCP: scrape, post, schedule, analyze, engage. No API key required.
MCP Security Weekly
Get CVE alerts and security updates for io.github.mikusnuz/meta-ads and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
MCP server for the Meta Marketing API v26.0 — 134 tools for managing Facebook & Instagram ad campaigns, audiences, creatives, insights, catalogs, and more.
Use this MCP when you need to:
create_campaign, create_adset, create_ad, and create_creative to build a full funnelget_account_insights or get_campaign_insights with today's date rangelist_campaigns + get_campaign_insights to find underperformers, then update_campaign to pausecreate_experiment to run a controlled test between ad setscreate_custom_audience, add_users_to_audience, then create_lookalike_audienceupload_image for each image, then create_creative with carousel formatcreate_async_report for large date ranges, then get_async_report to retrievesearch_ad_library to find public ad datacreate_rule with conditions like CPA > thresholdcreate_catalog, create_feed, and upload_feed to set up dynamic product adscreate_adset accepts bid_amount; creation and updates accept dsa_beneficiary and dsa_payor. For EU-targeted ads, supply each required value or configure the corresponding account default. The payer does not automatically copy the beneficiary.create_adset and update_adset accept destination_type, attribution_spec, adset_schedule, pacing_type, and validate_only. Existing calls still perform their requested writes; set validate_only: true to ask Meta to validate without mutation. A successful validation does not create an ad set.timezone_type as USER or ADVERTISER. Scheduling adds day_parting pacing. Meta validates effective lifetime budgeting, objective eligibility, and attribution restrictions. No budget or status is changed automatically.create_custom_audience accepts a JSON rule, pixel_id, and retention_days for rule-based audiences. Audience creation is a real write, not a dry run.See the official ad-set creation and ad-set update contracts.
events JSON input and send it as the required data array. Use test_event_code to verify receipt in Events Manager; offline events use a dataset ID and action_source=physical_store for store events.destination_spec, wamo_whatsapp_identity_spec, and degrees_of_freedom_spec JSON objects. Dynamic creatives also accept object_story_spec for Page identity. To opt out of the v26 Shops destination default, set destination_spec to {"destination_type":"WEBSITE_AND_SHOP_OPT_OUT"}.