What is Meta Ads MCP, and how do you use it?

Updated November 14, 2026

Short answer: Meta Ads MCP connects an AI assistant to advertising tools through Model Context Protocol. Meta's official server is at https://mcp.facebook.com/ads; independent providers offer different servers for Meta advertising. To use one, choose a compatible assistant, add the provider's endpoint, authorize access and test a reporting request before permitting changes to real campaigns.

What MCP means in a media buyer's workflow

Model Context Protocol is a standard for connecting AI applications to external tools and data. The assistant handles the conversation; an MCP server supplies the tools it can call. In advertising, a tool might retrieve campaign performance or submit a supported edit.

Without a connection, you can supply a report for the assistant to interpret. With an authorized connection, the assistant can request data through the server. Write access is a further permission decision. The word “MCP” alone tells you little about account coverage, data freshness, supported changes or approval behavior.

Keep three names distinct when setting up:

• Client: the assistant application where you ask for work.
• Server: the provider exposing tools and enforcing its authorization.
• Advertising assets: the accounts, campaigns and other objects those permissions allow it to reach.

If a request fails, identifying the layer involved helps you avoid changing unrelated account settings.

Meta's official server and tool categories

Meta's Ads MCP overview identifies a Meta-hosted remote server for compatible AI agents. It groups tools into seven areas: reporting; ad creation and management; catalogs; signals and datasets; help and troubleshooting; A/B tests and conversion lift studies; and activity logs.

These category names describe coverage, rather than a promise that every object or field is editable. Inspect the tools available after authentication and test the exact task you require. Meta's overview does not document a universal preview-and-approval sequence for every write. Configure your client's permissions and inspect the proposed arguments before authorizing account changes.

Which Meta Ads MCP URL to use

Pipeboard's endpoint and client listings come from its Meta Ads MCP guide, as of November 2026. The endpoints connect to separate providers. Copy the complete URL, including its path, from the provider you chose.

How to get Meta Ads MCP

Meta's get-started page separates access without your own Meta app from a developer setup. It links to How to set up Meta ads AI connectors for the former. That Help Center page required login during this review, so its current non-developer steps could not be independently checked.

For the documented developer route:

1. Create or reuse a Meta developer app and add Create & manage ads with ads MCP server.
2. Choose the documented authentication method: OAuth, a user access token or a system user access token.
3. Configure the required permissions and, for OAuth, the client's redirect URL in Facebook Login for Business.
4. Add https://mcp.facebook.com/ads to the compatible client using Meta's instructions for that client.
5. Authenticate and begin with a narrowly scoped reporting request.

Meta lists ads_mcp_management plus ads_read or ads_management as minimum token permissions; more tools require additional permissions. Its system-user route supports Employee-role system users, rather than Admin-role tokens. Follow the current setup page for the full configuration instead of copying token instructions from another provider.

How to use Meta Ads MCP with Claude

First distinguish Claude's custom remote connectors from Claude Code configuration. Anthropic documents the former in its custom connector guide. Meta's developer guide includes a Claude Code command with HTTP transport and your Meta app ID. Those are different setup surfaces; use the one matching your client.

For Claude's remote-connector route, start in Customize → Connectors → Add custom connector, enter the provider's exact URL and follow its authentication requirements. A server requiring your own OAuth client needs that configuration too. Adding an endpoint alone does not finish authorization.

For Meta's non-developer route, consult its linked AI connector setup page in your own signed-in session. This guide cannot verify the current eligibility or rollout status of your ad accounts. A successful connection should be followed by a visible list of the assets you intend to use.

Make the first question easy to audit

Use one account and a completed reporting period. For example: “List campaigns in account A for yesterday. Include account ID, spend, result type, results, currency and reporting time zone. Make no changes.” This is a suggested test prompt, rather than an exact tool schema.

Compare the response with the same period in Ads Manager. Resolve missing accounts, mixed result events or date differences before asking the assistant to rank campaigns. A plausible explanation cannot compensate for an incorrectly scoped report.

For a later edit, ask for the object IDs and current and proposed values first. Approve a specific action, then inspect its returned outcome. Keep responsibility for budget and policy decisions with the buyer who owns the account.

Other servers for Meta advertising

The Multitool Ads connector connects Claude to the Multitool ADS workspace. It answers across connected ad accounts, combines results for identical creative media, reads comment inboxes and inspects Business Manager access. Workspace and permission scope are selected at connection. Advertising changes receive a preview and require your approval; the assistant never receives Meta passwords or tokens.

Pipeboard provides a separate Meta Ads MCP service with hosted and source-available server options, as described in its guide, as of November 2026. Compare the actual tools and client documentation before choosing.

For the detailed workflow comparison, read Meta Ads MCP vs Multitool Ads. You can also inspect the Multitool ADS workspace in its live demo using demo data, with no account needed.

Sources: Meta Ads MCP overview, get started and AI connector setup (login required during review); MCP introduction; Anthropic custom connectors; Pipeboard guide, as of November 2026; Multitool Ads for Claude.