๐ Connect Claude to your Meta ads account (MCP setup)
Claude can talk directly to your Meta ads account โ reading campaigns, spend, and results, and answering questions about them in plain English. The bridge is called MCP (Model Context Protocol). Here's the honest setup guide, including the parts that are fiddly.
What this actually gets you
Instead of exporting CSVs and squinting at Ads Manager, you ask: "Which ad sets spent the most last week and what did each cost per lead?" and get an answer with the real numbers. It's analysis on demand โ Claude reads your account; you keep making the decisions.
The setup (30โ45 minutes, one time)
- Get Claude Desktop (the app, not just the website) โ MCP connectors run through it.
- Find a Meta Ads MCP server. Search the web or an MCP directory for "Meta Ads MCP" โ there are open-source options and hosted ones. Prefer actively maintained projects, and read what permissions they request.
- Create a Meta access token. This happens in Meta's developer portal: create an app, add the Marketing API, generate a token with ads_read permission. Read-only is all you need for analysis โ don't grant write access on day one.
- Add the server to Claude Desktop per the project's README (usually a few lines in a config file or a one-click connector), paste the token, restart, and test with: "List my ad campaigns."
Starter prompts once you're connected
If MCP setup is too much right now
The manual fallback works fine: export your campaign report from Ads Manager as CSV, paste it into any Claude chat, and use the same prompts. You lose the live connection, keep 80% of the value. Start there, wire up MCP when it earns its keep.
Want this done for you?
We set up these exact systems for businesses like yours. One call, honest scope, no pressure.
Massin Systems