On April 29, 2026, Meta launched the official Meta Ads AI Connector — its own MCP server that any advertiser can paste into Claude, ChatGPT, or Perplexity. Sign in once with your Meta account; the connector handles everything else. No developer credentials, no token generation, no Business Verification waiting room.
If your only ad platform is Meta, use the official connector. It's the fastest, deepest path, and it's free.
This post covers (1) how to set up Meta's official connector, (2) what it does, and (3) when StackPicks Connect's unified gateway makes sense instead.
Option A — Meta's official Ads AI Connector (recommended for Meta-only)
Setup (60 seconds):
- In Claude → Settings → Connectors → Add custom connector.
- Paste:
```
https://mcp.facebook.com/ads
```
- Sign in with the Meta account that has access to your ad account.
- Done.
Now ask Claude: *"List my Meta ad accounts and show last 7 days spend by campaign."*
What you get — 29 tools across 4 categories:
| Category | Capabilities |
|---|---|
| Reporting | Account / campaign / ad-set / ad-level insights, custom date ranges, breakdowns by device/placement/region, comparison reports |
| Campaign management | Create / pause / edit campaigns, change budgets, modify targeting, schedule changes |
| Catalog management | Product feeds for Advantage+ catalog ads, catalog diagnostics, feed health |
| Signal diagnostics | Meta Pixel + Conversions API troubleshooting, event match quality, attribution debugging |
That's a full Meta Ads workflow available conversationally inside Claude. As of June 2026 it supports Claude, ChatGPT, and Perplexity, with more clients to be added.
Official launch post: Meta for Business — Introducing Meta Ads AI Connectors.
Option B — StackPicks Connect (recommended if Meta isn't your only platform)
Meta's official connector is great, but it only covers Meta. If you actually want a single AI prompt to do something like this:
> *"Compare last 7 days spend across Google Ads and Meta Ads, flag any campaign where CPC jumped over 25%, then post a summary to my #marketing Slack and create a Linear issue for the worst performer."*
…you need a **unified gateway** — one connection URL that exposes tools from many platforms at once. That's StackPicks Connect.
StackPicks Connect today wires 22 providers behind a single MCP URL: Meta Ads + Google Ads + GitHub, Slack, Notion, Linear, Calendly, Figma, Vercel, Supabase, Cloudflare, Sentry, plus search providers (Tavily, Exa, Perplexity, Brave) and more. Add Meta's official MCP alongside StackPicks in Claude — they don't conflict. Claude picks the right tool per request:
- Deep Meta Ads work (create campaign, edit budgets, debug Pixel) → routes to Meta's 29 tools
- Cross-platform questions ("show me Meta + Google last week") → routes through StackPicks' read-only ad tools
- Anything non-ads (GitHub PR, Slack post, Linear issue) → StackPicks
Setup StackPicks Connect for Meta Ads in 60 seconds (uses the same simple flow):
- Sign up at stackpicks.dev.
- Click the Meta Ads card → follow the connect flow.
- In Claude, add
https://stackpicks.dev/api/mcpas a custom connector → sign in with StackPicks → approve.
Once connected, every other StackPicks-connected app is available too. One URL, full stack.
Which one to pick — the honest decision tree
| Your situation | Use |
|---|---|
| You only run Meta Ads. No Google Ads, no other tools you want Claude to touch. | Meta's official connector. Done in 60 seconds, 29 tools deep, no waiting. |
| You run Meta Ads + Google Ads but everything else stays in dashboards. | Both, side by side. Add mcp.facebook.com/ads for Meta depth, add stackpicks.dev/api/mcp for Google Ads (BYO-token mode, also live). |
| You want Claude to do cross-platform workflows. Ad ops + GitHub + Slack + Linear + Notion in one prompt. | StackPicks Connect as your primary, optionally with Meta's official for deeper Meta-specific work. |
There's no wrong answer. We built StackPicks Connect because we kept hitting the "one URL for all my tools" problem ourselves — but if Meta's free official connector solves your case end-to-end, use it.
Security model — both paths
Meta's official connector:
- Authentication via Meta sign-in (the same flow you use on facebook.com / business.facebook.com).
- Tokens are managed by Meta — never leave Meta's infrastructure.
- Revoke any time at Business Settings → Apps → Meta Ads AI Connector → Remove.
StackPicks Connect (BYO-token path for Meta Ads):
- You supply a Meta System User Access Token from your own Business Manager.
- Token stored encrypted (AES-256-GCM) in StackPicks' Postgres with Row-Level Security.
- Audit log: every call recorded with user_id, tool, timestamp.
- Revoke from Meta Business Manager (instant) OR /dashboard/connections (instant).
Common pitfalls
- "Where do I find mcp.facebook.com/ads in Claude?" — Settings → Connectors → "Add custom connector" → paste the URL. Same place you'd add any other MCP server.
- Sign-in opens but never returns — pop-up blocked. Allow pop-ups for claude.ai (or chatgpt.com / perplexity.ai) and retry.
- "This connector isn't supported by your client" — your client doesn't support remote MCP servers yet. Update Claude/ChatGPT/Perplexity to the latest version.
Related reading
- Connect Google Ads to Claude via MCP — the BYO-token setup (Google has no official MCP yet)
- ChatGPT Ads Explained — the new third ad channel
- One MCP for All Your Apps — the unified-gateway model