Meta Ads MCP for multiple ad accounts and agencies
One Pipeboard account holds as many Facebook logins as your clients require. Every tool call names an account id and is routed to the login that owns it. Teammates use shared connections without Facebook access of their own, juniors can be capped to read-only, and the same URL also serves Google, TikTok and LinkedIn.
Where Meta’s own Ads MCP server stops
Meta hosts an Ads MCP server at https://mcp.facebook.com/ads (developer docs). It is write-capable: Meta’s docs list reporting, creating and editing ads, ad sets and campaigns, catalogs, A/B tests and activity logs. It reaches whatever the Facebook login you connect can reach, and it is in open beta.
What Meta’s documentation does not describe, as of 2026-10-13:
- Sharing that access with teammates who have no Facebook permission on the account.
- Capping a specific person or assistant to read-only.
- Scoping an API token or automation to one client’s accounts.
- Managing Google, TikTok, LinkedIn, Pinterest, Reddit, Snap or Microsoft Ads from the same connection.
Many accounts also still see is_ads_mcp_enabled: false during Meta’s rollout — see what that means and what to do.
How Pipeboard handles many accounts
Pipeboard is a Badged Meta Business Partner. The MCP talks to Meta’s standard Marketing API under the access your own Facebook logins already hold; nothing below bypasses Meta’s permissions.
Several Facebook logins, one Pipeboard account
Connect each login that holds client access. list_meta_connections shows which login owns which ad account; per-account calls are routed to the right login for you.
Account id on every call, no default account
Every per-account tool requires an explicit account id. The assistant cannot "accidentally" act on whichever account happened to be first.
Shared connections for teammates
Share a connection with named members, for all accounts or a subset. They work in Claude without their own Facebook login; changes appear under the shared login.
Read-only caps and scoped tokens
Read-only API tokens for anyone; per-member read-only caps and per-account token scoping on the Agency plan.
Slots that match how agencies bill
Pay per connected ad account, not per command. Swap accounts between slots from Settings or by prompt with manage_account_slots.
Google, TikTok, LinkedIn and more on the same URL
The All Ads URL serves every platform you have connected, so cross-platform client reports are one prompt.
Ad account slots per plan
A slot is one distinct ad account you run commands against in a billing cycle. Paid plans do not meter commands; they meter accounts. Extra slots are available as an add-on on the pricing page.
Agency setup, step by step
- 1
Connect every login that holds client access
At pipeboard.co/connections connect each Facebook login (one per Business Portfolio if that is how your clients granted access). Runget_ad_accountsonce so Pipeboard learns which accounts each login reaches. - 2
Pick which accounts use your slots
Open the Slots tab in Settings, or ask the assistant to callmanage_account_slots, and choose the client accounts you will run commands against this cycle. - 3
Share the connection with your team
From the connection card, share all accounts or a chosen subset with the media buyers who need them. They add the MCP URL to their own Claude or ChatGPT and see only the shared accounts, with no Facebook login of their own. - 4
Set read-only where appropriate
Cap juniors and contractors to read-only via team access controls, or hand automations a read-only or account-scoped API token. - 5
Add one URL to the AI client
https://meta-ads.mcp.pipeboard.co/Or the All Ads URL if clients also run Google, TikTok or LinkedIn:
https://ads.mcp.pipeboard.co/Client-by-client steps are in the Meta Ads MCP guide.
Prompts across client accounts
“List my Meta connections and which ad accounts route through each one.”
“For accounts act_111, act_222 and act_333, compare spend, ROAS and CPA for the last 7 days against the previous 7 and flag anything that moved more than 20%.”
“In act_222 only, find ad sets with CPA above $45 over the last 14 days. Show me the list first; after I confirm, pause them.”
“Duplicate the top campaign from act_111 into act_333 with a $100 daily budget, paused, and swap in the creatives from the client’s Drive folder.”
New campaigns and ad sets are created paused by default, so a duplicate into the wrong account cannot spend before someone looks at it.
Frequently asked questions
Can one Meta Ads MCP connection manage several ad accounts?
Yes. Pipeboard connects as many Facebook logins as you need to one Pipeboard account, lists every ad account each login can reach, and routes each tool call to the login that owns that account automatically. You pass an account id on every call and never a connection id, so a prompt like "compare ROAS across these five accounts" just works even when the accounts live in different Business Portfolios.
Do my teammates need their own Facebook access to use the MCP?
No. A team owner or admin connects Meta once and shares that connection with named team members, covering all accounts or a chosen subset. Members then use those accounts in Claude, ChatGPT or any MCP client without connecting a Facebook login of their own. Changes they make appear in Meta as made by the shared login.
Can I give a junior media buyer read-only access?
Yes, two ways. Any user can issue a read-only API token, and the server refuses write tools for that token. On the Agency plan, team owners can also cap individual members to read-only across every Pipeboard MCP; new invitees start read-only by default and their assistant’s tools/list no longer shows write tools.
What is an ad account slot and how many do I get?
Each distinct ad account you run commands against in a billing cycle uses one slot. The Free plan includes 2, Pro 3, Premium 10 and Agency 25, with additional slots available as an add-on. You can view and swap which accounts use your slots from Settings or by asking the assistant to call manage_account_slots.
Does Meta’s official Ads MCP server support agencies with many client accounts?
Meta’s server at mcp.facebook.com/ads can read reporting and create and edit campaigns, ad sets and ads, and it reaches whatever your own Facebook login can reach. Meta’s documentation does not describe sharing that access with teammates who lack Facebook permissions, per-member read-only limits, or managing Google, TikTok or LinkedIn from the same connection. It is also in open beta and many accounts still see is_ads_mcp_enabled: false during the rollout.
What is the Meta Ads MCP server URL for multiple accounts?
Pipeboard’s hosted Meta Ads MCP is https://meta-ads.mcp.pipeboard.co/. If you also run other platforms through Pipeboard, the All Ads URL https://ads.mcp.pipeboard.co/ exposes every connected platform on one connection. Both are Streamable HTTP endpoints you add to Claude, ChatGPT, Cursor or any MCP client; you authenticate with your Pipeboard account.
Can I use Pipeboard alongside Meta’s official MCP server?
Yes. They are independent servers. Keep Meta’s connector installed if your account is enabled for it and add Pipeboard for the accounts, teammates or platforms it does not cover. Pipeboard is a Badged Meta Business Partner and talks to the standard Marketing API under your own account access, so nothing breaks if Meta enables more of your accounts later.
How do I avoid an AI editing the wrong client’s account?
Every per-account tool requires an explicit account id and there is no "default account", so a prompt has to name the account it touches. Campaigns are created paused by default, read-only tokens and team caps limit who can write at all, and on the Agency plan API tokens can be scoped to specific ad accounts so an automation for one client cannot reach another.