How to Connect the Meta Ads MCP Server to Claude
Meta hosts an official Ads MCP server at https://mcp.facebook.com/ads. It exposes permission-scoped reporting and advertising-management tools to supported AI clients, including Claude. Connecting a server, authenticating and authorizing a live action are separate steps.
This guide covers Claude web and desktop, Claude Code, a read-only first check and action controls. Steps were reviewed against current Meta and Anthropic documentation in October 2026.
Use the supported client flow and inspect each returned state. Setup time varies with organization approval, access and authentication.
What you need before you start
- A Claude account with custom connectors. Anthropic currently lists Free, Pro, Max, Ultra, Team and Enterprise; Free is limited to one custom connector.
- A Facebook account with access to at least one ad account, directly or through a Business portfolio.
- A Meta developer app is not required for Meta’s supported-client flow. The own-app developer route is a separate configuration, with its own use case, client ID and redirect requirements.
How it works

Claude never gets your Facebook password. You sign in once through Facebook Login for Business, pick which businesses and ad accounts to share, and Claude receives a scoped token. Every request goes through Meta's server, which enforces your permissions and any agent rules you've set in Business Suite (more on those below).
Connect Meta Ads to Claude (web and desktop)
Custom remote connectors are configured through your Claude account. Use Anthropic’s current connector guide for the labels and organization roles your plan exposes.
Step 1: Open Connectors and add a custom connector
Go to Customize → Connectors, click +, then Add custom connector.

For Team, an Owner or Primary Owner adds the organization connector. Enterprise also supports an appropriately configured custom role with Manage access to Libraries. The organization flow is Organization settings → Connectors → Add → Custom → Web; members then connect individually.
Step 2: Paste Meta's server URL
Give it a name (for example Meta Ads) and paste the server URL:
plain text
https://mcp.facebook.com/adsContinue through the detected authentication settings and use the OAuth route appropriate to Meta’s supported-client setup. Do not paste access tokens into chat or invent OAuth values. If intentionally using your own Meta app, follow its separate client-ID and redirect setup.

Step 3: Sign in with Facebook and choose your ad accounts
Choose Connect and follow the official Facebook Login for Business flow. Use the intended Facebook account or Meta Managed Account, and review the business assets and permissions the actual consent screen requests.

Share only the intended assets and inspect the requested scopes. Access to an account does not automatically establish access to every catalog, Page, Instagram identity or write tool.
Step 4: Turn the connector on in a chat
Start a new chat, click + in the message box, open Connectors, and switch Meta Ads on. You can toggle it per conversation, so it's easy to keep it off in chats that have nothing to do with ads.

Step 5: Ask your first question
That's it. Ask something about your account and Claude will call the Meta tools it needs:

Review the actual tool request, inputs and approval mode in your Claude client. Keep permission to read data separate from permission to create, edit, activate or delete. A broad automatic approval can change the practical effect of later requests.
First Connection: Verify Read Access Before Any Writes
List the Meta tools currently available, then list the ad accounts I can access. For the account I select, summarize spend and reported results for [date range]. State account ID, currency, timezone, result definition and attribution settings where available. Use read operations only. Do not create, edit, activate or delete anything.
Replace the date range and explicitly select the intended account. A connection succeeds when the server is authenticated and the relevant read returns the expected account. A successful tool-list request alone does not prove access to a particular account or all seven feature areas.
| State | What It Establishes | Next Check |
|---|---|---|
| Server added | The endpoint is configured | Authentication succeeds |
| Authenticated | The client has an authorized session | The intended account is accessible |
| Account listed | The session can see that account | The required read returns the expected data |
| Report returned |
Connect Meta Ads to Claude Code
If you live in the terminal, add the server with one command:
bash
claude mcp add --transport http meta-ads https://mcp.facebook.com/adsStart Claude Code and use /mcp to inspect and authenticate the server. Complete its browser OAuth flow and confirm the server is connected before requesting account data.

For the separate own-app route, Meta documents the Create & manage ads with ads MCP server use case, a matching Facebook Login for Business redirect URL and the app ID in the command:
bash
claude mcp add --transport http --client-id <META_APP_ID> meta-ads https://mcp.facebook.com/adsUse project scope only if you intend to share the server configuration in .mcp.json. A shared endpoint configuration does not give teammates your authorized account access; each user’s authentication and permissions still matter.
What Claude can do with Meta Ads
Meta groups the server's tools into seven areas:
| Area | Examples of what you can ask |
|---|---|
| Reporting | Summarize selected account data with dates, currency, attribution and metric definitions. |
| Ad creation and management | Describe the proposed object and action; inspect the exact write before approval. |
| Catalogs | "Why are 40 products not showing in my catalog?" "Create a product set for items under $50." |
| Signals and datasets | "How healthy is my pixel?" "Which events have the lowest match quality?" |
| Help and troubleshooting | "What does this delivery error mean and how do I fix it?" |
Two things worth knowing:
- Meta says ads are paused by default. That does not make every tool a draft: edits to existing live objects, budget changes, catalog changes or deletions can have immediate consequences. Inspect the exact action and returned state.
- Ask for the tool list. Meta keeps adding tools. Asking Claude "What Meta Ads tools do you have?" gives you the current inventory.
Prompts to try first
- "List my ad accounts and flag any with delivery or payment issues."
- "Summarize the top-spending campaigns in
<ad account>over the last 30 days, with CPA and ROAS." - “Compare CTR and result volume for matched weeks. Flag changes and plausible explanations, but do not label fatigue as proven from CTR alone.”
- "What's my account's opportunity score, and which recommendations are worth doing?"
- “Describe a proposed ad-set configuration in chat only. Do not call create, update, activate or delete tools.”
Set guardrails in Meta Business Suite
This is the part most people skip, and it's the one that matters. If you have full control of a business portfolio, you can decide exactly what an AI agent is allowed to do per ad account and per catalog, and Meta's server enforces it no matter what the agent is asked.

