How to set up Meta Ads MCP
How to Set Up Meta Ads MCP for Claude, ChatGPT & Cursor
Meta Ads MCP setup for Claude, Cursor, ChatGPT, and Codex: connect the ad account, verify with list_connections, start read-only, and keep writes approval-gated.
Published and last verified: July 29, 2026 · AdsCove Product & Engineering
Direct answer
To set up Meta Ads MCP with AdsCove: create an account, connect Meta Ads via Facebook Login for Business (the Ads Manager ad account you intend to operate), connect your AI client to https://adscove.com/api/mcp, then call list_connections. Start with a read-only report. Campaign, budget, and status changes return a reviewable pending action before AdsCove executes them. Meta also hosts an Ads MCP at mcp.facebook.com/ads—that path is Meta-only; AdsCove adds Shopify/Google context and approval-gated writes. Compare options in Meta Ads MCP vs AdsCove.
Setup steps
- 1
Create an AdsCove account
Sign up in the browser. You do not need to install Python, clone a repository, or keep a Meta access token in your AI client.
- 2
Connect the Meta / Ads Manager ad account
Open Connections, choose Meta Ads, complete Facebook Login for Business, and select the Ads Manager ad account you intend to use. Confirm the account ID matches Meta Ads Manager before continuing.
- 3
Connect Claude, Cursor, ChatGPT, or Codex
Use the remote MCP endpoint https://adscove.com/api/mcp. Codex, Claude, Doubao Desktop, Gemini, Cursor, and eligible ChatGPT web accounts can use OAuth; API keys remain a fallback for clients without remote-MCP OAuth. Ecommerce operators in Cursor or Claude usually want this same endpoint so Shopify + Meta share one agent loop.
- 4
Verify with list_connections
Ask the client to call list_connections. Confirm the returned Meta connection is the expected Ads Manager account before requesting performance data.
- 5
Run a read-only Ads Manager check
Request seven-day account performance or campaign-level results first. This confirms Marketing API permissions and reporting before any write is prepared. Do not invent ROAS thresholds—ask the model to show the fields it used.
- 6
Keep every write approval-gated
A real write first returns a pending execution. Review the object, budget, targeting, creative, landing page, and status, then approve that exact execution. Never treat setup success as permission for unsupervised budget changes.
What “Meta Ads MCP” / Ads Manager MCP means
MCP is the connection layer between an AI client and advertising tools. A Meta Ads MCP (often searched as Ads Manager MCP or Facebook Ads MCP) exposes account reporting and campaign operations as named tools, so the AI can request structured data instead of asking you to export CSV files from Ads Manager.
Meta provides a hosted Ads MCP endpoint, and independent services can also expose Meta Marketing API workflows over MCP. These are not identical products. Tool coverage, authorization, approval behavior, and cross-platform context can differ, so inspect the tool list before granting access.
Two setup paths: Meta hosted vs AdsCove hosted
Path A — Meta’s hosted Ads MCP (mcp.facebook.com/ads): direct Meta advertising context. Useful when you only need Meta tools inside the client.
Path B — AdsCove hosted MCP (https://adscove.com/api/mcp): Meta Ads plus optional Shopify and Google Ads in one agent loop, with reads separated from writes and protected changes behind explicit approval. Ecommerce operators who reconcile store cash with paid spend usually want Path B. Details: Meta Ads MCP vs AdsCove.
Connection details for AdsCove
AdsCove is a remote Streamable HTTP MCP server. The platform token stays on AdsCove's server; the AI client receives a revocable AdsCove authorization rather than your raw Meta token.
Use the compact endpoint for normal use. It includes a dispatcher for the full AdsCove catalog while keeping client setup small.
Server name: adscove
Endpoint: https://adscove.com/api/mcp
Transport: Streamable HTTP
OAuth: supported by compatible remote-MCP clients
API-key fallback: Authorization: Bearer sk_live_your_key
Verification tool: list_connectionsConnect Meta Ads to Claude or ChatGPT (where to paste the URL)
Every client uses the same AdsCove endpoint, https://adscove.com/api/mcp; only the place you paste it differs. Connect the Meta ad account once in AdsCove → Connections, then add the endpoint to each AI client you use. There is no separate Meta-only URL to add for AdsCove.
After adding the server, enable it for the chat and ask the client to call list_connections. If Meta is listed with the expected ad account ID, the connection works and you can start with a read-only report.
- Claude web or Desktop: Settings → Connectors → Add custom connector → paste the URL → sign in to AdsCove and Authorize. Claude mobile can use the connector after it is added on web or Desktop. Details: /clients/claude.
- Claude Code: run claude mcp add --transport http adscove https://adscove.com/api/mcp, then open /mcp and complete OAuth in the browser. Details: /clients/claude-code.
- ChatGPT (web): enable Developer mode, create a custom MCP app named AdsCove with the URL, choose OAuth with Dynamic Client Registration, select Scan tools, and approve in the browser. ChatGPT's mobile apps cannot use custom MCP apps yet. Details: /clients/chatgpt.
- Cursor, Codex, and other remote-MCP clients: add a remote MCP server named adscove with the same URL and complete OAuth; use an AdsCove API key in the Authorization header only if the client cannot do OAuth. Details: /clients/cursor and /clients/codex.
Looking for Google Ads MCP or a GitHub Meta Ads MCP server?
This guide covers Meta (Facebook) Ads only. If you want Google Ads in Claude, ChatGPT, Cursor, or Codex, use the Google Ads MCP setup guide at /guides/google-ads-mcp-setup. With AdsCove you do not need a second server: the same endpoint, https://adscove.com/api/mcp, serves Meta Ads, Google Ads, and optional Shopify once each account is connected in AdsCove → Connections.
Community Meta Ads MCP servers on GitHub are a self-hosted route: you run the code, create or reuse a Meta app and access token, and own updates and security. Meta's hosted Ads MCP (mcp.facebook.com/ads) and AdsCove are hosted routes, so no server runs on your machine. Whichever route you choose, inspect the tool list and keep write actions behind a review step.
Safe first prompts after setup
Begin with a narrow date range and a read-only request. Ask the AI to show its evidence and name the exact object it would change before it prepares a write.
- Show Meta account and campaign performance for the last seven days. Do not change anything.
- Find campaigns with material spend and weak conversion evidence. Explain the fields you used—do not invent a ROAS cutoff.
- Draft one paused Meta campaign from this approved brief. Return the pending execution and wait for my approval.
- Show the exact current and proposed budget before preparing a budget change.
Common Meta MCP setup problems
If list_connections does not show Meta, reconnect from the AdsCove console and confirm the Facebook user has access to the intended Business and Ads Manager ad account. If reads work but a specific operation fails, check the required permission and account eligibility rather than repeatedly authorizing the same request.
- Wrong ad account: compare the returned account ID with Meta Ads Manager.
- Expired or revoked access: reconnect Meta from AdsCove Connections.
- Client cannot use OAuth: generate an AdsCove key and send it only in the Authorization header.
- Write remains pending: approve the exact execution in the conversation or AdsCove Activity page before it expires.
- Expecting Shopify context on Meta-only MCP: use AdsCove (or connect Shopify separately)—Meta’s hosted Ads MCP does not replace store-truth reconciliation.
Frequently asked questions
How do I set up Meta MCP for Claude or Cursor?
With AdsCove: add https://adscove.com/api/mcp as a remote MCP server, complete OAuth (or API key fallback), connect Meta Ads in the AdsCove console, then call list_connections and run a read-only seven-day report before any write.
Is Ads Manager MCP the same as Meta Ads MCP?
In search, yes—operators usually mean connecting Ads Manager / Marketing API workflows to an AI client over MCP. This guide covers that setup intent without a duplicate URL.
How do I connect Meta Ads to Claude?
Connect your Meta ad account in AdsCove → Connections (Facebook Login for Business). Then in Claude web or Desktop open Settings → Connectors → Add custom connector, paste https://adscove.com/api/mcp, and authorize AdsCove. Enable AdsCove in a chat and ask Claude to check your platform connection status (list_connections) before requesting a report.
Can ChatGPT use Meta Ads MCP?
Yes, on ChatGPT web for eligible accounts: enable Developer mode, create a custom MCP app with https://adscove.com/api/mcp, choose OAuth with Dynamic Client Registration, and select Scan tools. ChatGPT mobile does not currently support custom MCP apps; AdsCove also exposes a REST fallback for other workflows.
Can a Meta Ads MCP server change live campaigns?
It depends on the server and permissions. AdsCove separates reads from writes, creates campaign resources paused where supported, and requires explicit approval tied to the pending execution before protected changes run.
I searched for Google Ads MCP. Is this the right guide?
No, this one is for Meta Ads. Go to the Google Ads MCP setup guide (/guides/google-ads-mcp-setup). If you use AdsCove, the same https://adscove.com/api/mcp endpoint covers both platforms; connect Google Ads in AdsCove → Connections and list_connections will show it.
Is there a GitHub or open-source Meta Ads MCP server?
Community projects exist on GitHub, and they are self-hosted: you manage the Meta app, access token, hosting, and updates. If you prefer not to run a server, use Meta's hosted Ads MCP for Meta-only work, or AdsCove for Meta plus optional Google Ads and Shopify with approval-gated writes.
Should I use Meta’s hosted Ads MCP or AdsCove?
Use Meta’s hosted endpoint when you only need Meta tools. Use AdsCove when you want Meta plus optional Shopify/Google context and approval-gated writes in one agent loop. See Meta Ads MCP vs AdsCove for an honest comparison.