All posts
How-to· 5 min·

Meta Ads MCP Setup — Connect Meta Ads to Claude or ChatGPT (2026 Guide)

Meta's official Ads MCP server (mcp.facebook.com/ads) launched in April 2026 — one URL, sign-in with your Meta account, 29 tools across reporting, campaigns, catalog, and diagnostics. No developer token. No code. 90 seconds.

Quick answer

Meta's official Ads AI Connectors went into open beta in April 2026. To connect: open Claude → Settings → Connectors → Add custom connector → paste https://mcp.facebook.com/ads → sign in with your Meta account. No developer token. No API setup. 29 tools across reporting, campaigns, catalog, and diagnostics. Works identically in ChatGPT and Cursor. Free.

On April 29, 2026, Meta launched Meta Ads AI Connectors — an official MCP (Model Context Protocol) server that lets Claude, ChatGPT, Cursor, and any MCP-compatible AI client manage your Meta ad campaigns through one URL, with a single Meta sign-in.

If you've ever wired up Marketing API access by hand — developer token, app review, Business Verification, OAuth refresh tokens — this is the most welcome thing Meta has shipped for advertisers since detailed targeting got nuked.

What you get

29 tools across 4 categories:

  • Reporting — campaign performance, breakdown by demo / geo / device / placement, account-level metrics, ad-level metrics. Replaces 80% of Looker dashboards.
  • Campaign management — create campaigns, ad sets, ads. Pause / activate. Budget adjustments. Schedule changes.
  • Catalog management — upload products, update inventory, sync to Advantage+ shopping campaigns.
  • Diagnostics — Pixel signal quality, audience overlap warnings, optimisation event readiness.

It works in Claude Desktop, Claude.ai web, ChatGPT (with the Connectors feature), Cursor, Cline, Windsurf, and Perplexity Comet — any MCP 2026-07-28 spec-compliant client. (See our MCP 2.0 explainer for what's new in the latest spec.)

90-second setup

  1. Open Claude → Settings → Connectors → Add custom connector.
  2. Paste https://mcp.facebook.com/ads as the URL.
  3. Claude opens Meta sign-in — log in with the Meta account that has Business Manager access.
  4. Grant the requested permissions.

That's it. The connector activates instantly. No JSON config. No API key in environment variables. No app review wait.

A real example

Once it's wired, this prompt works:

> "Pause every active campaign with ROAS under 1.5x in the last 7 days, then show me what we're spending on the ones still running."

Claude calls 3 MCP tools sequentially:

  1. list_active_campaigns to get the candidate list.
  2. get_campaign_performance with last_7_days, ROAS metric, for each one.
  3. pause_campaign on the ones returning ROAS < 1.5.
  4. get_spend_summary on the survivors.

Replies with a clean table. Total time: ~12 seconds.

What it costs

The MCP server itself is free during open beta. You pay only for:

  • The Meta ad spend you create through it (same as Ads Manager).
  • Your AI client's usage (Claude Pro, ChatGPT Plus, etc.).

There's no per-tool charge or API call fee on the Meta side.

The honest caveats

  • Open beta. Tool surface may change. Treat it as production-stable for reporting / queries; treat it as experimental for high-stakes bulk changes until GA.
  • Permissions follow Meta Business Manager. If your role can't pause a campaign in the UI, the MCP can't either. Use a Business Manager admin token for full access.
  • Per-account scope. You connect one Meta business account per OAuth grant. Agencies managing multiple businesses need to add the connector multiple times with different sign-ins.

Compared to building it yourself

Before this launched, the alternative was:

  1. Apply for Meta App access.
  2. Wait for App Review (1-3 weeks).
  3. Pass Business Verification (1-2 weeks).
  4. Get a developer token (Standard Access usually).
  5. Implement OAuth in your own service.
  6. Mirror the entire Marketing API surface as tool definitions.

Total: 4-8 weeks. Meta did all of this for you and charges $0.

Where StackPicks fits

If you only run Meta Ads, use Meta's MCP directly. It's the fastest, cleanest path.

If you want Meta Ads + Google Ads + GitHub + Slack + Notion + 20 other apps through ONE connector URL, that's where StackPicks Connect earns its keep. We're the unified gateway — one OAuth sign-in per app, one MCP URL into your AI client, every provider on the same dashboard.

For ads specifically, we wire Meta's official MCP through Connect for unified-billing customers, and we offer a Bring-Your-Own-Token (BYO) path for Google Ads via the open-source mcp-google-ads server.

— Piyush

Frequently asked

What is Meta Ads MCP?
Meta Ads MCP is Meta's official Model Context Protocol server, launched April 2026 in open beta. It exposes 29 tools across four categories — reporting, campaign management, catalog management, and diagnostics — letting AI clients like Claude, ChatGPT, Cursor, and Perplexity manage Meta ad campaigns directly. The server is hosted by Meta at mcp.facebook.com/ads. There's also a Meta Ads CLI for terminal workflows.
How do I set up Meta Ads MCP in Claude Desktop?
Open Claude → Settings → Connectors → Add custom connector. Paste https://mcp.facebook.com/ads as the connector URL. Claude opens a Meta sign-in window — log in with the Meta account that has Business Manager access to the ad accounts you want to query. Grant the requested permissions. The connector activates instantly. No JSON config, no API key juggling, no developer token.
Does Meta Ads MCP cost money?
No. The MCP server itself is free during the open beta. You pay only for the Meta Ads spend you create through it — same as if you ran the ads through Ads Manager. There's no per-tool charge, no API call cost, no setup fee. The AI client (Claude, ChatGPT) bills separately for their model usage, but the Meta side is free.
What can I do with Meta Ads MCP that I can't do in Ads Manager?
Bulk operations in natural language. "Pause every campaign with ROAS under 1.5x last 7 days." "Summarise CPC trends across my Top-of-Funnel campaigns weekly." "Create a lookalike audience from purchasers in the last 30 days, then test 3 ad creatives against it." All of these would take 30-90 minutes of Ads Manager clicking. Through Claude with the MCP wired in, they take one prompt.
Is Meta Ads MCP safer than third-party tools like Revealbot?
Yes for two reasons. (1) It's Meta's own server, so it has full access to all current and future APIs without dependency on a third party staying in business. (2) Authorization happens through Meta's own sign-in flow, not through a third-party OAuth proxy or developer token. Your credentials never touch the MCP itself. The risk surface is essentially the same as logging into business.facebook.com.
Can I use Meta Ads MCP and Google Ads MCP at the same time?
Yes — but you need to add each one separately in Claude. The Meta one is mcp.facebook.com/ads. Google's isn't officially hosted yet (as of June 2026), so most builders use the open-source mcp-google-ads server (github.com/cohnen/mcp-google-ads) — that one requires a Google Ads developer token + OAuth refresh token setup, about 20 minutes one-time. Once both are connected, you can run cross-platform queries: "Compare ROAS by channel for last 30 days."

Sources

Stop debugging Meta's API. Start sending.

StackPicks AutoDM ships with Private Reply, follower-aware bodies, account warming, and an AI follow-up agent built in. 90-second setup. No browser bots.

Connect Instagram

More from the blog

Meta Ads MCP Setup — Connect Meta Ads to Claude or ChatGPT (2026 Guide) — StackPicks