Meta Ads MCP serverMeta Ads MCP Server for any AI client.
NotFair connects your Meta Ads account to Claude, Codex, Cursor, and any MCP client — 35 tools to inspect campaigns, find issues, and stage approved changes.
No credit card required · Read live data, approve every write
MCP endpoint
https://notfair.co/api/mcp/meta_adsLive tools
35New to MCP? Read the spec at modelcontextprotocol.io.
Tools exposed
35What your AI client can read and change
Read tools provide live ad-account context. Write tools propose changes — every write requires explicit human approval before it hits the Meta Marketing API.
| Tool | Type | What it does |
|---|---|---|
runScript | Read | Sandboxed JS with Graph API fan-out — fan out 20 calls in one pass for audits and analysis. |
getInsights | Read | Performance insights with breakdowns: spend, impressions, clicks, CTR, CPC, CPM, conversions. |
listCampaigns | Read | List campaigns with status, objective, budget, bid strategy, and schedule. |
listAdSets | Read | Ad set details: optimization goal, billing event, daily/lifetime budget, targeting summary. |
listAds | Read | Ads with status, parent ad set/campaign, creative envelope, configured status. |
getAdAccount | Read | Account snapshot: currency, timezone, balance, amount spent, spend cap, parent BM. |
| and more | ||
Ready to wire up your client?
Sign in to NotFair, link your Meta ad accounts, then paste a config above into your MCP client.
FAQ — NotFair Meta MCP server
Common questions about authenticating, configuring, and using the NotFair Meta Ads MCP server.
It's a hosted Model Context Protocol server that exposes your Meta ad accounts (Facebook + Instagram) to MCP-compatible AI clients. Read tools provide live campaign context for diagnosis; write tools propose fixes that you approve in chat.
Any client that speaks the MCP Streamable HTTP transport — Claude.ai (Web, Desktop, Cowork), Claude Code, OpenAI Codex CLI, Hermes Agent, OpenClaw, Cursor, Cline, and custom MCP clients. The server URL is the same; only the client-side config differs.
No. The Meta Ads MCP server is hosted at https://notfair.co/api/mcp/meta_ads. You just point your client at it and authenticate.
OAuth 2.0 with PKCE is the recommended flow — Claude.ai and Codex run it automatically. For clients that don't support OAuth, you can use a Bearer token via the Authorization header. Generate either at notfair.co/connect/meta-ads.
Yes. Connecting to NotFair's Meta MCP is free with no credit card. Paid plans unlock higher usage limits and team features.
Only with your explicit approval. Write tools propose changes (pause campaigns, adjust budgets, rename entities, etc.), the client surfaces them, and you confirm before anything hits the Meta Marketing API. Read access is unrestricted; write access is gated.
Yes. Meta Ads covers both Facebook and Instagram inventory under a single ad account. The MCP exposes everything Meta surfaces through the Marketing API: campaigns, ad sets, ads, creative, audiences, insights, and the parent Business Manager.
Per-client setup guides
Walkthroughs for each supported client.
Claude × Meta Ads
Set up the NotFair Meta Ads MCP in Claude.
Read setup guideClaude Code × Meta Ads
Set up the NotFair Meta Ads MCP in Claude Code.
Read setup guideCodex × Meta Ads
Set up the NotFair Meta Ads MCP in Codex.
Read setup guideCursor × Meta Ads
Set up the NotFair Meta Ads MCP in Cursor.
Read setup guideOpenClaw × Meta Ads
Set up the NotFair Meta Ads MCP in OpenClaw.
Read setup guideHermes × Meta Ads
Set up the NotFair Meta Ads MCP in Hermes.
Read setup guide