Meta Ads MCP Server: What It Does, How to Set It Up, and Windsor.ai Compared

Meta Ads MCP is Meta’s official server for connecting AI assistants to Meta ad accounts. It runs at https://mcp.facebook.com/ads, and you connect it by adding that URL to Claude, ChatGPT or Perplexity and signing in with Facebook. Meta launched it on 29 April 2026 as part of Meta ads AI connectors, and it is still in open beta.

Once connected, the assistant can report on your campaigns, create and edit campaigns, ad sets and ads, manage product catalogs and check pixel signals. New campaigns start as drafts. Meta does not charge for the connection, but it says not every ad account has access yet.

Windsor.ai is another way to get the same ad data into Claude or ChatGPT. It installs from Claude’s connector directory, adds 350+ other sources to the same chat, and sends Meta Ads data to BI tools and warehouses too. When we ran the same questions through both on our own ad account, both answered correctly, and Meta’s server returned about five times more data to Claude.

What Meta Ads MCP can do

Meta groups the server’s tools into seven areas (Meta developer documentation, July 2026):

• Reporting: List campaigns, ad sets and ads with spend, impressions, CTR, CPC, CPM and conversions, with filters, breakdowns and date ranges. Also an opportunity score with recommendations, anomaly detection, performance trends, auction ranking and industry benchmarks.
• Ad creation and management: Create and edit campaigns, ad sets and ads. Meta’s developer blog adds creating and updating custom audiences.
• Catalogs: Create a catalog, add products and product sets, and find feed or item issues.
• Signals and datasets: Check pixel and Conversions API signal quality.
• Help and troubleshooting: Search Meta Business Help Center articles.
• A/B tests and lift studies: Create and manage A/B tests and conversion lift studies.
• Activity logs: Read the ad account’s change history, as on the campaign history page in Ads Manager.

Meta also says it is rolling out tool access to ad accounts gradually, and the list an assistant sees can be shorter than this list. Asking the assistant which tools it has is the quickest check.

Safeguards. Campaigns the assistant creates are paused until you review them, and each change asks for your authorization in the AI tool. Meta has added rules that block specific agent actions on an ad account, such as budget increases above a percentage, targeting changes or status changes. Rules are in limited availability, set in Meta Business Suite or through the Marketing API.

Not the same as Meta Social Technologies MCP. Meta runs a second server at https://mcp.facebook.com/devtools for developers who build Meta apps: app settings, App Review status, webhooks, the API changelog and documentation search. It has no ad account tools. If a search for “Meta MCP” brought you here for ads, the ads server is the one at /ads.

How to set up Meta Ads MCP

You need a Meta ad account you have permission to manage, a supported AI tool and your Facebook login. No developer app is needed for the standard setup.

In Claude (claude.ai or Claude Desktop)

1. Open Customize, then Connectors.
2. Click + Add, then Add custom connector.
3. Name it (for example, Meta Ads) and enter https://mcp.facebook.com/ads as the URL.
4. Click Connect and sign in with Facebook. Meta then asks which Pages, businesses and Instagram accounts Claude can reach (all current and future ones, or only those you pick), lists the permissions, and asks you to accept its terms. It does not ask which ad accounts: Claude gets the same ad management permissions you have.
5. In a chat, ask “List my ad accounts.” In our account, Claude showed 98 tools from Meta’s server, all set to ask for approval before each use. You can change that per tool under Customize, Connectors.

Custom connectors work on every Claude plan, but the free plan allows only one, and Meta’s server uses it. Connectors from Claude’s directory, Windsor.ai included, do not count toward that limit (Claude Help Center).

In ChatGPT, Perplexity and other tools

Meta lists ChatGPT, Claude and Perplexity as supported, plus data platforms such as Snowflake and Databricks, and uses the same URL for all of them. Follow each tool’s own steps for adding a remote MCP server with OAuth. On a company plan of these tools, your admin may need to add it. Developers can also connect the server from their own Meta app (Meta’s developer announcement), which agencies managing other businesses’ accounts need to submit for app review.

Meta Ads MCP vs Windsor.ai

Both connect Meta ad accounts to an AI assistant, read the data and can change campaigns. They differ in where the data can go, what else is in the same chat, and which Meta-specific tools you get.

Data sources

• Meta Ads MCP: Meta ad accounts, catalogs and datasets
• Windsor.ai: Meta Ads plus 350+ others, including Google Ads, GA4, TikTok Ads, Shopify, HubSpot, and Facebook Page and Instagram organic data

Where the data goes

• Meta Ads MCP: AI assistants and agent platforms
• Windsor.ai: Claude, ChatGPT and other AI tools, plus Data Studio, Power BI, Sheets, Excel, BigQuery, Snowflake and 20+ more

Adding it to Claude

• Meta Ads MCP: Custom connector by URL; uses the free plan’s one custom connector
• Windsor.ai: One click from Claude’s connector directory

