Meta's official Ads MCP Server is live and documented at developers.facebook.com. It exposes 29 tools covering campaign management, creative uploads, audience targeting, and performance reporting — all callable by any MCP-compatible client.
Here is the official endpoint to add to your client:
# Claude Code
claude mcp add https://developers.facebook.com/tools/ads-mcp-server
# Cursor — paste into Settings → MCP, or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"meta-ads": {
"url": "https://developers.facebook.com/tools/ads-mcp-server"
}
}
}
# Codex CLI
codex --mcp-server https://developers.facebook.com/tools/ads-mcp-server
Authentication requires a Meta developer account and an active ad account. Check the official setup guide for current OAuth requirements before you begin.
What "Meta MCP Server" Actually Refers To
The phrase "meta mcp server" maps to three distinct things in 2026. Getting them confused wastes setup time.
What you find | What it is | Useful if… |
|---|---|---|
Meta Ads MCP Server | Official Meta server, 29 ad-management tools | You manage Facebook or Instagram ad campaigns |
Meta Social Technologies MCP | Developer tools for Meta platform APIs | You build on Meta's broader social graph |
Meta VR CLI ( | Horizon OS docs search + VR device management | You build on Quest / Horizon OS |
Most developers searching this term want the Ads MCP Server. The other two are real but narrow.
What the Meta Ads MCP Server Covers
The 29 tools span four categories:
Campaign management — create, edit, and pause campaigns and ad sets
Creative management — upload images and video, assemble ad creatives
Audience targeting — define custom audiences, lookalikes, and targeting rules
Reporting — pull performance breakdowns by campaign, ad set, placement, and date range
The tools call the Meta Marketing API on your behalf, so they carry the same rate limits and permission scopes as direct API calls. An agent running these tools needs ads_management and ads_read permissions on the connected ad account.
What It Does Not Cover
The Ads MCP Server is scoped to the Meta Ads surface. It does not expose:
Organic page management or Instagram publishing
WhatsApp Business APIs
Messenger or Stories outside a paid campaign context
Any tool outside the Ads and Commerce surface
If you need those surfaces, Meta publishes separate MCP tooling under Meta Social Technologies MCP, which is a different server at a different endpoint.
Wiring Meta Ads Alongside Other MCP Servers
The Ads MCP Server is one endpoint among many. A production agent workflow typically connects several servers simultaneously — each covering its own tool namespace.
A Claude Code session wiring three servers looks like this:
claude mcp add https://developers.facebook.com/tools/ads-mcp-server
claude mcp add https://mcp.moltlinestudio.com/github
claude mcp add https://mcp.moltlinestudio.com/web-search
The agent sees all three tool namespaces at once and can call across them in a single session. No wrapper, no middleware. Tool namespaces do not collide as long as tool names do not overlap — and the Meta Ads tools use descriptive prefixed names that do not conflict with general-purpose servers.
For general-purpose MCP tooling to run alongside the Ads server, mcp.moltlinestudio.com hosts 22 servers covering 160 tools. 110 are free with no account, no API key, and no signup. Paste any endpoint directly into Claude Code, Cursor, or Codex CLI and the tools appear immediately.
Debugging a Meta Ads MCP Connection
Three failure modes account for most broken connections:
OAuth scope mismatch. The server returns a 403 or an empty tool list if the connected token lacks ads_management. Re-authorise through the Meta Business Suite with the correct permission scope selected.
Wrong endpoint URL. The documented endpoint is at developers.facebook.com, not a third-party host. Confirm you are using Meta's official URL, not a community fork.
Rate limits mid-session. The Marketing API enforces per-account hourly call limits. If an agent loops a reporting tool at high frequency, it will hit a 429. Build in a retry with backoff; the Retry-After header tells you when to resume.
To confirm the connection is clean before building a workflow, ask the connected agent to call list_tools and verify you see all 29 tools in the response. If you see fewer, the permission scope is incomplete.
Should You Use the Official Server or a Community Fork?
Several community-maintained Meta Ads MCP servers exist on GitHub. The decision is straightforward:
Use Meta's official server if you need long-term stability and do not want to manage a dependency on a third-party maintainer.
Use a community fork only if it exposes a tool the official server does not, and you are prepared to track upstream changes yourself.
For production agent workflows, the official server is the right choice. Meta controls the Marketing API; they control the server. A community fork adds a maintenance dependency that breaks silently when the API changes.
Next Step
Wire the Meta Ads MCP Server into your client using the commands above, then confirm all 29 tools appear before building any workflow logic around them. Once the connection is verified, pair it with a general-purpose MCP server from moltlinestudio.com/servers.html to give your agent reach beyond the Meta Ads surface — no extra accounts required for the free tier.