Meta & Facebook Ads MCP Server for Claude, ChatGPT & Codex
AdsCove Product & Engineering · Last verified July 29, 2026
Check performance, draft, adjust budgets — guardrails throughout
Direct answer
AdsCove gives your AI client a remote Meta Ads MCP connection without putting raw Meta tokens in the client. It can read performance, campaigns, ad sets, ads, creatives, catalogs, datasets, and activity; protected campaign, budget, targeting, and status writes wait for your explicit approval.
What Meta Ads MCP means
A Meta Ads MCP server translates AI requests into structured Meta advertising tools. AdsCove adds an ecommerce operating layer: one connection can combine Meta delivery data with optional Shopify orders and Google Ads evidence before the AI proposes a change.
Facebook Ads MCP: same Meta ad accounts, one connection
People searching for a Facebook Ads MCP usually want an AI client to read and operate the ad accounts they manage in Ads Manager. Facebook and Instagram ads run on the same Meta advertising platform, so a Meta Ads MCP connection is the Facebook Ads MCP connection—there is no separate Facebook-only server to install.
With AdsCove, you authorize the ad account through Facebook Login for Business in the browser, then point Claude, ChatGPT, Codex, Cursor, or another remote-MCP client at https://adscove.com/api/mcp. The AI client never holds a raw Meta access token.
- Connect the Ads Manager ad account you actually operate in the AdsCove console (Facebook Login for Business).
- Add https://adscove.com/api/mcp to your AI client and sign in with OAuth, or use an AdsCove API key where OAuth is not supported.
- Call list_connections to confirm the right ad account, then start with a read-only performance or structure report.
- Let the AI propose changes; campaign, budget, targeting, and status writes return a pending action that runs only after you approve it.
Only need Meta tools inside one client? Meta also hosts its own Ads MCP endpoint—compare both paths in the Meta hosted MCP vs AdsCove guide before choosing. Read the comparison
Meta Ads MCP server URL: what to paste into Claude, ChatGPT, or Cursor
The AdsCove Meta Ads MCP server URL is https://adscove.com/api/mcp. It is one remote endpoint for every platform you connect—Meta, Google Ads, and Shopify—so there is no separate Meta-only URL, port, or local server to run.
Paste that URL wherever your client asks for a remote MCP server or custom connector URL, then sign in with OAuth (or use an AdsCove API key in clients without OAuth, such as Windsurf). Connect the Meta ad account in the AdsCove console first; the URL itself does not contain an account ID, token, or API key. Meta's own hosted endpoint, https://mcp.facebook.com/ads, is a different Meta-only server.
- Claude (web / Desktop): Settings → Connectors → Add custom connector → paste the URL → authorize AdsCove.
- Claude Code: Add it from the terminal with claude mcp add instead of Settings → Connectors.
- ChatGPT (web): Developer mode → create an app → paste the URL as the MCP server → OAuth.
- Cursor: Settings → MCP → add a remote server with the URL → Authenticate.
- Codex: codex mcp add adscove --url https://adscove.com/api/mcp, then codex mcp login adscove.
- Windsurf: Put the URL in mcp_config.json under serverUrl with an AdsCove API key header (Windsurf uses an API key rather than OAuth).
How to connect
Connect Meta Ads in the AdsCove browser console, then add https://adscove.com/api/mcp to Claude, ChatGPT, Codex, Cursor, Gemini, or another remote-MCP client. OAuth is available in compatible clients; an AdsCove API key is the fallback.
Why use AdsCove
- Remote Streamable HTTP endpoint — no local Meta token in the AI client
- Read-only diagnosis before campaign, budget, targeting, or status writes
- Paused campaign, ad-set, ad, duplicate, and test-matrix workflows
- Per-execution approval, idempotency, and activity evidence for protected writes
- Optional Shopify revenue and Google Ads context in the same conversation
Compatible AI clients
Setup and comparison guides
Core guarantees
- Standard Facebook Login for Business authorization
- Creation forces PAUSED; activation needs separate approval
- Budgets handled in account currency; guardrails convert uniformly
- Multiple ad accounts connect and disconnect independently
Available tools (73)
53 read (execute directly) · 20 write (need approval). Full parameters in Tools Reference.
Frequently asked questions
What is the Meta Ads MCP server URL?
For AdsCove it is https://adscove.com/api/mcp—the same remote URL for Meta, Google Ads, and Shopify. Paste it into your client's remote MCP or custom connector field and sign in with OAuth (or an AdsCove API key where OAuth is unsupported); it contains no account ID or token. Meta's own hosted Meta-only endpoint is https://mcp.facebook.com/ads.
What is a Meta Ads MCP server?
It is a Model Context Protocol server that exposes Meta advertising data and actions as tools an AI client can call with structured inputs and outputs.
Does AdsCove also cover Facebook Ads MCP searches?
Yes. Facebook Ads and Meta Ads refer to the same advertising platform family here, so this page covers Facebook and Instagram ad-account workflows without creating a duplicate page.
Is there a separate Facebook Ads MCP server?
Not for AdsCove users. Facebook and Instagram campaigns live in Meta ad accounts, so one Meta Ads MCP connection covers them. Meta's own hosted Ads MCP endpoint is a separate, Meta-only option.
Can the MCP change live campaigns?
AdsCove can prepare protected writes, but the write waits for explicit approval tied to that execution. Creation workflows use paused resources where supported, and activation is separate.
Is AdsCove Meta's official MCP?
No. AdsCove is an independent hosted MCP service using authorized Meta platform access. Meta also operates its own hosted Ads MCP endpoint.