Key takeaways
The official Facebook Ads MCP lives at mcp.facebook.com/ads, Meta-hosted and live since April 29, 2026. You connect over OAuth in minutes. Two catches. The beta is account-gated, so "connect it" can mean "get into the beta first." And it hands an agent write access to live ad spend.
Where the official Facebook Ads MCP server lives, and how to reach it
If you searched facebook ads mcp to find the server, here is the address: mcp.facebook.com/ads. It is Meta's official, Meta-hosted endpoint, one of its ads AI connectors, and it works with any MCP-compatible agent.
To connect, paste that URL into your AI tool's MCP settings and authorize through Meta's OAuth flow. There is no developer app to build and no Marketing API code to write. For an account already enabled for the beta, the whole thing runs about 15 minutes.
One honest caveat before you get excited. Reaching the URL is not the same as having access. The server is an open beta gated at the account level, so "connect it" can really mean "get your account into the beta first." If your account is not enabled, the wait is the gating, not the setup.
Official Meta server vs the community options at a glance
Reaching the server is the easy part. Choosing which one to point your agent at is the decision, and here is the split that settles it.
| Official Meta server | Pipeboard (community) | |
|---|---|---|
| Access | Gated open beta | Hosted remote, available now, free plan |
| Read vs write | Read and write, in beta | Read and write, end to end |
| Platforms | Meta only | Meta, Google, TikTok, Snap, Reddit |
| Hosting and auth | First-party, Meta-hosted, Meta OAuth | Independent open-source on Meta's public APIs; badged Meta Business Partner |
| Safety default | Yours to enforce, no protocol guarantee | Yours to enforce, no protocol guarantee |
Pipeboard is the clearest community example. It runs Meta Ads end to end from a hosted remote server, with no developer token and no self-hosting, and it reaches Google, TikTok, Snap, and Reddit from the same login. The project is open-source, so you can read the code on GitHub, where it carries roughly 1,090 stars.
The safety row reads the same on both sides for a reason. No server makes the paused-by-default promise for you, so the honest cell is that spend safety is yours to enforce either way. Ignore any "best overall" badge a community server hangs on itself. A self-awarded verdict is marketing, not proof, and the only thing worth judging is whether the server does the writes you actually need. If you go hunting on Reddit, expect r/facebookads and similar threads full of reactions and setup gripes. Read them for the gotchas, not the spec, and confirm anything you find against Meta's own docs.
What you're actually handing an agent
Connecting the server is quick. Understanding the grant takes a minute longer, and it is the part worth slowing down for.
The official server groups its tools into about seven categories. Reporting is the harmless one. The rest are not. Ad creation and management lets an agent create and edit ads, ad sets, and campaigns. Catalog management lets it create catalogs and change product data. Counting the underlying Marketing API tools, that's roughly 29 of them, reachable over OAuth 2.0 with no developer app. Treat that as approximate, not a hard spec.
That is capability, not a feature list. You are giving software the power to spin up a campaign and point it at a live budget. That is a write grant against real money. It is the thing to reason about before you paste the URL, not after. This is also why an autonomous agent on a live ad account is a different animal from one that only reads reports.
Connecting from Claude, ChatGPT, and Cursor
The protocol is client-agnostic, so any MCP-compatible assistant can talk to the server. In practice, the Meta Ads MCP experience is best in Claude and ChatGPT today. Cursor support is less consistent and shifts from release to release, so treat it as current-as-of, not a promise. For a tool with no MCP interface at all, Meta also ships an Ads CLI, which gives you a scripted path to the same account.
If you are wiring this into Claude specifically, the flow is the same as adding any hosted MCP: add the server in your MCP settings, run the OAuth flow, then confirm the connection with a read call before you let it touch anything live.
Which server to pick, by who you are
There is no single right server. There is the right one for your situation.
Pick the official Meta server if you run Meta and only Meta, and your account is already in the beta. You get a first-party, Meta-hosted connection with direct Meta OAuth, and no third party sits between your agent and your ad account. Do not pick it if you need cross-platform reach or your account is not enabled yet, because Meta-only and gated is exactly what it is. Some in the ecosystem also frame the official server as leaning read-first, so if reliable writes and bulk edits are the point, weigh that before you commit.
Pick a community, cross-platform server like Pipeboard if you run Meta alongside Google, TikTok, Snap, or Reddit, or you want one login across all of them. Pipeboard is an independent open-source project on Meta's public APIs, not Meta's first-party server, and it is a badged Meta Business Partner. Do not pick it expecting Meta's official stamp, and do not take any "best overall" self-verdict as independent proof. Judge it on whether it does the writes you actually need.
Paused by default: the pattern that keeps live spend reversible
Here is the operating rule I would keep no matter which server you choose. The agent holds a write grant to live budgets, so nothing it drafts should go live on its own.
The pattern is simple. Have the agent create campaigns in a PAUSED state. A human reviews the targeting, the creative, and the budget, then un-pauses. Spend starts on a person's decision, not a model's.
The important part is where the guarantee comes from. Paused-by-default is not something the protocol enforces. An agent with ad creation and management tools can create and edit live objects directly. So the control is yours to build and yours to keep. Reversible by design means you designed it, not that you hoped for it.
That is the whole harness stance. Legible, steerable, reversible, and nothing irreversible ships without your sign-off.
Where Meta's MCP sits in the wider ad-platform picture
The MCP that actually works today is not a given. As of mid-July 2026, across eleven major ad platforms, seven have launched, piloted, or announced an official Ads MCP. Only four are usable right now without an alpha or waitlist. Just three offer meaningful campaign writes.
Meta sits in the usable-and-writable group. Its server is an open beta with read and write over a Meta-hosted connection and Meta Business OAuth. Google Ads took the opposite path on purpose. Its official MCP is read-only, so an agent can pull reports but cannot move budget. That contrast is the whole safety conversation in one line.
The timeline matters too. Meta shipped its first-party server and CLI on April 29, 2026, joining Google (October 2025) and Amazon (February 2026). Treat every count here as a mid-2026 snapshot. This landscape changes monthly, which is the real reason to build your controls now rather than wait for it to settle.
What this guide can't verify yet
Two honest limits before you wire anything up. I have not run this beta end to end myself, so treat the setup timing and the tool counts as approximate and current-only. Both will move as the beta does. And no community server's paused-by-default safety default has been independently proven out, so read that promise as something to test on a throwaway campaign first, not a guarantee to trust with live budget on day one.
The connection takes minutes. The decision to let an agent spend your money should take longer. Before you grant write access to a live account, read how the harness decides what actually ships, or borrow the pre-connect checklist we run for any high-stakes MCP.