Is the Meta Ads MCP official, and how many tools does it actually expose?

Official and Meta-hosted at mcp.facebook.com/ads, launched in open beta April 29, 2026. The widely cited figure of 29 tools is the April launch snapshot and is stale: Meta's own documentation, updated mid-July 2026, enumerates roughly 91 unique tools across seven first-party categories — 28 for ad creation and management, 34 for catalogs, 13 for signals and datasets, 7 for reporting, 7 for A/B tests and lift studies, plus help and activity-log tools. Any comparison still built on '29 tools' undersells the current surface by a factor of three.

Can an AI agent connected to Meta's MCP spend my budget?

Not silently, per the documented design — Meta layered three guardrails. Write tools create entities in a paused state, and a separate explicit tool (ads_activate_entity) is what flips them live and starts spending. The AI client is expected to ask for confirmation before activation. And since July 16, 2026, portfolio admins can set server-enforced 'ads MCP server rules' in Business Suite: block specific actions like campaign creation or budget edits per ad account, or set a budget ceiling above which requests are refused. TikTok's official server documents none of these layers — no paused-by-default, no server-side rules, no read-only mode.

Do I need a developer app to connect Claude or ChatGPT to either platform's ads MCP?

No on both standard paths. Meta explicitly states owning a Meta app is not a prerequisite: you add the remote server URL and sign in through the Facebook Login for Business dialog, with a developer-app route available as an optional second path since July 16 (agencies managing others' data need app review there). TikTok likewise requires only a TikTok for Business login — no developer account or API key. The exception is Meta's companion Ads CLI, which does require a developer app plus a system-user token; several guides conflate the two.

What about the read-only / read-write / financial permission tiers everyone mentions for Meta?

Treat that as reported, not documented. The three tier names circulate across third-party guides but appear on zero first-party Meta pages — the developer docs instead list seven Graph-style permissions (ads_read, ads_management, catalog_management and so on) for the token path, and the tier picker, if it exists as described, lives only inside the OAuth consent dialog. If your security review needs the exact grant semantics, complete a live consent flow and screenshot what it offers; do not cite the tier names from blog posts, ours included.

Meta vs TikTok Ads MCP: The Verified Comparison

Within eleven weeks in 2026, the two ad platforms where short-form creative actually converts both shipped official MCP servers — Meta on April 29, TikTok announced May 13 and live by early July. An AI agent can now hold a conversation that ends with a live campaign on either platform.

The comparisons you will find ranking for this topic are systematically wrong on both sides, and for the same mechanical reason: both platforms document their servers behind JavaScript-rendered pages that return nothing to plain fetchers. Writers quote each other instead, so Meta is still described by its April launch snapshot and TikTok by its May announcement. We rendered both documentation sets in a real browser, probed TikTok's endpoints directly, and had the numbers re-verified by an independent pass. Here is what is actually true in August 2026.

The two corrections that reframe the comparison

Meta does not have 29 tools. That figure was true at launch and is cited everywhere. Meta's own docs, updated July 14–24, enumerate roughly 91 unique tools across seven categories: ad creation and management (28), catalog management (34 — by far the deepest catalog surface on any ads MCP), signals and datasets (13), reporting (7), A/B tests and conversion-lift studies (7), help search (2), activity logs (1).

TikTok's server is not "an announcement." Guides written in June still say there is no product. The endpoints have been live since around July 3 — we probed both and got the auth challenge a live service returns — exposing ~400 tools flat or ~40 with progressive disclosure. Our TikTok-side working guide has the full detail.

Side by side, verified

	Meta Ads MCP	TikTok Ads MCP
Endpoint	`mcp.facebook.com/ads`	`business-api.tiktok.com/open_mcp/` (flat or layer)
Tools	~91, 7 curated categories	~400 flat / ~40 progressive
Developer app needed	No (optional path since Jul 16)	No
Auth	Facebook Login for Business OAuth	TikTok for Business OAuth
Re-auth cadence	Undocumented	30 days, documented
Spend guardrails	Paused-by-default writes + explicit activation tool + server-side rules with budget ceilings	None documented
Read-only option	Not first-party documented (see below)	None documented
Sandbox	Not documented	Not documented
Rate limits	Not documented for MCP	3 QPS per tool, documented
First-party client list	ChatGPT, Claude, Claude Code, Perplexity	Client-agnostic
Companion	Ads CLI (Python, needs dev app + system-user token)	Agentic Hub skill marketplace

Both rollouts are staged — Meta's Help Center opens with "you may not have access to all tools/features yet," and TikTok notes tool availability varies by region and account. A feature not appearing on your account is not evidence it doesn't exist.

The guardrail gap is the actual decision

Strip the tool counts away and one difference decides which server you let touch a real account. Meta shipped a safety architecture: write tools create entities paused; a separate, explicit tool is what starts spend; and since July 16 a portfolio admin can set server-enforced rules — block campaign creation, block budget edits, or cap budgets so any request above the ceiling is refused, per ad account and per catalog. TikTok shipped power without documented restraint: budget and payment tools sit in the same all-or-nothing grant as reporting, with no paused-default, no server rules, and no read-only mode documented. If you run client accounts, that asymmetry, not the tool count, is the comparison.

One myth to retire while we are here: the "read-only / read-write / read-write-financial" permission tiers that every Meta MCP guide repeats appear on zero first-party pages. The developer docs list seven Graph-style permissions instead, and the tier picker — if it exists as described — lives only in the OAuth consent dialog. Reported, not documented. Verify it in a live consent flow before your security review cites it.

The rest of the field, for context

The write-capable pair really is Meta and TikTok. Google's official Ads MCP is open-source, three tools, and by its own doc text "strictly read-only. It cannot modify bids, pause campaigns, or create new assets" — first published October 7, 2025. Microsoft's is a read-only pilot from June 2026 per trade coverage, and an Amazon open beta is reported from February. Every platform agreed agents should read; only Meta and TikTok let them act.

What neither server provides

Campaigns, budgets, audiences, catalogs, reports — everything after the creative exists. Neither MCP makes the video, and on TikTok's side the platform's own in-hub answer produces TikTok-locked, labeled, stock-avatar output.

That half is Riffkit, and it is agent-native by design: a skill your agent invokes with a winning short video, returning your product's version of it — rebuilt formula, your locked character if you want one, a file you own — which the same agent can then upload and launch through either MCP above. The skill page has the one-line install; pricing shows the per-second rate before anything renders. The agents got their hands this summer. They still need ammunition.