Meta ads alongside AdCopilot

AdCopilot works with Google Ads, Google Analytics 4, Search Console and Tag Manager. It has no Meta integration yet. Meta publishes a connector of its own for Meta ads, and an AI assistant can use both side by side.

What each connector does

Meta's connector is its ads MCP server, one of Meta's "ads AI connectors". Meta announced it in open beta on 29 April 2026 and says it reads reporting, finds your ad accounts and Pages, shows the activity log and searches the public Ad Library. It also builds and edits campaigns, ad sets, ads and creatives, and manages audiences and catalogs. See Meta's help page and Meta's developer documentation.

The two connectors do not talk to each other. Your assistant calls each one and puts the answers together.

Add Meta's connector next to AdCopilot

Add AdCopilot first if you have not: Connect Claude or Connect ChatGPT. Meta's is a second connector with its own address and its own sign-in. Adding it changes nothing in AdCopilot.

Meta says you do not need a Meta developer app or developer credentials of your own: its announcement says "no developer credentials, API setup, or coding required". Meta's help page lists Claude, Claude Code, ChatGPT and Perplexity as the assistants it supports.

Claude on the web and desktop

1. In Claude, open Customize, then Connectors, press + Add and choose Add custom connector. This link opens the box.
2. Name it Meta ads, enter the address https://mcp.facebook.com/ads and press Continue.
3. Claude shows the sign-in settings it detected. Review them, then press Add.
4. On the connector's page, press Connect. Meta's documentation says the sign-in is Facebook Login for Business: you sign in with your Facebook account or your Meta Managed Account and approve the permissions it asks for.

We found no Meta connector in Claude's connector directory on 12 October 2026, so it goes in as a custom connector, the way Meta's help page says. We have not run Meta's sign-in end to end, so its screens may differ from this description. We have not tried which sign-in setting Meta accepts. If the detected default fails, try Register automatically under OAuth client. Our AdCopilot steps say to leave the settings as detected; that is for AdCopilot's connector, which we have run.

Claude's own help sets two limits: a free Claude account can have one custom connector, and on a Team or Enterprise organisation members do not add connectors themselves. An owner adds it (on Enterprise, a person with the right role can too) and members then connect. AdCopilot's connector shows in Claude as Custom, so check Claude's help before you add a second.

In Claude Code, the general form is claude mcp add --scope user --transport http meta-ads https://mcp.facebook.com/ads, then /mcp to sign in. We have not tried it against Meta. The command on Meta's own page adds --client-id for a Meta developer app of your own.

ChatGPT

ChatGPT takes Meta's connector as a custom MCP server: name Meta ads, server URL https://mcp.facebook.com/ads, sign-in OAuth. Follow OpenAI's steps. ChatGPT moves these screens often, so go by OpenAI's words. Connect ChatGPT shows the ones we checked for AdCopilot.

We have not run this against Meta. Meta's own developer page for ChatGPT is written for a Meta developer app of your own: it asks you to enter that app's ID as the OAuth Client ID, under Advanced OAuth Settings. Meta's help page, for adding the connector without an app of your own, lists ChatGPT but links OpenAI's general steps and gives none of its own, so we cannot say what ChatGPT will ask for there.

What ChatGPT lets a custom MCP server do depends on your ChatGPT account, and these limits are OpenAI's words, not ours. OpenAI's help page says full MCP support, including tools that change things, is a beta for ChatGPT Business, Enterprise and Edu, and that on Business an admin or owner turns on developer mode first. It says ChatGPT Pro can connect MCP servers with read and fetch permissions only, and it does not mention Plus. So ChatGPT may read your Meta ads without being able to change them. We checked Connect ChatGPT separately, for AdCopilot's connector, so the two pages can differ; OpenAI's page is the one to go by.

If Meta's connector is not there for you

Meta's help page says you may not have access to all of its tools and features yet, so you may see fewer tools than Meta lists.

Meta's help page also describes a page in Meta Business Suite, under Settings, then Integrations, called Ads MCP server. It is where whoever has full control of a business portfolio sets rules for what AI agents may do on an ad account, and Meta says that if you don't see it, you don't have that feature yet. That note is about the rules page. We do not use it to say whether the connector works for you.

The Meta pages we read about adding the connector without a developer app of your own give no list of countries, no cost, no role you need on the ad account and no business verification step. We state none of them. Using your own Meta app to act for other businesses is a different route: Meta's developer documentation says an app used that way must be submitted for review. Meta's help page is where to check.

Ask across both

Name both platforms, so the assistant uses both connectors:

Compare my Google and Meta spend last week.

Which campaigns got the most results this month, on Google and on Meta?

The assistant reads Google Ads through AdCopilot and Meta ads through Meta's connector, then compares. Each platform reports in its own account currency and time zone and counts results its own way, so ask it to say which numbers came from which connector. In ChatGPT, pick each app with @ at the start of a chat, as for AdCopilot in Connect ChatGPT.

Who can change what

• AdCopilot never changes anything in Meta. It has no connection to Meta. Its changes are to your Google products, proposed first, and your AI client asks before each change while write tools stay on Needs approval. See Approval-gated writes.
• Meta's connector can change Meta ads, and its rules are Meta's. Meta says new campaigns, ad sets and ads are created paused, and that your AI client asks for confirmation before one is activated.
• AdCopilot's limits stop at AdCopilot. That it can never delete, and its budget checks, do not apply to Meta's connector, which has a tool that deletes a custom audience.
• Meta has a control of its own. Whoever has full control of a business portfolio can set rules in Meta Business Suite for what AI agents may do on an ad account, such as blocking budget changes. Meta says its server enforces them.

In Claude, open Meta's connector under Customize, then Connectors, and under Tool permissions keep anything that changes your ads on Needs approval, as for AdCopilot.

Where your Meta data goes

Meta's connector is Meta's own server, and your assistant talks to it directly. When you ask about Meta ads, your assistant calls Meta's server and Meta's answer comes straight back to it. AdCopilot's server is not on that path. AdCopilot has no Meta sign-in, so it holds no Meta token, and it sees only the calls your assistant makes to AdCopilot's own tools. The conversation itself stays with your AI client's vendor, as in How your data moves.

AdCopilot's own Meta integration

An AdCopilot integration with Meta ads is on the roadmap. We give no date and do not say yet what it will include. Until it exists, Meta's own connector next to AdCopilot is the way to use both from one assistant.

Sources

• Meta ads AI connectors, Meta's announcement
• Manage ads from an AI agent with Meta ads AI connectors, Meta Business Help Center
• Ads MCP Server, Meta's developer documentation
• Get started, Meta's developer documentation, for a Meta developer app of your own
• Meta ads MCP server, Meta for Developers blog, for the app review step