Meta Ads Manager is one of the most data-rich advertising platforms available — and one of the hardest to navigate for quick answers. Finding out which ad sets are over-CPA, which creatives are fatiguing, or where your daily budget is burning requires navigating multiple reports, applying filters, and often exporting to a spreadsheet. The Digital Face MCP server gives Claude direct access to your Meta Ads account, so you can get answers in natural language without leaving your conversation.
This guide walks through connecting Claude Desktop or Cursor to your Meta Ads account via the Digital Face MCP server. The setup takes under 15 minutes. Once connected, Claude can query your live campaign data, pull creative performance breakdowns, detect fatigue signals, and flag budget inefficiencies — all through natural language in any Claude conversation.
The Digital Face MCP server is an authenticated integration layer that sits between Claude and your Meta Ads account. It exposes structured tools — list campaigns, get ad set performance, pull creative metrics, check audience overlap, and more — that Claude calls automatically when you ask account-specific questions. Claude does not need you to export data or paste reports. It fetches what it needs from your live account and responds with grounded, current information.
Before starting you need: a Meta Business Manager account with at least one active ad account, Claude Desktop (free at claude.ai) or Cursor, and a Digital Face account. The free plan is sufficient — no credit card required.
Step one: create your Digital Face account and connect Meta Ads. Go to digital-face.nl/signup and sign up with Google. After login, navigate to the Accounts section of your dashboard and click Connect Meta Ads. You will be redirected to a Facebook OAuth flow. Digital Face requests read access for insights, campaign data, and audience information, plus write access for campaign management actions. You can revoke this access at any time from your Facebook Business Settings. The connection takes about 60 seconds.
Step two: retrieve your MCP server URL. Once your Meta Ads account is connected, go to Settings in your Digital Face dashboard and open the MCP and Integrations tab. Copy your personal MCP endpoint URL — it follows the format digital-face.nl/api/mcp/[your-token]. This URL authenticates you automatically so you do not need to manage separate API credentials.
Step three: configure Claude Desktop. On Mac, open Terminal and run: open ~/Library/Application\ Support/Claude. This opens the Claude configuration directory. Open claude_desktop_config.json in a text editor — create it if it does not exist. Add a mcpServers section with the key digital-face, transport set to http, and url set to your MCP endpoint. Save the file and restart Claude Desktop. On Windows, the config file lives at %APPDATA%\Claude\claude_desktop_config.json. The structure is identical.
Step four: verify the connection. Open a new Claude conversation and type: what Meta Ads campaigns are currently active? Claude will call the Digital Face MCP server, query your Meta Ads account in real time, and respond with a list of your active campaigns including their current spend, impressions, and status. If you see your actual campaign names, the connection is working. If Claude does not have access to Meta Ads tools, restart Claude Desktop and try again.
Five high-value queries to run on day one. First: which ad sets have a frequency above 3.0 this week? This is the leading indicator of creative fatigue — catching it early saves budget before CTR drops. Second: show me all ads with CPA more than 50 percent above my campaign target — Claude fetches live conversion data and surfaces the worst performers by name. Third: what is my total Meta Ads spend today versus my daily budget across all accounts? A fast sanity check that normally requires navigating three different reports. Fourth: which ad sets are in the Learning phase right now? Learning-phase ad sets have unstable performance — knowing which ones are still learning helps you avoid premature optimization decisions. Fifth: compare CTR trends for my top five ads over the last 14 days — Claude generates a comparative breakdown that makes creative fatigue visible without you building a pivot table.
For Cursor users: open Cursor settings, go to the MCP section, and click Add MCP Server. Name it digital-face, set transport to HTTP, and paste your MCP endpoint URL. Save and reload the Cursor window. Meta Ads tools are then available in Cursor's AI chat panel. This is useful if you also manage landing pages in Cursor — you can query conversion performance from your Meta Ads account in the same session as reviewing your landing page code.
A note on write operations: Claude confirms every change before executing it. When you ask Claude to pause an underperforming ad set, it shows you which ad set it will pause and the current spend data, then waits for your approval before making any change. Digital Face never modifies your campaigns without explicit in-conversation approval. If you only want read access to start, you can still connect and use all the reporting and analysis features — just skip any queries that request changes.
The MCP endpoint URL authenticates your session. Treat it like a password — do not share it publicly or commit it to a repository. Regenerate it from your Digital Face dashboard under Settings if you believe it has been compromised. For the full reference on Meta Ads MCP tools, including the complete list of supported actions and query examples, visit digital-face.nl/docs. Free plan available at digital-face.nl/signup — connect Meta Ads and Google Ads in the same account.