Meta Ads MCP

Meta Ads MCP Server

An MCP server for Meta Ads: read campaigns, build ad sets, upload creatives, and pull performance from the chat you already work in.

MCP Ads exposes your Meta Ads account to any client that speaks the Model Context Protocol. You sign in through the browser once, and the assistant can then read and change the account directly — no API key to paste, no export step, no Ads Manager tab.

230

tools on this platform

3,120

tools in total

Browser

sign-in, no API keys

What a call looks like

These are real tool names from the live server, with the shape of what they return.

YouWhich Meta campaigns spent the most last week and what did they return?

Toolmeta_ads_campaign_performance

{
  "campaigns": [
    { "name": "Retargeting - 30d",  "spend": 4820.11, "purchases": 96, "roas": 3.71 },
    { "name": "Prospecting - Broad", "spend": 3915.60, "purchases": 41, "roas": 1.88 }
  ],
  "date_range": "2026-08-11 to 2026-08-17"
}

YouList the ad accounts I can reach.

Toolmeta_ads_list_ad_accounts

{
  "accounts": [
    { "id": "act_1029384756", "name": "Main Brand",  "currency": "USD", "status": "ACTIVE" },
    { "id": "act_5647382910", "name": "EU Storefront", "currency": "EUR", "status": "ACTIVE" }
  ]
}

YouIs anything under-delivering right now?

Toolmeta_ads_delivery_insights

{
  "ad_sets": [
    { "name": "Lookalike 1% - US", "issue": "LEARNING_LIMITED", "conversions_7d": 11,
      "note": "Under 50 conversions in 7 days keeps this ad set in the learning phase." }
  ]
}

What the Meta Ads MCP server can do

The read side covers everything Ads Manager shows you, and the write side covers the changes people actually make between reports.

Campaigns, ad sets, and ads — list, inspect, create, pause, and update
Creatives — upload images and video, build creatives, swap the asset on a live ad
Audiences — custom, lookalike, and saved audiences, plus customer list uploads
Lead ads — retrieve leads and the forms behind them
Reporting — spend, ROAS, delivery, placement and demographic breakdowns

How it connects

Authorisation is a browser sign-in with Meta, the same flow you already use for Business Manager. Tokens are stored encrypted on our side; your AI client only ever holds the MCP connector URL. Several Meta logins can be connected at once, and each write goes back through the login that owns that account.

Which clients it works with

Anything that supports MCP: Claude and Claude Code, ChatGPT, Cursor, Windsurf, Codex, Gemini CLI. One connector URL covers all of them, and the tools behave identically in each.

Questions

Do I need a Meta developer app or API key?

No. You authorise through Meta in the browser and MCP Ads holds the token. There is nothing to create in developers.facebook.com and no key to paste into your AI client.

Can it change my live campaigns, or only read them?

Both. Write tools are separated from read tools and are blocked for viewer-role users, so you can give someone reporting access without giving them the ability to change spend.

What happens with multiple ad accounts or multiple Meta logins?

Both are supported. Every ad account is mapped to the connection that owns it, so a write is always sent with the token that actually has permission on that account.

Competitor Ads

Competitor Ad Research in Claude

Ask what a competitor is running and get their live ads back - from Google's Ads Transparency Center and Meta's Ad Library, in the same chat you plan campaigns in.

Ad Library

Facebook Ad Library in Claude

Meta's Ad Library, as tools your assistant can call - find a page, list what it is running, and read the angles out of the creative.

Ads Transparency

Google Ads Transparency Center in Claude

Google's public ad archive, as tools your assistant can call - search any advertiser, in almost any country, with nothing to connect.