Meta’s official Ads MCP server is at https://mcp.facebook.com/ads. It lets Claude or ChatGPT report on your ads, and it can also create and edit campaigns. If all you do is report, that’s more access than you need. And on a client’s account, you can only restrict your own team, not theirs. SyncWith’s MCP server reads your ads, never changes them, and puts Google Ads, GA4 and Shopify in the same chat.
Meta announced its ads MCP server on April 29, 2026. Reporting is one part of it. According to Meta’s help center, the agent can also create and edit campaigns, ad sets and ads, and create, update or delete custom audiences. New ads start paused until you set them live, and anything it does for you needs your authorization in the AI agent first.
Meta’s answer to that is a set of rules for each ad account. Someone with full control of the business portfolio can block new campaigns, block budget edits, or cap budgets (Meta’s example blocks any budget over $1,000). They set this in Meta Business Suite, under Settings and then Integrations. A partner with access to the account, like your agency, can set rules too, but they apply only to the partner’s own employees. Meta also says the rules are in limited availability, so the client may not see that page at all.
Meta doesn’t say what’s allowed by default. When Jon Loomer checked his own ad accounts in August 2026, every one allowed “7 of 7” actions, from editing budgets to creating campaigns. He also found “there’s still no way to limit access to ad accounts” when you connect: you pick portfolios, not single accounts.
You can keep your own connection read-only. Meta’s MCP docs advise “Keep an app at the Read scope unless an agent needs to make changes,” and you set that in your Facebook account’s Business Integrations settings. But each person on your team has to make that choice and stick to it. Only the portfolio owner can enforce it for everyone, with rules. For reporting, we think read-only should be the only option.
Loomer suggests that if you manage accounts you don’t own, you check that your clients would be okay with it and get their approval before experimenting. We’d say the same for any AI tool, ours included.
Here’s how the two compare if your job is reporting on client accounts.
| Compared on | SyncWith MCP server | Meta’s Ads MCP server |
|---|---|---|
| What it can do in your ad account | Read only. It never changes your ads. | Read and change: campaigns, ad sets, ads, budgets and custom audiences. New ads start paused. |
| Who can block changes | Nobody has to. There’s nothing to block. | Whoever has full control of the business portfolio, per ad account. A partner’s rules cover only its own employees. |
| Sources in one chat | Facebook Ads plus 18 more, including Google Ads, GA4, Shopify and HubSpot | Meta ads |
| You sign in with | Google, then you connect Facebook Ads in SyncWith | Your Meta account |
| Assistants | Claude, ChatGPT, Gemini CLI, Cursor, VS Code Copilot and Windsurf | Validated clients: Claude Desktop, Claude Code, ChatGPT on the web, Codex and Cursor |
| Price | No separate charge today | Meta lists no price. Guides call it free during the open beta. |
| Server URL | https://mcp.syncwith.com/mcp | https://mcp.facebook.com/ads |
Our server has no tool that creates, edits or pauses anything in an ad account. There’s no scope to pick, no rule to ask a client for, and nothing a new teammate can switch on by mistake. It reads Facebook Ads two ways: a live query, which calls Facebook’s own API when you ask, or a read of the SyncWith reports you already run.
It’s the same Facebook Ads connection our customers connect more than any other: 11,846 new connections in Q3 2026 across SyncWith’s Google Sheets add-on and Looker Studio connectors, 51% of the new connections we could attribute to a source. As our co-founder Alex Black told a customer in 2025, “our meta connector is the most popular by far. So we’ve put a lot of work into that.”
And it’s one server for all your sources, so one chat can put Facebook spend next to Google Ads spend, Google Analytics 4 sessions or Shopify sales. Meta’s server covers Meta ads, and its launch post leaves cross-channel questions for your own AI tool to handle.
Your Google account is your login, and we create a free SyncWith account if you don’t have one. Then connect Facebook Ads in SyncWith, or ask your assistant to do it and follow the sign-in link it sends back. Your assistant may ask before it runs a live query. Each live query uses one refresh from your plan, the same as a report refresh, and the free Hobby plan includes 35 a month. Listing and reading reports don’t use any.
Start each prompt with “using SyncWith.” If Meta’s connector is also on in the same chat, that keeps the answer coming from the read-only one.
Then check the answer before it reaches a client:
e-dialog found charts in chat aren’t “sufficient for reporting to clients,” and we agree. Use the chat to find what to look at, then send the scheduled Facebook Ads report in Google Sheets or Looker Studio.
Paste this URL into Claude or ChatGPT as a custom connector, then sign in with Google:
https://mcp.syncwith.com/mcp
Every Claude plan can add one, though Free allows a single custom connector. In ChatGPT, an admin of a Business, Enterprise or Edu workspace adds it. Steps for Claude and ChatGPT are on their own pages, and the full setup is in the SyncWith MCP docs.