The Meta ads MCP server connects to Claude as a custom connector. You add the server URL https://mcp.facebook.com/ads inside Claude, finish the Facebook Login for Business sign-in in a browser window, and the ad account tools appear in the chat. In Claude Code the same connection takes one command plus your Meta app ID.
Meta announced the server in open beta on April 29, 2026, and hosts it at that address. It works with any MCP-compatible agent, so the Claude side of the setup is the standard remote connector path, not a Meta-specific integration.
What you need before you start
- A Claude plan that includes custom connectors. Anthropic lists Free, Pro, Max, Ultra, Team and Enterprise, with Free limited to one connector.
- Access to the ad account you want the agent to read, and the business portfolio that owns it.
- A Facebook account or a Meta Managed Account to sign in with.
- The minimum permission set Meta documents:
ads_mcp_managementplus eitherads_readorads_management.
Decide the permission level before the first sign-in, not after. That choice is what separates an agent that can look at spend from one that can change it.
Connect the server in Claude.ai or Claude Desktop
- Open the connectors settings in Claude and choose to add a custom connector.
- Give it a name you will recognize in a chat, for example Meta ads.
- Paste the server URL
https://mcp.facebook.com/ads. - Save the connector, then start the connection. A browser window opens for the sign-in.
- Sign in with the Facebook account that can see the ad account, and approve the permission set you chose.
- Return to a chat and check that the tools are listed before you ask anything.
On Team and Enterprise plans an owner adds the connector for the whole organization, and each member then connects their own account. If your company runs several ad accounts, connect once and name the account in every prompt.
Connect the server in Claude Code
Claude Code takes the server as an HTTP transport and then signs in from inside the session:
claude mcp add --transport http meta-ads https://mcp.facebook.com/ads --client-id <META_APP_ID>
Run /mcp afterwards to complete the OAuth sign-in. The client ID argument matters here because Meta’s server expects a pre-registered OAuth client, and your own Meta app is that client. Without it the browser step opens and the authorization fails.
If the command succeeds but no tools appear, check that you are in the project or user scope you think you are in, and that the sign-in finished in the same browser profile you use for Meta.
Check the access before the agent touches budget
Treat the connection as you would a new media buyer on their first day: full visibility, no spending rights until they earn them.
Start with ads_read. Meta’s permissions reference says ads_read lets an app pull ads report information, while ads_management lets it both read and manage the ad account. You can change the grant later without rebuilding the connector.
Know what the write tools do. Meta’s ad creation tools reference says write tools create entities in a paused state, and activation is a separate tool that starts spending budget. That reference lists no tool to delete a campaign, ad set or ad; its only delete removes a custom audience. A misread prompt can therefore build a structure, but it cannot launch or delete one.
Keep the client’s approval setting on. In normal chats Claude asks before calling a connector’s tool, and Anthropic advises using “Allow always” only for servers you trust. In Research, Claude can call connector tools automatically, so do not run budget questions there with write permissions granted.
Read the log after a session. Meta’s server has an activity log tool that shows what changed on the ad account, the same way the campaign history in Ads Manager does. If several people connect agents to one business portfolio, the ads MCP server rules Meta introduced in July 2026 are where full-control users decide what agents may touch, from budget changes to catalogs.
Anthropic also warns that a malicious server can carry hidden instructions. Connect servers from organizations you trust, and nothing else.
What the connection does not give you
The server reports what Meta counted. Its conversions are Meta’s attributed number, and Meta also models conversions where its data is partial, so the count inside Claude will not match the leads in your CRM. For a lead generation account that gap is the one number worth understanding before you act on anything the agent says; the mechanics are in Meta Pixel, Conversions API and attribution.
Coverage is broad on Meta and stops there. Reporting, ad creation, catalogs, signal health, A/B tests, lift studies, activity logs and Ad Library searches are all inside, which is why the comparison of Meta Ads MCP servers puts Meta’s own server first when you need breadth on one platform.
If the connection does not work
Most failures are permission or client-side, not Meta-side: a permission set that does not include ads_mcp_management, a browser sign-in completed with the wrong Facebook profile, or a workspace policy that blocks the connector. The error-by-error list is in why your Meta Ads MCP server is not working.
Once the tools are visible, start with a read-only question that names the campaign and the date range, and ask for a plan before any write. An agent that can see spend, creatives and result counts per ad is already useful; the write side can wait until you have watched it answer correctly for a week.