All posts

Meta Ads MCP: What It Does and How to Connect It Safely

Meta Ads MCP: What It Does and How to Connect It Safely

META TITLE: Meta Ads MCP: What It Does and How to Connect

META DESCRIPTION: Meta Ads MCP connects an AI agent to your ad account. What the official server does, the seven scopes it requests, and how to connect it safely.

SLUG: meta-ads-mcp

TAGS: Meta Ads, MCP, Model Context Protocol, Claude, Facebook Ads, ad account security, Google Ads MCP

Meta Ads MCP connects an AI agent directly to your Meta advertising account. MCP is an open-source standard for linking AI applications to external systems. Meta hosts an official server at `mcp.facebook.com/ads` that reads reporting and also writes campaigns.

A safe setup means a narrow scope set and a human approving every write. An unsafe one means a broad token handed to an agent with no review step.

This guide covers what the official server does and the seven scopes it requests. You also get the Claude Code connect command, a Google comparison, and when read-only fits.

What the Meta Ads MCP Server Is

Model Context Protocol is an open-source standard for connecting AI applications to external systems. An ads MCP server applies that standard to an advertising account.

The Official Meta Ads MCP Endpoint

Only one official server exists, and Meta runs it. Meta's own documentation describes a Meta-hosted server that manages Meta ads from an AI agent. It sits at `mcp.facebook.com/ads` and is remote-hosted, so nothing runs on your machine.

Owning a Meta app is not a prerequisite, according to the same get-started page. Meta opened the server in beta on 29 April 2026.

General developer availability followed on 16 July 2026, announced on Meta's developer blog. Compatibility is described as broad: any MCP-compatible AI agent, through structured, permission-scoped tools.

What the Meta Ads MCP Server Can Do

Reading is only half of it. Creating and editing ads, ad sets and campaigns all appear on Meta's overview page. That makes this a write-capable connection. Meta lists seven capability areas on that page, all of them vendor claims:

Alongside the server, Meta ships an Ads CLI, a command-line tool for managing Meta advertising from your terminal. Same account, different surface. Pick whichever matches how your team already works.

Facebook Ads MCP vs Meta Ads MCP

Search demand splits across two names. People type "facebook ads MCP" and "meta ads MCP", and both phrases point at the same server. Look at the endpoint itself, where `mcp.facebook.com/ads` still carries the older brand name in the hostname.

If you came looking for a Facebook Ads MCP setup, this is it. There is no second product hiding behind the other spelling. Our roundup of MCP servers for marketing treats them as one entry for the same reason.

How to Connect the Meta Ads MCP

Permissions the Meta Ads MCP Requests

Meta's get-started documentation names seven scopes, listed as the permissions to grant when generating the token:

That set spans reading, writing, catalogs, business assets and Instagram. Read the list before you approve it, because approval is where most of your risk gets decided.

Authentication Options for the Meta Ads MCP

Authentication runs two ways. Your MCP client can redirect you to the Facebook Login for Business dialog, which is the OAuth route. Alternatively, pass a user access token to the ads MCP server in the Authorization: Bearer header.

Bearer tokens are convenient and easy to leak. Keep them out of shared repositories, screenshots and chat logs.

Connecting Claude Code to the Meta Ads MCP

Setup takes one documented command:

claude mcp add --transport http --client-id <META_APP_ID> meta-ads https://mcp.facebook.com/ads

Swap in your own app ID. Anthropic's support documentation lists custom connectors using remote MCP on Claude, Cowork and Claude Desktop.

Free, Pro, Max, Team and Enterprise plans all qualify. One custom connector is the limit on the Free plan, so choose that slot carefully. Our step-by-step Claude setup guide walks through the same flow for both ad platforms.

Meta Ads MCP Agency Access and App Review

Acting on behalf of other businesses changes the process. Agencies must submit the app for review and request Advanced Access on the ads_mcp_management permission, per Meta's launch post. Budget time for that before promising a client a live connection this week.

Meta Ads MCP vs Google Ads MCP

Both platforms now ship a server. They are not equivalent in what an agent is allowed to do.

What Google's Ads MCP Server Exposes

Google open-sourced its Google Ads API MCP server on 7 October 2025. That server exposes three retrieval tools and no create or update tools. Our roundup of MCP servers for marketing lists them in full.

Read Access vs Write Access

