How to connect Claude to Meta Ads
How-to guide · 2 min read · Updated 2026-10-21 · By the Cofoundr team
You connect Claude to Meta Ads through an MCP server. Meta has its own ads MCP server for developers, and tools like Cofoundr offer a hosted one scoped to your accounts. Start read-only, test with simple questions, and only allow changes once you trust the setup.
Claude can answer questions about your campaigns when it can reach the data. MCP, the Model Context Protocol, is the standard way to give it that access. There are a few routes, and the right one depends on how many accounts you run and how much control you want. Check each provider's own setup page, because options change quickly.
The options
- Meta's own ads MCP server. Meta's developer documentation describes an MCP server that connects AI apps to ad accounts, with tools for creating and editing campaigns, audiences and catalogs, reporting, and signal diagnostics. You connect it through your own Meta app, and an agency managing other businesses' data needs Advanced Access to the ads_mcp_management permission, which requires app review. Meta says it is rolling out tools to ad accounts gradually. Read its ads MCP server documentation for the current steps.
- A third-party MCP server built for agencies, such as Cofoundr's, which covers many client accounts with per-account permissions.
- Your own server built on Meta's APIs, which needs developer time and ongoing upkeep.
Before you connect
- Decide which accounts the AI may see. Fewer is safer.
- Choose read-only first. Add write access only after testing.
- Check your client agreements for rules on sharing data with AI tools.
- Confirm the server logs what the AI does, so you can review it.
General steps in Claude
- Open Claude's settings and find connectors or integrations.
- Add the MCP server using the address and sign-in method the provider gives you.
- Sign in and approve the accounts and permission level.
- Start a new chat and confirm the connection by asking which ad accounts it can see.
Test with safe questions first
- Which accounts can you see?
- What did account X spend yesterday, and how does it compare with the previous seven days?
- Which campaigns are spending without results this week?
- List what changed in account X recently.
When to allow changes
Allow edits only for a narrow set of actions and accounts, keep a human approval step for anything that spends money, and review the log regularly. The safe AI automation checklist lists the controls to look for.
Using Cofoundr's MCP server
You can also skip the outside setup: Hadya, the chat inside Cofoundr, can create campaigns and take the same actions as the MCP, apart from creating ad images or videos. Cofoundr's MCP server has 82 actions, per-account scoped tokens, a read-only or read and write choice, and an audit trail. The full explanation is in the MCP guide.
Frequently asked questions
Can Claude connect to Meta Ads?
Yes, through an MCP server. Meta documents its own ads MCP server, which you connect through a Meta app of your own. Third-party servers such as Cofoundr's are hosted and need no Meta app review. Check each provider's current setup page.
Is it safe to let Claude access my ad accounts?
It can be, if you give read-only access first, limit the accounts, keep approval on spending changes and review the activity log.
Do I need to code?
Not for a hosted MCP server. Building your own does need development work.
Does it work with ChatGPT too?
MCP is an open standard and several AI tools support it. Check the provider's page for your tool.