Meta Ads MCP: Connect Claude or ChatGPT to Your Ad Account

Yes, Meta has an official Meta Ads MCP server, and you can connect Claude or ChatGPT to it with a custom connector and a Facebook sign-in. MCP (Model Context Protocol) is an open standard that lets an AI assistant connect to outside tools and data. In this case the tool is your Meta ad account. This guide covers the steps, the safety settings to turn on first, and what can go wrong.

If MCP itself is new to you, read What Is MCP? A Plain-English Guide for E-commerce Merchants first.

Does Meta Ads have an MCP server?

Yes. Meta announced "Meta ads AI connectors" in open beta on 29 April 2026. The name covers two things:

• The ads MCP server: a server hosted by Meta that an AI assistant connects to over the internet.
• The ads CLI: a command-line tool (a text-based program) that a coding assistant such as Claude Code can run on your computer.

Meta describes the connection as secure and Meta-authenticated, running from your ad account to the AI agent. Digiday reported that the beta was opened to all eligible advertisers globally.

Do not confuse it with Meta's separate Devtools MCP server. That one is for developers exploring the Graph API (Meta's programming interface) and debugging errors. It does not manage campaigns.

What do you need before connecting?

• A Meta ad account where you have the access level to approve the connection. Meta's own page says anyone with full control of a business portfolio can set governance rules.
• An AI app that supports remote MCP connectors: Claude, Claude Code, ChatGPT or Perplexity are the ones Meta's help page was reported to list. Check the current list in the Business Help Center article "Manage ads from an AI agent".
• A plan that allows custom connectors. This depends on Anthropic or OpenAI, not Meta. Anthropic has limited free Claude plans to one custom connector. OpenAI offers ChatGPT developer mode on Plus, Pro, Business, Enterprise and Edu on the web, with stricter admin controls on workspace plans. Verify in their current docs.
• The server address. Sources disagreed on the exact endpoint, so copy it from Meta's Business Help Center rather than from a blog.

The beta is free at the time of writing. Meta has not said what pricing will be afterwards. Your AI subscription and your ad spend are separate costs.

How do you connect Meta Ads MCP to Claude?

These steps come from third-party guides that cite Meta's help page. Menu names change, so compare with Meta's "Get started" documentation.

1. Open Claude and go to Customize, then Connectors.
2. Choose to add a custom connector.
3. Paste the Meta ads MCP server address from the Business Help Center.
4. Sign in through Facebook Login for Business.
5. Choose which ad accounts to approve. Pick one, not all.
6. Approve the permissions and return to Claude.
7. Start a new conversation and switch the connector on. Connectors are activated per conversation, not globally.
8. Test with a harmless request: "List my active campaigns and their spend for the last 7 days."

One guide tells users to enter an OAuth client ID and secret from their own Meta developer app. Others say none is needed. Meta's July 2026 update says you can connect any AI application using your own developer app, so that looks like an option rather than a requirement. If Claude asks for these values, check Meta's documentation.

How do you connect Meta Ads MCP to ChatGPT?

ChatGPT treats MCP servers as custom apps, and this needs developer mode.

1. In ChatGPT, open Settings, then Apps, then Advanced settings, and turn on developer mode.
2. Create a custom app and paste the same server address from Meta.
3. Choose OAuth as the authentication method.
4. Complete the Facebook sign-in and approve one ad account.
5. In a new chat, enable the app and run a read-only test.

One guide claims that on some plans ChatGPT supports read and fetch access only, while write actions are rolling out to Business and Enterprise or Edu workspaces. This came from a single source. Check OpenAI's current developer mode documentation.

What about Claude Code, Cursor and other clients?

Claude Code uses the same server address. For clients not on Meta's list, such as Cursor or Codex, Meta points you to its developer documentation and your own Meta developer app.

The CLI route is different. It runs locally and authenticates with a system-user token (a non-personal login for automated access). Meta's token guidance, as reported by a third party, requires the ads_mcp_management permission plus ads_read or ads_management. Employee-role system users are supported, Admin-role ones are not. Agencies managing other businesses' accounts reportedly need App Review approval for ads_mcp_management. Confirm all of this in Meta's docs.

