How to connect multiple Meta ad accounts to Claude

Connect multiple Meta ad accounts to Claude in 5 steps

Order matters: settle access in Meta first, connect once, then tell Claude how your accounts are named.

Multi-account setups at a glance

Pick the row that matches who holds access to your Meta ad accounts.

Rows 1 to 4 are Ryze AI settings that combine freely. Row 5 is Meta's own route.

How Meta access decides which ad accounts Claude can reach

Claude reaches only the ad accounts your Meta login can open, so access in Meta is the real setup step.

Ryze AI asks Meta for access with OAuth and lists the account it can use through the Meta Ads tool meta_ads__listAdAccounts, which returns every ad account the connected user can access with its id, name and currency. Meta's Marketing API documentation says an app with the right permissions can manage an unlimited number of ad accounts, so the ceiling is access, not a count.

The Ryze AI help center asks for a Meta Business account with an ad account and at least Advertiser access on it, ideally granted through Meta Business Manager. For an agency, that means each client adds your login or your business as a partner with access to their ad account. The Business Manager access guide walks through what to ask the client for.

Access levels and what Claude can do with each

Role names and the steps to assign them are in Meta's own Business Help Center, which did not render for our check, so confirm them there. Ryze AI states the minimum as Advertiser and Admin to allow changes. For a hard read-only setup, connect a Meta login that only has read access.

Meta access expires more often than most platforms

The Ryze AI help center says a Meta connection can show Reconnect needed after two-factor changes or Business Manager role changes. If you manage many accounts under one login, a single reconnect restores all of them.

How Ryze AI handles several Meta ad accounts

Ryze AI keeps 4 things apart: Meta logins, the ad accounts each login reaches, default accounts and workspaces.

The help center's rule is separate clients belong in separate workspaces, while several logins of one business can share one. On the Claude side, one connection covers up to 20 workspaces, which you tick on the Allow connection page. To change the selection, remove the Ryze AI connector in Claude and add it again.

Which Ryze AI plan fits

Ads work starts on the Paid Ads plan: $89 a month with a 7-day free trial. Agencies use the Agency plan at $279 a month. Annual billing takes 30% off the first year. Connecting the connector is free, and the tools need an active plan or trial.

Which Meta Ads tools Claude uses across accounts

Ryze AI exposes 10 Meta Ads tools: 7 read, 2 write and 1 delete.

The list below covers the tools that matter when you switch accounts. The Meta Ads MCP page describes the connector as a whole.

The other four tools list and read creatives and lead forms and upload an image from a URL. Every meta_ads tool takes an optional connection_id. Two limits to know: getAccountSummary uses Meta's default attribution window, while runRawInsights can request others, and Ryze AI cannot reach ad accounts your Meta user has no access to.

Name Meta ad accounts so Claude picks the right one

Most wrong-account answers come from vague names. Give Claude a fixed map once.

• Ask Claude to list the accounts first. The list shows each ad account's id, name and currency, which is the map to copy into your notes.
• Use the account id for anything that moves money. Two ad accounts can carry similar names; an id cannot be confused.
• Keep account names unique. If two accounts share a name, rename one in Meta before using names in prompts.
• Name workspaces after the client, so a prompt can name the workspace without an id.
• Ask for the currency. Every ad account has its own currency, so have Claude show it before adding money across accounts.

Put the map in a Claude project

Claude projects carry instructions into every chat inside them. Paste this block once per agency or client and fill it from the account list:

6 prompts that switch or compare Meta ad accounts

Replace the brackets. Each prompt names its account, so it works the same in a fresh chat.

Every answer comes from your own accounts, so no example numbers are shown. More Meta workflows are in Claude skills for Meta Ads.

Meta's own ads MCP server as a second route

Meta documents a hosted ads MCP server of its own, so you can compare it with the Ryze AI connector.

• Meta's Ads MCP Server overview says the server is hosted remotely at https://mcp.facebook.com/ads.
• The overview describes seven categories of tools. Its requirements, authentication and any multi-account behavior are on Meta's Get started pages, which did not load for our check, so read them before you rely on it.
• Ryze AI's connector is a different server at https://connector.get-ryze.ai/mcp. It signs in with OAuth through Ryze AI, and it adds default accounts, workspaces and Ryze AI features around the Meta tools.

Server-by-server differences are in the best MCP for Meta Ads comparison. Which to pick: use Meta's server if you want only Meta's own tools and are happy with its setup; use Ryze AI if you want several Meta logins, default accounts and workspaces managed in one place.

Keep changes inside the right ad account

With many accounts in one chat, a write to the wrong account is the main risk.

• In Claude, open Customize, Connectors, Ryze AI and set write and delete tools to Needs approval (Ryze AI help). Read tools keep running on their own.
• In the Ryze AI chat, Tool approvals starts on Skip all approvals. Switch it to Approve write & delete, or Manual approve, before you work on live accounts. Scheduled tasks run without an approval step.
• For analysts, connect a Meta login that only has read access. That is the hard read-only guarantee.
• Ask Claude to repeat the account name and id before each change, as in prompt 6.
• The delete tool is meant for an explicit item-by-item approved list, and Ryze AI cannot restore archived or deleted Meta objects.

Other platforms follow the same pattern: see the Google Ads version of this guide and the cross-platform multi-account guide.

Troubleshooting: missing ad accounts, Reconnect needed, stale tools

Match what you see to the row.

Fixes follow the Ryze AI Meta Ads help page. All setups: Ryze AI integrations. Using ChatGPT instead: connect ChatGPT to Meta Ads.

Sources

The verdict

Settle access in Meta first: one login that can open every ad account, with Admin where Claude should make changes. Then connect it to Ryze AI once, set default accounts, keep separate clients in separate workspaces and name the account in every prompt.