← The BriefPlatforms
Meta’s MCP server, explained for marketers
Meta now offers an MCP server for ad accounts. What it does, what AdsOS uses it for, and why AI still never changes your account on its own.
Meta now runs an MCP server for ad accounts: a standard way for software, including AI tools, to read and manage campaigns through a published list of tools. It is in beta, and it changes how AdsOS talks to Meta behind the scenes.
Nothing changes about who is in charge. Here is what MCP does in AdsOS, what still goes through the Graph API, and what happens when something breaks.
What goes through MCP
- Finding the ad accounts you connected, and reading campaigns, ad sets and their statuses.
- Reconciling what is live with what AdsOS expects.
- Creating, updating and activating campaigns, only after a person approved the change.
What stays on the Graph API
Image uploads, creatives, targeting search, insights sync, webhooks and data deletion still use Meta’s Graph API, which also answers anything MCP cannot. If your connection was made before MCP access existed, AdsOS keeps using Graph and asks you to reconnect to enable Meta MCP.
When something fails
- Reads A failed read falls back to the Graph API, so your reports keep loading.
- Creates A create is never sent twice. If the outcome is unclear, AdsOS reconciles it against your account first.
- Drift When Meta changes a tool’s arguments, AdsOS records it for review instead of guessing.
“AI reads Meta through a fixed, read-only list of tools. Writing always waits for a person.”
How AdsOS handles AI access
Both routes share the same rate windows, cooldowns and redacted request logs. For you, most of this is invisible: you still approve every change, and the activity log still shows who approved it.
Sources
AdsOS Team
The people building AdsOS: product, engineering and the specialists who help teams launch their first approved campaigns.