What can the connector do, and what can it not do?

At launch, sources reported around 29 tools covering reporting, campaign management, catalog management and signal diagnostics (checks on whether your pixel and conversion data are arriving). Later guides report a much longer list, including pixels, A/B tests and activity logs. The tool list appears to have grown, so check Meta's current tool overview instead of trusting a number.

Realistic uses:

• Pull performance by campaign, ad set or ad, and summarize it in plain language.
• Flag campaigns with rising cost per result.
• Check catalog and pixel health.
• Draft new campaigns (created paused, see below).

What it cannot do:

• It does not fix bad tracking. If conversions are under-reported, the assistant reports the wrong numbers confidently.
• It does not know your margins unless you tell it. Revenue-based ROAS (return on ad spend) can hide unprofitable products. Profit-based tracking addresses that on the data side, which MCP does not.
• It is not a substitute for judgment on budgets and creative.

For the Google side, see Connect Claude to Google Ads with the Google Ads MCP Server.

How do you keep it safe? Read-only first

Meta reports write access in this server, so treat it like giving a new employee login to your ad account.

• Start with reporting prompts only. State in your prompt: "Read data only. Do not change anything."
• Approve one ad account, ideally a smaller one first.
• Use ads MCP server rules. Meta added these in July 2026. A person with full control of the business portfolio can set them in Business Suite, under Settings, Integrations, Ads MCP server. They can block certain actions or budgets above an amount.
• Know the defaults. Campaigns, ad sets and ads are created paused. Activating one starts spending. Meta says actions taken on your behalf require your authorization through the AI agent.
• Review before approving. Read what the assistant plans to change, then confirm manually.
• Check the activity trail in Meta after any test that touched settings.

What can go wrong?

• "Not enabled" or "gradually rolled out" errors. Some guides, mostly from the spring, report a flag (is_ads_mcp_enabled) that was false for many accounts. This may no longer apply, but if you see it, the account is not yet eligible. Try another ad account or wait.
• Wrong account or permission screen. If the account does not appear, check your role on the business portfolio.
• Free plan limits. A second custom connector may be refused on a free Claude plan.
• Account restrictions. Digiday noted online claims that some advertisers had accounts restricted after connecting Claude Code. No official link was confirmed, and unofficial token-based scripts are the usual suspect. Treat "the official server avoids bans" as a vendor claim, not a guarantee. Keep changes small and logged.
• Confident but wrong answers. Check key numbers against Ads Manager.
• Wrong server. Using a lookalike address from a random blog is a security risk. Only use the address from Meta.

What is the best Meta Ads MCP?

For most advertisers, the official Meta server is the sensible starting point: it is hosted by Meta, free in beta and signs in through Meta's own login. Third-party options exist, but they are products from vendors, not neutral recommendations.

Option	Who runs it	Good for	Caveat
Meta ads MCP server	Meta	Most advertisers, reporting first	Open beta, account eligibility may vary
Meta ads CLI	Meta	Coding assistants, scripts	Needs system-user token setup
Pipeboard	Third party	Teams wanting a hosted alternative	Says it is a Meta Business Partner and lists 42 tools in its README; vendor claims, repo is under a BUSL-1.1 license
Adspirer, Markifact, Porter Metrics, GoMarble	Third parties	Cross-platform reporting	Mostly vendor material, evaluate yourself

Whatever you pick, apply the same checks: who holds your token, what permissions are granted, and whether you can revoke access.

Meta is also testing campaign creation and budget changes inside its own Meta AI business assistant. That is a separate test, not part of the MCP server.

Where to confirm the details

Meta's announcement page, the Business Help Center article and the developer documentation are the authority. Third-party guides are useful for screenshots but have disagreed on tool counts, developer-app requirements and plan limits. For the wider picture on connecting assistants to a store, see Ten MCP Use Cases for E-commerce Marketing Teams.