Meta Ads MCP for Claude & Cursor: Hosted vs DIY vs Synter

TL;DR

Running Meta Ads from Claude or Cursor through the Model Context Protocol (MCP) is now practical. You can ask for last week's worst ad sets, review a proposed change, and approve it without opening Ads Manager.

There are three ways to get there:

• Self-hosted Meta MCP: open-source code you run yourself, with your own Meta developer app and access token.
• Hosted single-platform connector: sign in with OAuth and get Meta (and sometimes one or two other platforms) in your chat client.
• Synter: one MCP connection to 27 ad platforms with approval gates on every change, plus cloud agents in the Synter Campaign IDE that keep working after the chat ends.

If Meta is one channel in a wider mix, Synter covers the rest of the stack from the same connection.

What a Meta Ads MCP should handle

Whichever route you choose, check four things before an assistant touches a live account:

1. Authentication. Creating a Meta developer app, requesting ads_read and ads_management, and pasting a long-lived token into a local config file is real work and a real risk. OAuth through a hosted server avoids both.
2. Approvals. Reads should be free. Budget, status, and creative changes should wait for a person to confirm.
3. Response size. Raw Marketing API payloads are large. A good server returns compact, normalized results so the model can reason instead of wading through nested JSON.
4. Coverage. Budget decisions depend on how Meta compares with search, LinkedIn, Reddit, and everything else you run. A Meta-only view cannot tell you where the next dollar should go.

Option 1: Self-hosted

Open-source Meta MCP servers are a good way to learn how MCP works. Expect to:

• Register a Meta developer app and a Business Manager system user.
• Generate and rotate access tokens, and keep them out of version control.
• Run a local process that stops when your laptop sleeps.
• Handle raw API responses and rate limits yourself.

Worth it if you want full control and are comfortable maintaining the integration.

Option 2: Hosted single-platform connector

Hosted connectors remove the developer-app step: add a URL to Claude or Cursor, sign in, and start asking questions. Many hold writes for approval.

The limit is scope. Most cover Meta and perhaps one or two other platforms, so cross-channel questions still need another tool, and the work stops when the chat does.

Option 3: Synter MCP in Claude or Cursor

Connect your ad accounts once in Synter, then point your client at the hosted server:

{
  "mcpServers": {
    "synter-ads": {
      "url": "https://mcp.syntermedia.ai"
    }
  }
}

Prefer a local process? The published package is @synterai/mcp-server. See the Synter MCP setup page for Claude Code, Windsurf, and API-key options.

What you get:

• 27 ad platforms from one connection: Meta, Google, LinkedIn, Microsoft, Reddit, TikTok, X, Amazon, Pinterest, Snapchat, programmatic, and retail media.
• Execution, not only reporting: create campaigns, adjust budgets, pause and enable, sync audiences, and generate creative on the platforms where Synter supports writes, with reporting across all 27.
• Approval gates: changes are staged and confirmed before anything touches a live account.
• Cross-channel questions: ask Claude to compare Meta CPA with Google Search and LinkedIn, then propose a budget shift for you to approve.

Or let Synter run it

An MCP session lasts as long as your chat. Campaigns need attention around the clock.

In the Synter Campaign IDE, named agents do the work you would otherwise prompt for, and bring it back for review:

• Build: audiences, ad variants for each placement, and landing pages matched to the ad.
• Track: Synter Pixel and server-side conversion forwarding to Meta, Google, LinkedIn, and other platforms, so optimization follows real outcomes.
• Monitor: spend, pacing, and performance are watched while you are away, with changes held for your approval.

Your team sets the goal and the rules. Agents do the campaign work you hand off.

Side by side

Which should you use?

• You want to learn MCP or need full control: self-host.
• Your program lives on one or two platforms: a hosted connector may be enough.
• Meta is one channel of several: Synter MCP gives Claude and Cursor the full picture from one config.
• You want the work done, not just queried: use Synter directly and review what the agents prepare.

Set up Synter MCP or get started with Synter.