Connect Meta Ads to Claude Code

Let Claude pause underperformers and shift budgets in Meta Ads. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Meta Ads to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Meta Ads, you add a Meta Ads MCP server: a small hosted service that exposes Meta Ads's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Meta Ads account. No API keys pasted into config files.

claude mcp add --transport http meta-ads https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Meta Ads once connected?

Full read-write Meta Ads access lets Claude pause an underperforming ad set, shift budget between campaigns, adjust a daily cap, duplicate a winning ad, and draft a new campaign for your review. The optimization that used to mean tab-switching into Ads Manager happens where you are already working, with you approving each change.

Pause or resume a specific ad, ad set, or campaign
Adjust a daily or lifetime budget on a named ad set after you confirm
Duplicate a high-performing ad into a new ad set
Create a draft campaign with objective, audience, and placements set
Update bid strategy or schedule on an existing campaign
Flag ad sets exceeding a target cost per result and propose changes

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Meta Ads access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Meta Ads API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Meta Ads changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Meta Ads connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Meta Ads connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Meta Ads account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Meta Ads's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Meta Ads?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Meta Ads account it signs in with. Revoking access is one click in Meta Ads.

More on the Meta Ads connector

Meta Ads connector for claude.ai Braze + Claude Code Iterable + Claude Code Customer.io + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us