Meta Ads MCP server, with a policy gate.
Connect the official Meta-hosted Ads MCP server to every agent through Gentkey, with your user access token encrypted server-side and each mutation family behind its own explicit, revocable grant.
https://app.gentkey.com/mcpclaude.ai (web & mobile) · Claude Code · Cursor · any MCP clientWhat’s free, what needs a grant.
Reads: Gentkey curates 55 tools from Meta's official documentation as reads: reporting, account and asset discovery, catalog and dataset diagnostics, experiment results, help, and activity logs.
Writes: Thirty-six documented mutations map to seven resource-family grants. Activating or changing campaign delivery, uploading audience members, catalog changes, pixel rules, and experiments remain independently revocable and rate-limitable; new Meta tools fail closed to the full-write grant.
Gentkey proxies the official Meta Ads MCP server (https://mcp.facebook.com/ads) — you get the vendor’s own tools, with custody, gating, and audit added in front.
| Grant | What it governs |
|---|---|
mcp-meta-ads.campaigns.write | Campaign, ad-set, and ad creation or updates — including activation, budgets, and status |
mcp-meta-ads.creatives.write | Creating ad creatives |
mcp-meta-ads.instagram.write | Boosting an organic Instagram post as an ad |
mcp-meta-ads.audiences.write | Creating, populating, changing, and permanently deleting custom audiences |
mcp-meta-ads.catalogs.write | Catalogs, products, product sets, feeds, rules, and event-source connections |
mcp-meta-ads.signals.write | Pixel event rules and parameter extractors |
mcp-meta-ads.experiments.write | A/B tests and conversion-lift studies |
mcp-meta-ads.write | Anything not yet curated, including tools Meta adds later |
Bounds the gate enforces with arithmetic.
mcp-meta-ads.campaigns.write · max writes/hour = 10An agent can make up to ten campaign-delivery changes in the rolling hour; the next attempt is denied before it reaches Meta and recorded in the audit log.
Connect once, use everywhere.
Sign in at gentkey.com, add Meta Ads (api key), then point each client at your endpoint. Every client completes a standard OAuth flow and lands in your Gentkey — your connections, nobody else’s.
claude.ai (web & mobile)
- Settings → Connectors
- Add custom connector
- Paste
https://app.gentkey.com/mcpand finish the OAuth prompt
Claude Code
claude mcp add --transport http \
gentkey https://app.gentkey.com/mcpCursor
// .cursor/mcp.json
{
"mcpServers": {
"gentkey": { "url": "https://app.gentkey.com/mcp" }
}
}Things agents do with Meta Ads here.
- Which campaigns lost the most ROAS over the last seven days?
- Show delivery-blocking errors and signal-quality issues for this account.
- Create a paused campaign and ad set for the fall launch.
- Pause the three ad sets with the highest cost per result.
- Check whether my product catalog is healthy enough for Advantage+ catalog ads.
Custody, gating, and audit — built in.
The model never sees a credential
Your Meta Ads key is encrypted at rest and injected server-side at call time. Your stored credential never enters a context window.
Writes need a grant
Anything that changes state needs a capability you granted explicitly — revoke it and the next call is denied.
A trail you can act on
Every decision is attributed to the agent that made it — allowed, denied, or denied by constraint.
Fair questions.
Does Gentkey proxy Meta's official server?
Yes. Tool discovery and calls go to https://mcp.facebook.com/ads. You paste a Meta user access token, Gentkey proves it against that server before storage, then keeps it encrypted and injects it only into upstream requests. Gentkey needs no Meta App ID or App Secret.
Can a reporting agent activate campaigns?
Not without mcp-meta-ads.campaigns.write. The 55 documented reads work independently, while campaign creation, budget/status updates, and activation share an explicit rate-limitable grant that can be revoked immediately.
What happens when an agent calls a Meta Ads write tool it hasn't been granted?
The call is denied at the gateway — nothing reaches Meta Ads — and the denial is recorded in the audit log along with the grant that would have authorized it, so you can decide deliberately instead of finding out later.
Where are my credentials stored?
Encrypted at rest (AES-256-GCM) on Gentkey's server and injected server-side at call time. No credential you store with Gentkey ever enters a model's context window or an agent's config file.
Can I use this from claude.ai's free plan?
Yes — and it's the strongest case for a gateway: free claude.ai accounts currently get a single custom connector, so pointing that one slot at Gentkey puts every connector you've linked behind it.
How do I revoke an agent's access?
Revoke the grant (the next write is denied) or revoke the agent's tokens entirely in one click. Other agents and their grants are untouched — no shared key to rotate.
Is Gentkey affiliated with Meta Ads?
No. Gentkey is an independent MCP gateway. Trademarks belong to their owners; where an official Meta Ads MCP server exists, Gentkey proxies it and adds custody, gating, and audit on top.
Often connected together.
Cut Meta Ads a smaller key.
Sign in, connect Meta Ads, and grant your first scoped capability in under a minute.