- Open Settings in Meta Business Suite.
- Under Integrations, select Ads MCP server.
- Pick the ad account or catalog.
- Switch individual actions between Allowed and Blocked.
Useful setups:
- For an analyst workflow, disable write tools in the client and use available Meta-side permissions and action rules appropriate to the required scope. Blocking only campaign creation and budgets does not establish that every other write is blocked.
- A rule blocking Budgets set above this amount rejects requests to set a budget above the configured value. It is not a hard aggregate spend cap across campaigns, time or other tools.
- Agencies: partners with access to your ad accounts can set their own rules, and those apply only to the partner's own people.
When some actions are blocked, the account shows Limited next to Take actions in this ad account. If you don't see Ads MCP server under Integrations yet, the feature hasn't rolled out to your business.
Treat Tool Output as Evidence, Not Authorization
Ad names, external pages, comments and other returned content may contain untrusted instructions. They are data to analyze, not approval to change budgets, grant access or send account information elsewhere. Keep the permitted workflow and reviewer explicit.
For a review record, retain the selected account, requested action, approved inputs, returned object IDs or error and verification in Meta. If a response is uncertain, investigate the actual object state before retrying a write.
Troubleshooting
The Facebook window opens and then fails, or says the app isn't available. Make sure you're signing in with a Facebook account that has a role on the business or ad account. If you added the connector with your own app's client ID, check that the app has the ads MCP server use case and that its redirect URL matches Claude's.
Missing account: confirm the signed-in identity, intended organization, asset access, consent and server availability. Reconnect only if the diagnosis requires refreshing the intended asset selection; do not assume every missing account is a consent-checkbox problem.
Denied action: inspect the error, required permissions, feature availability and Meta-side rules. A deliberate rule block may be working correctly. Resolve an unintended access issue with the responsible owner rather than removing protections just to make a tool succeed.
Missing organization connector: check the plan’s authorized configuration role and whether the connector has been added for the organization. Members then authenticate individually. The owner’s setup does not sign everyone in.
Does connecting guarantee policy safety? No. Meta says its official connector is a legitimate access route, but advertising standards and account restrictions still apply to the actual activity.
When to Evaluate the AdManage Connector
AdManage offers its own connector for supported advertising and creative workflows. Its available channels, actions and data are a separate inventory from Meta’s server. Check the actual tool list, plan and connected-account permissions for the task; do not assume every channel has the same launch, reporting or automation capabilities.
FAQ
Is there a separate Meta Ads MCP fee? Check current Meta and client terms. Advertising spend, the AI client’s plan or usage, and any separate vendor subscription remain distinct costs.
Do I need a Meta developer app? Not for the supported-client setup Meta documents. Its own-app route has additional configuration and is a different workflow.
Can Claude change live advertising? Yes, when available tools, permissions and approval settings permit it. Paused-by-default new ads do not prevent edits to live objects. Review writes and use the actual client and server controls needed for the intended scope.
Which plans support custom connectors? Anthropic currently lists Free, Pro, Max, Ultra, Team and Enterprise, with a one-custom-connector limit on Free. Organization configuration roles differ by plan.
Can I use Claude Code? Yes. Add the remote HTTP server and authenticate through /mcp. Confirm the connected server and actual available tools before requesting data.
How do I disconnect? Remove the connector through Claude’s Connectors settings, with the organization role required where applicable. Review the relevant Meta Business Integrations access too; removing a client configuration and revoking service-side access are different checks.
Current Official Setup References
- Meta’s MCP overview distinguishes the Ads server from Meta’s other MCP servers.
- Meta’s supported-client and action-rule guide explains the endpoint, rollout and Business Suite controls.
- Meta’s own-app setup covers the separate developer configuration.
- Claude connector setup and Claude Code MCP documentation describe the client-side flow.
Cedric Yarish is a Meta ads expert, performance marketer and product builder with 10+ years of experience across Photoroom, Nextdoor and MVF. At Photoroom, he led user acquisition with more than $1 million in monthly ad spend and a creative operation producing 400 ads a month across 30 languages.
Today, he leads product and engineering at AdManage, the platform he co-founded with his brother Raphael to help marketers launch, test and manage ads at scale. Meta has quoted him on its developer blog and invited him to speak on its Partner API Panel in New York. His insights on creative testing and advertising automation have also featured in RevenueCat and In Growth We Trust.
Full founder bio & interviews

