Most Meta Ads analysis still starts with the same routine: open Ads Manager, choose the right account, reset the date range, export a table, and explain what changed. That works for an occasional check. It becomes slow when you manage several campaigns, compare Facebook with Instagram, or repeat the same report every week.
Connecting Meta Ads to Claude removes the export-and-paste step. Claude can work from your live campaign data, answer follow-up questions in the same conversation, and prepare account changes for your review. Markifact provides the managed connection and controls which Meta account and operations Claude can use.
To connect Meta Ads to Claude, connect your Meta ad account in Markifact, create an MCP server, then add https://api.markifact.com/mcp as a custom connector in Claude and sign in.
That is the whole path. You do not need to build a Meta developer app, host an MCP server, or paste campaign exports into a chat.
This guide covers the Markifact route for connecting Facebook and Instagram ads to Claude. It gives you one managed MCP connection for Meta Ads and the rest of your marketing stack. If you are deciding between different Meta MCP options, I will cover that separately rather than turning a setup guide into a comparison page.
The quick version
- In Markifact, open Connections and connect Meta Ads.
- Open MCP and create a server for Claude.
- Limit that server to the Meta connection you want Claude to use.
- In Claude, add
https://api.markifact.com/mcpas a custom connector. - Sign in to Markifact and test the connection with a read-only report.
I recommend doing the first test before you ask Claude to create or change anything. A boring seven-day campaign report is the fastest way to catch the wrong account, an expired login, or a date-range mistake.
What you are actually connecting
Claude does not log in to Ads Manager with your password. It talks to a remote MCP server, and that server exposes specific tools Claude can call.
In this setup, the path is:
Claude → Markifact MCP → your approved Meta Ads connection
Markifact handles the connection layer and lets you control which saved connections and tools are available to a particular MCP server. That matters if you manage several brands or client accounts. A Claude connector for Client A should not automatically expose Client B.
You can see the current Meta Ads capabilities on the Markifact Meta Ads MCP page.
Before you start
You need:
- Access to the Meta business and ad account you want to connect
- A Markifact workspace
- A Claude plan that supports custom connectors
- Permission to configure connectors if you use a Team or Enterprise Claude organization
Anthropic currently lists custom remote MCP connectors for Pro, Max, Team, and Enterprise plans. On Team and Enterprise, an Owner or Primary Owner may need to configure the organization connector first. The current steps are documented in Anthropic's custom connector guide.
1. Connect Meta Ads in Markifact
Open Connections in Markifact and find Meta Ads. Click Connect.
The Meta authorization flow will ask you to sign in and choose the business assets available to the connection. Read the screens instead of clicking through on autopilot. The accounts Claude can work with ultimately depend on the access granted to the connected Meta user.
When the flow returns to Markifact, confirm that Meta Ads shows as connected. If you manage several Meta logins, give each connection a name you will recognize later.
2. Create an MCP server for Claude
Open MCP in Markifact and create a new server. I use names that tell me both the client and the scope, such as:
Claude - Meta Ads - Main Brand
A clear name becomes useful once you have more than one server.
Inside the server configuration, choose whether it can use every team connection or only specific ones. For a first setup, I would select the single Meta connection you just created. You can also limit the exposed tools if you want a reporting-focused server.
The endpoint shown in Markifact is:
https://api.markifact.com/mcp
The URL is shared, while your Markifact authentication and selected MCP server determine what Claude can access.
3. Add Markifact as a custom connector in Claude
Open Claude's Connectors settings and choose Add custom connector.
Enter these values:
Name: Markifact
URL: https://api.markifact.com/mcp
Then click Add.
Claude will show the connector in your list. Click Connect and complete the Markifact sign-in flow. If Markifact asks you to select an MCP server, choose the server you created for this Meta account.
After authentication, open a Claude chat and check Search and tools. Enable the Markifact connector and the Meta reporting tools you want for the conversation.
4. Run a read-only test first
Do not begin with a prompt like "fix my ads." It gives Claude no date range, no success metric, and no boundary around account changes.
Use this instead:
Use my connected Meta Ads account.
Compare Facebook and Instagram performance for the last 7 days by campaign.
Show spend, conversions, CPA, and ROAS.
Sort by spend from highest to lowest.
Flag missing or incomplete data.
Do not make any changes.
For this request, Claude can call the read-only meta_ads_get_report operation. The report call retrieves data. It does not update the ad account.
The numbers in the example image are illustrative. Your report will use the connected account and date range you specify.
Before moving on, check four things:
- Is this the correct ad account?
- Is the account currency what you expected?
- Does the date range match your request?
- Are the conversion and ROAS fields the ones your team actually uses?
If any answer is no, fix the scope before asking for recommendations.
Copy-paste prompts that are specific enough to work
Weekly campaign summary
Pull Meta Ads campaign performance for the last 7 complete days.
Include spend, impressions, clicks, conversions, CPA, conversion value, and ROAS.
Compare it with the previous 7 days.
Return a table followed by the three biggest changes.
Do not make account changes.
Facebook versus Instagram
Break down Meta Ads performance by platform for the last 14 days.
Compare Facebook and Instagram on spend, CPM, CTR, conversions, CPA, and ROAS.
Explain whether the difference comes from cost, click-through rate, or conversion rate.
Do not make changes.
Find campaigns that need attention
Review active Meta campaigns for the last 30 days.
Flag campaigns that spent at least $500 and have a CPA 25% above the account average.
Show the data behind every flag.
Recommend next steps, but do not apply them.
Client-ready update
Create a concise client update from the last 7 days of Meta Ads data.
Use three sections: wins, issues, and next actions.
Include the numbers supporting each point.
Keep it under 250 words and do not make account changes.
The exact threshold in these prompts is not sacred. Replace it with the amount that is meaningful for your account. What matters is giving Claude a window, metrics, filters, and an output format.
What happens when you ask Claude to change a budget
Reporting and account changes are separate operations.
If you ask Claude to increase a campaign budget, Markifact can prepare the write operation, show the proposed target and value, and wait for approval before continuing. The real operation for this example is meta_ads_update_campaign_budget, and it is marked as requiring approval.
The figures in the example are illustrative. The important part is the state: Nothing has changed yet.
Before approving a budget update, verify:
- The ad account
- The campaign name and ID
- Daily budget versus lifetime budget
- Account currency
- Current value
- Proposed value
I would not approve a budget change based only on a campaign name. Names get duplicated. IDs and current settings are the better confirmation.
Troubleshooting the connection
The Meta ad account is missing
Confirm that the Meta user you connected can access the business and ad account. If several saved Meta connections exist in Markifact, also confirm that the MCP server exposes the right one.
Claude cannot see Markifact
Open Claude's connector settings and check that Markifact is connected. Then open Search and tools in the chat and enable the connector. On a Team or Enterprise organization, ask the owner whether custom connectors are enabled.
Claude can see Markifact but not Meta tools
Review the MCP server configuration in Markifact. A tool restriction may exclude Meta reporting, or the server may point at a different saved connection.
Authentication keeps reopening
Remove or disconnect the connector in Claude, then add it again using the endpoint copied from Markifact. Make sure the URL is exactly https://api.markifact.com/mcp.
The report is empty
Try a wider date range and remove optional filters. Confirm that the selected account had delivery during that period. An empty report is not always an authentication problem.
Claude proposes the wrong account change
Do not approve it. Restate the account, campaign ID, current value, and intended value. If the scope still looks wrong, return to Markifact and narrow the MCP server to the correct connection.
A practical first workflow
Once the connection is stable, save one weekly reporting prompt and run it on the same day each week. Keep the metrics and comparison window consistent. That gives Claude a repeatable job instead of a new guessing exercise every Monday.
I would start with:
- Pull the report.
- Check that the account and dates are correct.
- Ask Claude to explain the largest changes.
- Ask for recommendations without applying them.
- Review one proposed action at a time.
That sequence is slower than saying "optimize everything," but it is much easier to audit.
If you also manage paid search, the next useful setup is the Google Ads MCP and Claude guide. Both platforms can then live behind the same Markifact MCP connection.
Frequently asked questions
Is there a Meta Ads MCP for Claude?
Yes. This guide uses Markifact's managed Meta Ads MCP connection. Add the Markifact remote MCP endpoint to Claude, authenticate, and expose the Meta connection through your selected Markifact MCP server.
What is the Markifact MCP URL for Claude?
The current remote MCP URL is https://api.markifact.com/mcp.
Can Claude access both Facebook and Instagram ad data?
Yes, when those assets are available through the connected Meta Ads account. The reporting scope still depends on the access granted to the Meta user and the connection selected in Markifact.
Do I need to create a Meta developer app?
No. With the managed Markifact route, you do not need to create and host your own Meta developer app or MCP server.
Is the Meta Ads connection read-only?
No. meta_ads_get_report is read-only, while write operations such as meta_ads_update_campaign_budget can change the account after approval. Treat reporting and write requests as separate workflows.
Can Claude change a campaign budget automatically?
Claude can prepare a budget update through Markifact, but the write operation requires approval. Check the account, campaign, budget type, currency, current value, and proposed value before approving it.
Why does Claude not show the connector?
Check your Claude plan, organization permissions, connector authentication, and the Search and tools menu in the current chat. Team and Enterprise organizations may require an Owner or Primary Owner to configure the connector.
Can I limit Claude to one Meta ad account?
Yes. Configure the Markifact MCP server to expose only the saved Meta connection intended for that Claude workflow.