Access

• Meta Ads MCP: Open beta; Meta says not all ad accounts have access yet
• Windsor.ai: Any ad account your Facebook login can read

Meta-only insight tools

• Meta Ads MCP: Opportunity score, industry and auction benchmarks, anomaly detection
• Windsor.ai: Not available; Claude works from the metrics (858 Meta Ads fields)

Changes it can make

• Meta Ads MCP: Campaigns, ad sets, ads, creatives, custom audiences, catalogs, pixel events, A/B tests and lift studies, including delete tools for creatives, custom audiences, catalog products and pixel events
• Windsor.ai: 20 actions: pause and enable, budgets, create campaigns, ad sets and ads, duplicate ad sets, edit settings and creative, boost posts

Safeguards

• Meta Ads MCP: New campaigns paused; each tool asks for approval in Claude by default; rules per ad account (limited availability)
• Windsor.ai: Everything created starts paused; the assistant confirms each change; no delete action

Attribution window

• Meta Ads MCP: Not documented on Meta’s tool pages
• Windsor.ai: 7-day click and 1-day view by default; other windows per request

Cost

• Meta Ads MCP: No cost from Meta; your AI tool’s plan applies
• Windsor.ai: Free forever plan for one data source; paid plans from $19 a month for 3 sources, billed annually

Links: Windsor.ai write actions, Meta Ads field reference, pricing.

We ran the same prompts through both

On 18 October 2026 we connected both to the same Claude account (Opus 5.5) and asked each, in a new chat, the same two questions about our own ad account for 18 September to 17 October 2026: spend, impressions, reach, clicks, leads and cost per lead by ad set, then spend, impressions, clicks and leads by placement. We checked every answer against Ads Manager.

• Ad set table: correct on both routes.
• Placement table: correct on both routes.
• Tool calls for both questions: 5 with Meta Ads MCP, 6 with Windsor.ai.
• Data the tools returned to Claude: 39,692 characters with Meta Ads MCP, 7,496 with Windsor.ai.

Both routes returned the right numbers ($59.55 spent, 9,736 impressions, 82 leads), and both reported the account’s reach without double counting people who saw both ad sets. The difference was in how much data reached Claude. For the ad set question, Meta’s server returned all of the account’s ad sets, about 100, most of them old tests with no spend, in 28,601 characters, and Claude filtered them down to the two that ran. Windsor.ai returned only the two ad sets with delivery. Everything a tool returns goes into Claude’s context, which counts toward your usage limits; an account with fewer idle ad sets would see a smaller gap.

Each call to Meta’s reporting tool also sent the text of our question, a job label and the model name to Meta as part of the request.

Which one to use

Meta Ads MCP fits when Meta is your only paid channel, your account is in Meta’s rollout, and you want Meta’s own recommendations and benchmarks, catalog work or A/B tests from the chat. It is also the route for custom audiences, which Windsor.ai’s actions do not cover.

Windsor.ai fits when the question involves more than Meta: Meta spend next to Google Ads, GA4 sessions or Shopify revenue, or paid results next to Page and Instagram organic posts. Choose it as well when the same Meta data has to feed a Data Studio report, a Sheet or a warehouse, and when the free Claude plan’s custom connector slot is already in use.

“Where the difference shows up is less in the first connection and more in the boring stuff after that: multiple accounts, fields that keep changing, scheduled refreshes, cross-source reporting, blending Meta + Google + Klaviyo + CRM/store data.”
Matthias Kraaz, COO at Windsor.ai

You can use both. Claude can have Meta’s server and Windsor.ai connected at the same time. Name the connector in the prompt, for example Meta’s opportunity score from Meta Ads MCP and cross-channel spend from Windsor.ai.

How to connect Meta Ads to Claude with Windsor.ai

1. Connect your Meta Ads account in Windsor.ai: onboard.windsor.ai/app/facebook (free forever plan, no credit card).
2. In Claude, open Customize, then Connectors, search for Windsor.ai and click Add. Sign in to Windsor.ai.
3. Ask, for example, “Show spend, leads and cost per lead by ad set for the last 30 days.”

The full walkthrough, with prompts by task and the safety settings for changes, is in how to connect Meta Ads to Claude. For ChatGPT, see how to connect Meta Ads to ChatGPT.

Conclusion

Meta Ads MCP connects Meta directly to an AI assistant and brings Meta’s own recommendations, benchmarks and catalog tools. Windsor.ai covers Meta Ads together with your other channels, in AI assistants and in reports, and installs in Claude without a custom connector. Teams that want both can run both in one chat.

Next steps: compare every way to connect Meta Ads to Claude, manage Facebook Ads campaigns from Claude, or connect Meta Ads to Windsor.ai for free.

Facts about Meta’s server come from Meta’s developer documentation and its Meta for Business page, read on 18 October 2026. Meta’s server is in open beta and its tools and availability can change.