When Meta shipped an official MCP server for Meta Ads earlier this year, the announcement posts mostly said "Claude can now manage your Facebook ads." That is true and also not very useful to an engineer deciding whether to build on it. I wanted the boring answers: what tools, what auth, what rate limits, what it refuses to do, and where you still need your own code.
I have not reverse-engineered the server. What follows is assembled from two write-ups Ryze published on the launch (the second is a tool-by-tool breakdown), with the places where they disagree called out, because they do disagree on a couple of details and you should check Meta's own documentation before you depend on either. Every number is cited to the page it came from.
The shape of the thing
Per Ryze's breakdown, Meta's server was released in public beta on 29 April 2026 and exposed 29 core tools at launch, grouped roughly into campaign management, performance insights, audience tools and creative management (source: https://www.get-ryze.ai/blog/meta-official-mcp-what-it-does-and-how-to-install). The same page maps those categories onto the Marketing API endpoints the server calls behind them:
| Tool category | Example functions | Endpoints called |
|---|---|---|
| Campaign management | create, edit, pause, delete |
/campaigns, /adsets, /ads
|
| Performance insights | pull metrics, compare periods |
/insights, /delivery_check
|
| Audience tools | lookalikes, custom audiences |
/customaudiences, /saved_audiences
|
| Creative management | upload images, manage library |
/adcreatives, /adimages
|
(Table from https://www.get-ryze.ai/blog/meta-official-mcp-what-it-does-and-how-to-install.)
The important architectural point is that the AI client never touches the Marketing API directly. The MCP server receives a tool call, constructs the Graph API request, executes it and returns a formatted response. Your Claude or ChatGPT session holds no Meta token.
Meta ships this in two flavors, and the Ryze launch post is clear about who each is for: an HTTP MCP server you point Claude Desktop or ChatGPT at, and a CLI binary for Claude Code and Codex users. Same Marketing API underneath; the launch post estimates about 10 minutes for the MCP route and about 15 minutes for the CLI route (npm install, env vars, auth) (source: https://www.get-ryze.ai/blog/meta-ads-official-mcp-cli-launch).
Auth: this is the real feature
The thing that changes the economics is not the tool list; it is that you do not need a Meta Developer App. Authentication is Meta Business OAuth, the same login flow Shopify and Mailchimp use. The launch post's framing: no Developer App, no Marketing API approval wait, querying live campaigns within minutes instead of the old 1 to 3 day wait (source: https://www.get-ryze.ai/blog/meta-ads-official-mcp-cli-launch).
Per the breakdown page, the OAuth screen asks for permissions covering campaigns, ad sets, ads, insights, audiences and catalogs; the token is stored server-side by Meta and refreshed automatically. If auth succeeds but data calls fail with "insufficient permissions", the fix it gives is re-authenticating with all requested scopes granted (ads_read, ads_management, business_management, pages_read_engagement) and confirming your Business role is Admin or Advertiser, not Analyst (source: https://www.get-ryze.ai/blog/meta-official-mcp-what-it-does-and-how-to-install).
Where the two write-ups disagree
Read both pages side by side and you hit three inconsistencies. I am listing them rather than picking a winner, because I could only verify what the pages say, not what Meta's server does today.
-
Endpoint. The launch post's Claude Desktop config uses
https://mcp.meta.com/ads/<your-business-id>undermcpServers(source: https://www.get-ryze.ai/blog/meta-ads-official-mcp-cli-launch). The breakdown page says the server is hosted atmcp.ads.meta.comand shows annpx -y @meta/ads-mcpstdio config with emptyMETA_ACCESS_TOKEN,META_APP_IDandMETA_APP_SECRETenv vars (source: https://www.get-ryze.ai/blog/meta-official-mcp-what-it-does-and-how-to-install). A remote URL and a local npx package are different transports. Check Meta's setup docs, which the launch post cites at facebook.com/business/help/1456422242197840. -
Setup time. 10 minutes on the launch post, "under 5 minutes" on the breakdown page. Both put most of the time in finding
claude_desktop_config.json. - Which Claude. The breakdown page says MCP requires Claude Desktop and a Pro subscription, and that the web version does not support MCP servers. That was written in May 2026; treat it as a dated claim and test against the client you actually use.
The config edit itself is the step that bites. The launch post's troubleshooting is practical: a red indicator almost always means a JSON syntax error (trailing comma, missing brace); closing the Claude window is not quitting, you need a full Cmd-Q and reopen; and if the first prompt errors it is read access, not the prompt (source: https://www.get-ryze.ai/blog/meta-ads-official-mcp-cli-launch).
What it does
Once connected, the capability that matters most versus the third-party servers that came before is write access, including campaign creation. The breakdown page's claim: full read/write access to the Marketing API, with everything created in PAUSED status by default so you review before launch (source: https://www.get-ryze.ai/blog/meta-official-mcp-what-it-does-and-how-to-install). The example prompts it lists give a feel for the surface:
- Pull campaigns with spend over $1,000 this month, CTR under 1% and CPA over $50.
- Create a conversion campaign with a $200 daily budget, CBO on, three ad sets, in PAUSED status.
- Build a 1% lookalike from top-20% purchasers in the last 90 days and check overlap against existing audiences.
- Pause campaigns with ROAS under 2.0x and raise budgets 20% on campaigns above 4.0x, showing the plan before executing.
- Flag ads with CTR down more than 30% over 7 days, frequency over 3.0, or CPM up more than 40%.
Those are prompts, not tool names; the model composes them from the 29 tools.
What it doesn't do
No agent layer. The server exposes operations. It does not run them on a schedule, watch for fatigue, or pause anything on its own. The launch post states this directly: Meta's official MCP tells you ad sets are fatigued, it does not pause them (source: https://www.get-ryze.ai/blog/meta-ads-official-mcp-cli-launch). If you want overnight automation you wire your own cron job, alerting and pause logic on top, or you use a hosted product that does. Ryze is one of those and publishes its own comparison on the launch page; I work with them, so read that comparison knowing they sell the alternative.
No multi-account auto-discovery and no per-client token isolation. Both pages describe account switching as manual and the launch post calls the lack of token isolation "a hard fail for regulated agency work" (source: https://www.get-ryze.ai/blog/meta-ads-official-mcp-cli-launch). If you manage many Business Managers, that is your integration work.
Not everyone is enabled. The breakdown page says access is gated by an is_ads_mcp_enabled flag on the Business account and that roughly 40% of accounts still showed false as of May 2026, with Meta prioritizing high-spend accounts and typical wait times of 2 to 4 weeks (source: https://www.get-ryze.ai/blog/meta-official-mcp-what-it-does-and-how-to-install). The symptom is an install that looks fine followed by an "Account not enabled for MCP access" error at auth. Check the flag before you debug your config.
Personal accounts are out. A Facebook Business account with Admin or Advertiser access is required, regardless of personal ad-spend history (same source).
Rate limits are the Marketing API's. The breakdown page quotes 200 calls per user per hour and 4,800 per app per hour, enforced at the MCP server, with the server batching and caching repeat requests. The practical advice is to batch questions into single prompts and wait 15 to 20 minutes if you trip the limit (source: https://www.get-ryze.ai/blog/meta-official-mcp-what-it-does-and-how-to-install). If you are building anything that polls, budget for this.
Pricing is open-beta pricing. Free today, but the launch post notes Meta has not committed to long-term pricing and the free tag is beta-specific (source: https://www.get-ryze.ai/blog/meta-ads-official-mcp-cli-launch). The breakdown page adds that the third-party servers it replaced charged $25 to $99 a month, which is a useful anchor for what a post-beta price might look like.
A decision rule
The launch post's two-persona split is roughly right. If you are a developer with one or two accounts, comfortable editing JSON, and you will wire your own automation, the official server is free raw Marketing API access with an OAuth flow that finally skips app review. Use it. If you need scheduled actions, many Business Managers, or token isolation per client, the official server is the data layer and you are building (or buying) the rest.
Either way, do the first week read-only. Confirm Claude's tables match Ads Manager for the same date range and attribution window before any tool call with pause or budget in it runs unattended.
Top comments (0)