That difference decides your risk posture. On the Meta side, ads_read sits in the same approval prompt as ads_management and catalog_management. One click covers reporting and structural editing together. Meta's documented list is a single set of seven scopes, not a read tier and a write tier.

Google's README carries a blunt warning: the MCP server will expose your data to the agent or LLM you connect to it. Nothing in either vendor's documentation promises the agent will behave. Your controls have to do that work.

Safety Rules for a Write-Capable Ads MCP

Human Approval for Ads MCP Writes

MCP tools are model-controlled by design. Specification language says the model can discover and invoke tools automatically, based on context and user prompts. Nobody types "call the campaign editor" first.

Balancing that, the same specification states there should always be a human in the loop with the ability to deny tool invocations. Clients should also show tool inputs to the user before calling the server, to avoid data exfiltration. Applied to an ad account, that means reading the proposed change before it ships.

Least Privilege for Ads MCP Scopes

Security guidance in the specification says to start from a minimal scope set of low-risk discovery and read operations. Wildcard or omnibus scopes are named as a common mistake. Stolen broad tokens expand the blast radius, enabling unrelated tool and resource access.

In practice, if you only need analysis, do not connect a server that can spend money. Anthropic's guidance says to connect only services you trust and need, and to review authentication permissions carefully. Even when you allow a write action in Claude, a person still needs the underlying permission in the source system.

A Read-Only Meta Ads MCP Option

Analysis without write access is a legitimate middle ground, and it is the right default for most merchants. Reporting questions are constant. Structural campaign edits are not.

What Agency AI's MCP Connector Does

Agency AI positions it as the Meta and Google Ads MCP for Shopify. Its own page says the connector reads and explains, producing analysis, plans and clear next steps. It cannot spend money or change your ads. Tools, availability and approval behaviour are covered in our step-by-step Claude setup guide.

A published case study reports Lolahemp's Meta cost per purchase at $143.75 from 1 August to 30 September 2025, across 33 purchases.

It reached $63.56 from 10 October to 6 November 2025, per Agency AI's own write-up. Single store, two short windows, so do not read it as a product performance claim. For the broader workflow around it, see our guide to automating Facebook ads for Shopify.

Frequently Asked Questions

Is Facebook Ads MCP Different From Meta Ads MCP?
No. Both names describe the same connection, and Meta's own endpoint still uses a facebook.com hostname. Treat them as one page and one setup.
Can the Official Meta Ads MCP Server Change My Campaigns?
Yes. Meta's overview page documents creating and editing ads, ad sets and campaigns. Treat it as a write-capable server, not a reporting tool.
Do I Need a Meta App to Use the Ads MCP Server?
Not for your own account. Documentation states that owning a Meta app is not a prerequisite. Agencies acting for other businesses do need app review plus Advanced Access on ads_mcp_management.
What Permissions Does the Meta Ads MCP Require?
Seven scopes, per Meta's get-started page: ads_mcp_management, ads_read, ads_management, catalog_management, business_management, pages_show_list and instagram_basic.
Is Google's Ads MCP Server the Same as Meta's?
No. Google's published tool list contains three retrieval tools and no create or update tools. Meta's documented capabilities include writes.
How Much Does the Agency AI MCP Connector Cost?
Agency AI lists current pricing for the connector on its own MCP page. Check there before you sign up, because the figure is a separate line from the Shopify app subscription.

Sources

Most of this article comes from two pages on developers.facebook.com: the ads MCP server overview and its get-started guide. Endpoint, capability areas, permission scopes, authentication and the Claude Code command all come from there. A developer blog post there, dated 16 July 2026, supplied the announcement date and the agency app-review requirement. The 29 April 2026 beta date comes from our own roundup of MCP servers for marketing. Terminal tooling comes from the Ads CLI overview page on the same domain.

For Google, the googleads/google-ads-mcp repository on GitHub provided the three published tools and the data-exposure warning. The Google Ads Developer Blog post dated 7 October 2025 gave the open-source announcement date.

Protocol behaviour came from modelcontextprotocol.io. Model-controlled invocation and human-in-the-loop language come from the server tools specification, and least-privilege scoping from the current security best practices page. Anthropic's support articles on custom connectors and connector capabilities cover plan availability and the underlying-permission rule.

Product details for Agency AI came from its own MCP page and its published Lolahemp case study.

Free to install. Launch campaigns and pay nothing for your first 30 days.

Download Agency AI free on the Shopify App Store