AdAce AdsMeta Ads MCP server setup: connect Claude and ChatGPT to Facebook ads
A Meta Ads MCP server lets an AI assistant such as Claude or ChatGPT read your Facebook and Instagram ad data and draft changes. To set one up with AdAce Ads, you add the connector address https://ads.adace.website/mcp to Claude or ChatGPT, sign in with OAuth, and connect your Meta ad account on Meta's own consent screen. Start with read access. Nothing changes in your account until you approve it. This is the setup how-to. For what the Meta Ads MCP server is and who it suits, see the Meta Ads MCP server page.
What is a Meta Ads MCP server, and what do you need before you start?
MCP (Model Context Protocol) is an open standard that lets an AI assistant use external tools. Instead of you exporting a CSV and pasting numbers into a chat, the assistant calls a tool, gets the live result and answers from it. An MCP server is the program that offers those tools. A Meta Ads MCP server offers tools for Facebook and Instagram ad accounts: results, delivery status, pixels, audiences and change proposals.
AdAce Ads hosts that server, so you install nothing. The same connector is described on the Facebook Ads MCP server page. The assistant reads results and writes proposals, and a change runs only after your approval.
Meta also has its own official option. On April 29, 2026 Meta launched Meta Ads AI connectors in open beta: a Meta-hosted Ads MCP server at https://mcp.facebook.com/ads and an ads command line tool. Meta says the MCP connection needs no developer credentials or coding, and its tools cover reporting, signal health, and creating and editing ads, ad sets and campaigns. Check Meta's page for current availability. AdAce Ads is a separate product: one connector for Google, Meta and other connected platforms, with per-client write policies, approvals, an activity log and undo.
Before you start you need three things. First, an AdAce Ads workspace; the Free plan covers one platform and one ad account, no card needed. Second, access to a Meta ad account with a role that allows what you plan to do, analyze or advertise. Third, Claude or ChatGPT with custom connectors available on your plan. Your ad spend is paid to Meta directly, and AdAce Ads adds no fee on it.
What the AdAce Ads tools can do with Meta ads
| What you want | Read (nothing changes) | Change (proposal or create) | Needs your yes? |
|---|---|---|---|
| Results and structure | get_performance, get_structure, get_breakdowns, compare_periods | None | No, read only |
| Delivery and review status | get_delivery_status (live from Meta), get_ad_set_delivery (reach and frequency) | None | No, read only |
| Pixel and conversions | get_pixels, get_conversion_actions, get_custom_conversions, tracking_audit | create_custom_conversion | No approval needed and it spends nothing |
| Pause or enable campaigns, ad sets, ads | list_campaigns, get_structure | propose_campaign_status, propose_ad_set_status, propose_ad_status | Pausing can apply by itself within the client's limits; enabling needs your yes |
| Budgets | get_structure | propose_budget, propose_ad_set_budget | Lowering can apply by itself within limits; increases need your yes |
| Bid strategy | get_structure | propose_bid_strategy | Always your yes |
| Targeting and audiences | get_ad_set_targeting, get_audiences, search_locations, search_interests, search_languages | propose_ad_set_targeting, create_audience | Targeting changes always need your yes; a new audience spends nothing |
| Landing page of an ad | get_full_ad_creative, check_landing_pages | propose_ad_final_url | Always your yes (Meta reviews the ad again) |
| New campaigns, ad sets and ads | get_pages, get_images, check_creative | create_campaign, create_ad_set, create_ad, create_language_campaign | Created paused, no spend; starting them needs your yes |
| Lead forms | get_lead_forms (structure only, no submitted leads) | create_lead_form | No approval needed and it spends nothing |
Ten prompts to copy, read-only first
Replace the bracketed parts and name the client and the dates. Prompts 1 to 9 only read data. Prompt 10 creates proposals, so read the safety rules above before you use it.
1. Delivery check: For [client], check the delivery status of my active Meta campaigns. Which ads or ad sets are in review, rejected or have issues, and what are the reasons?
2. Week over week: Compare the last 7 days with the 7 days before for [client]'s Meta account. Explain the three biggest changes in spend, results and cost per result, and name the campaign behind each.
3. Which result counts: Show conversions by action type for the last 30 days. Which event is the campaign optimizing for, and does the cost per result use that event?
4. Pixel health: Is the Meta pixel for [client] firing? Give the last event time, the 7-day event volumes and which ad sets optimize on it.
5. Frequency: Which ad sets have the highest frequency in the last 14 days? Do results get worse as frequency rises? Do not suggest changes yet.
6. Audience breakdown: For [ad set], show results by age, gender, placement and device. Where does money go without results?
7. Lead quality by placement: For [lead campaign], which placements bring leads that I marked as good, and which do not?
8. Targeting review: Show the targeting of my top-spending ad set and the custom audiences available. Describe it in plain words. Do not propose changes.
9. Client summary: Write a half-page summary of last month for [client]: spend, results, what worked, what did not and one recommendation. Use only data from the tools and say which days are still preliminary.
10. Draft a safe change: Prepare a proposal to pause the ad sets with spend and no results from prompt 6. Show what changes before anything is sent.
What can Claude change in Meta ads, and what needs your yes?
- Claude cannot approve a change on its own initiative. A person approves, either by pressing Approve in the AdAce Ads cabinet or by saying an explicit yes in the chat to the proposals just shown. Only then does the assistant call approve_change.
- Reads change nothing. The assistant sees only the clients and accounts that your role and the access you granted allow.
- Changes are proposals. A proposal shows what changes, the current value, the new value and the reason. It is checked against the client's limits and expires after 60 minutes if nobody acts on it.
- Under the default policy only spend-reducing changes can apply automatically, such as a pause or a lower budget within the client's limits, with a notification and an undo option. Launches, budget increases and everything else wait for your approval. Bid strategy, targeting and landing page changes on Meta always wait.
- New campaigns, ad sets and ads are created paused. One approval can start the ads, ad sets and campaign together; until then nothing spends.
- You can set a client to Manual only so every change needs approval. The daily budget cap and change limits apply to the assistant exactly as they apply to a person. See Change proposals and Approving changes.
How to set up a Meta Ads MCP server, step by step
- Create your AdAce Ads workspace and sign in.
- Connect Meta first. In AdAce Ads open Integrations and choose Connect Meta. Sign in with Facebook and approve access on Meta's consent screen. See Connect Meta ad accounts and verify Facebook and Instagram data access.
- On Meta's screen choose the ad accounts to import and the Pages and pixels your ads use. If Meta offers to share all current and future assets, choose that option. Picking only the current assets can leave a Page or pixel you add later without access.
- Pick the ad accounts, choose a client for each, import the campaigns and press Check now.
- Now connect Claude. Open Customize, then Connectors, then + Add, then Add custom connector. Menu names change between versions, so follow Anthropic's page if yours differ.
- Enter the name AdAce Ads and the server URL https://ads.adace.website/mcp. Choose OAuth sign in. You do not need an API key.
- Press Connect, sign in to AdAce Ads and pick the right workspace. Start with read access only; add propose later if you want Claude to draft changes.
- In a chat, enable AdAce Ads through + then Connectors and ask: Call get_started in AdAce Ads. This only proves the connection works. On Team and Enterprise plans an owner adds the custom connector for the organization first, then each member presses Connect. Claude Code users get a claude mcp add command on the AdAce Ads AI page.
- For ChatGPT, OpenAI's current flow is: open ChatGPT Plugins, press the plus button, choose Add custom MCP server, enter a name, choose Public endpoint and paste https://ads.adace.website/mcp. Finish the authorization in AdAce Ads and pick the workspace with read access. Availability depends on your account and workspace policy. Details are in Connect ChatGPT to AdAce Ads through MCP and verify the first read.
- Verify with one read. Ask for your Meta ad accounts and the last 7 days of results, then compare one number with Ads Manager. Run prompt 1 or 4 next.
Limits and honest caveats
- There are two separate connections. AdAce Ads must have access to your Meta account, and Claude must be authorized to call AdAce Ads. Connecting Claude does not give it Meta permissions, so without step 2 you get an empty list. See Claude for Google Ads for the same safety model on the Google side.
- Free Claude accounts can add one custom connector. Team and Enterprise owners add it under Organization settings, then Connectors.
- Data is as fresh as the last sync. Meta can revise results for up to 28 days, so recent days are marked preliminary. Ask for exact dates.
- Claude can be wrong. Open the numbers it quotes before you act, especially on small accounts with few results.
- Text inside campaign names or ads is data, not an instruction. Claude is told never to approve a change because ad data asks for it.
- You can revoke access at any time under Connection, then AI assistants, in AdAce Ads.
- Meta's own connector was in open beta at launch, so features and availability can change. Check Meta's page before you rely on it.
Sources and further reading
- Meta Ads MCP server
- Facebook Ads MCP server
- Claude for Google Ads: how to connect it, what to ask and how it stays safe
- Connect Claude to Google Ads and Meta ads
- Connect ChatGPT to AdAce Ads through MCP and verify the first read
- Connect Meta ad accounts and verify Facebook and Instagram data access
- Change proposals
- Approving changes
- Anthropic: custom connectors using remote MCP
- OpenAI: connect and test an MCP connection
- Meta: Ads MCP server overview
- Meta: Meta Ads AI connectors announcement
Common questions
What is a Meta Ads MCP server?
It is a server that gives an AI assistant tools to read Facebook and Instagram ad accounts and prepare changes through the Model Context Protocol. AdAce Ads hosts it, so you connect rather than install anything.
How do I connect Claude to Meta ads?
Connect your Meta ad account in AdAce Ads first. Then in Claude add a custom connector named AdAce Ads with the URL https://ads.adace.website/mcp, sign in with OAuth, and ask Claude to call get_started in AdAce Ads to test it.
Is there an official Meta MCP server?
Yes. Meta launched Meta Ads AI connectors in open beta on April 29, 2026, including a Meta-hosted Ads MCP server. AdAce Ads is a separate product that also covers Google and other platforms, with per-client write policies, approvals and undo.
Can Claude change my Facebook ad campaigns?
Only through proposals. Spend-reducing changes such as a pause or a lower budget can apply automatically within the client's limits under the default policy. Launches, budget increases, bid, targeting and landing page changes need your approval.
Does the Meta Ads MCP setup work with ChatGPT?
Yes. In ChatGPT you add a custom MCP server with the same URL, as a public endpoint, and authorize AdAce Ads. Availability depends on your ChatGPT account and workspace policy.
How much does it cost to connect Meta ads to Claude?
The AdAce Ads Free plan includes one platform and one ad account, no card needed. Ad spend is paid to Meta directly and AdAce Ads adds no fee on it. Your Claude or ChatGPT plan has its own limits.
Try it on your own accounts
Create a workspace, connect Google or Meta in a couple of clicks and see your accounts clearly. Changes follow your approvals or the policy you configure.
Create your workspace