MCP connectorsMeta Ads

Meta Ads MCP: connect Meta Ads to Claude and ChatGPT

Ask Claude or ChatGPT which campaigns spent the most last week, which ads have stopped bringing results or how Instagram compares with Facebook this month. The answer comes straight from Meta Ads, without opening Ads Manager or exporting a report.

We build the connector for your company on Meta’s own Marketing API. Each person signs in with their own Facebook login, so the AI reaches the ad accounts that person reaches, and it only reads.

Built for your company · Works in Claude, ChatGPT and Copilot

In practice

What your team can do with Meta Ads in Claude and ChatGPT

Performance marketing

Find the ads that have gone tired

Ads and ad sets where the cost per result has crept up over the last two weeks, sorted by spend. A list to act on before the weekly review.
Marketing lead

The weekly report in five minutes

Spend, reach, clicks and results per campaign for last week, compared with the week before and written as the summary you send on Monday.
Founders and management

Ad spend in one sentence

What did we spend on Facebook and Instagram this month, and what did it bring in? An answer for the board pack without asking the agency.
Creative and content

Which message works

The ads behind the best results this quarter, with their headlines and texts side by side, so the next brief starts from what worked.
Examples

Ask it like this

  • “Which campaigns had the highest spend last week, and what did each one bring in results?”

  • “Which ads in the Spring Launch campaign have a rising cost per result over the last 14 days?”

  • “Compare spend, clicks and purchases for October and September, per campaign.”

  • “How do Facebook and Instagram compare on cost per lead this month?”

  • “Show daily spend and results for the Denver Store Opening ad set since it started.”

  • “Summarise last week’s results for Harlow & Finch in five bullet points I can send to the team.”

The connector

What we build for Meta Ads

Deployed OS has no ready Meta Ads connector yet. We build it for your company when you start, on Meta Ads’s own API, with the same rules as every other connector: each person’s own login, access decided by group, every call logged.

Ad accounts
The ad accounts each person reaches, with name, currency and time zone.
Campaigns, ad sets and ads
What is running, paused or ended, with objective, budget and schedule.
Spend and results
Spend, reach, impressions, clicks and results per day, campaign, ad set or ad, for the period you ask about.
Breakdowns
The same figures split by platform, placement, country, age or gender, such as Facebook against Instagram.
Ad content
The headline, text and link of each ad, so results can be read next to the message that produced them.
Security

Who sees what

Read-only
The connector reads. It does not create campaigns, change budgets or pause ads. We only build write actions if you ask for them.
Each person’s own Facebook login
Everyone signs in to Meta as themselves, and the connector asks for permission to read ads only. The AI reaches the ad accounts that person has been given in Meta, so no access to a client’s account means no figures from it through the AI either.
Your company decides who gets it
Admins choose which groups get Meta Ads in Deployed OS. A group without access never sees the connector.
Every call logged
Who asked, what was read and when. Deployed OS keeps the log, and it can be exported.
Setup

Set up the Meta Ads connector in three steps

01
We go through with you which questions matter most, such as which results you count and how you name campaigns, and build the connector on Meta’s Marketing API.
02
Your admin approves the connection and chooses which groups get Meta Ads in Deployed OS.
03
Each person connects with their own Facebook login. From then on they just ask.
Compared

Meta Ads’s own MCP server or Deployed OS?

Meta has its own Meta Ads AI Connectors, with an MCP server that Meta hosts. You sign in through Meta, and Meta describes it as covering reporting, creating and editing campaigns, catalogs and signal diagnostics. If Meta Ads is the only system you want in your AI tool, or you want the AI to build and change campaigns, it is a good place to start.

Deployed OS is for when Meta Ads is one system among several, or when the whole company should not be able to change live campaigns from a chat. Our connector reads by default and sits next to Google Ads, your analytics and your CRM in one company connection. Admins decide which groups get each system, every call is logged in one place, the same rules apply in Claude and ChatGPT, and the tools are built around the results your company counts.

Their documentation: Meta Ads AI Connectors

Questions

Meta Ads MCP: common questions

Yes. Meta offers Meta Ads AI Connectors with an MCP server it hosts itself, which can both report on and change campaigns. Deployed OS adds Meta Ads to one company connection with your other systems, read-only by default, with access per group, one log and tools built for your company.

No. The connector reads ad accounts, campaigns, ad sets, ads and their results. It does not create, change or pause anything, and we only build write actions if you ask for them.

Yes. Everyone signs in with their own Facebook login, and Meta only returns the ad accounts that person has been given. The AI cannot reach more than the person could in Ads Manager.

Yes. Instagram ads run from the same ad accounts as Facebook ads, so they are included, and you can ask for the figures split by platform and placement.

Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. Meta Ads data is fetched when someone asks for it.

It depends on the size of your team. Get in touch and we will walk you through it.

More connectorsAll connectors
Let’s talk

See it on your own tools.

Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.