Set Up the Official Meta Ads MCP (mcp.facebook.com/ads)

TL;DR

Yes, mcp.facebook.com/ads is Meta's official Ads AI Connectors MCP endpoint, launched 29 April 2026. Paste the URL into your AI tool's MCP settings and authorize with Meta through OAuth. No developer app or code is required, and for an already-enabled account the connection usually takes about 15 minutes. It works with MCP-capable tools like Claude and ChatGPT; support in other clients such as Cursor varies, and Meta also ships an Ads CLI for tools without an MCP interface. Meta owns the endpoint itself; this guide is the setup-and-fix companion that walks you through connecting it and clearing the common rollout error. For the concept behind it, see what the Facebook Ads MCP is.

AI Tool (Claude / ChatGPT / Cursor)
        |
        v
mcp.facebook.com/ads        <- official Meta MCP endpoint
        |
        v
OAuth authentication
        |
        v
Business Manager
        |
        v
Meta ad account
        |
        v
Read access
        |
        v
Write access (ads_management)

Who Should Use This Guide?

This guide is for advertisers, agencies, freelancers, and technical marketers who want to connect an AI tool to a Meta ad account they already manage.

It is not for API developers or people building their own MCP server. Those readers should start with Meta's Marketing API documentation instead, because this walkthrough covers connecting to Meta's ready-made endpoint, not building against the raw API.

What Do You Need Before Setting Up mcp.facebook.com/ads?

You need four things in place before mcp.facebook.com/ads will connect and return data.

• A Meta ad account you have access to, with a role in Business Manager (advertiser or admin). The MCP inherits whatever permissions your Meta login already has.
• An MCP-capable AI tool, such as Claude Desktop or ChatGPT with connector support. The endpoint is a remote server that follows the Model Context Protocol specification. MCP support is still uneven across tools, so confirm your client accepts a remote MCP server URL, and use Meta's Ads CLI instead if it does not.
• The ads_management permission if you want to make changes, not just read. This is the same Meta Marketing API permission that governs write access to campaigns, so the MCP inherits Meta's existing permission model rather than defining its own. Read-only access works with lighter scopes; write actions require ads_management.
• The MCP feature rolled out to your account. Meta is releasing this in phases, reportedly to US and higher-spend accounts first. Accounts that do not yet have access have reported an is_ads_mcp_enabled: false state.

If all four are true, setup takes one pass. If the feature has not reached your account yet, see the troubleshooting section below.

How to Set Up the Official Meta Ads MCP in 5 Steps

What a successful first response looks like

When the connection is working, your AI tool returns live account data rather than a generic message. A read on your campaigns should surface fields like these:

Campaign name
Status (active / paused)
Daily budget
Objective
Spend

If you get campaign names and spend figures back, the endpoint is authenticated and reading your account correctly. If you get an apology or an empty list, the connection likely has a permission or rollout issue, covered in troubleshooting below.

Verify Your Setup

Before using the MCP for live work, confirm each of these:

• The AI tool can list your campaigns by name.
• Campaign IDs are returned, not just labels.
• Spend and budget metrics are visible.
• You are connected to the intended Business Manager, not another one on your login.
• ads_management is granted, if you plan to make changes.
• A paused test action succeeds and can be reversed.

How Do You Verify Write Permissions Safely?

Read access and write access are separate. Confirm reads work first, then test writes on something reversible before trusting the connection with live budgets. The safe sequence:

Read-only test
    -> List campaigns
    -> Read spend metrics
    -> Pause one low-risk ad set
    -> Restore that ad set
    -> Write access confirmed

How Do You Set Up the Official Meta MCP in Claude, ChatGPT, and Cursor?

The endpoint mcp.facebook.com/ads is identical in every tool. Only where you paste it and how you reach the OAuth screen changes. Menu labels shift slightly as each tool updates its interface, so match on the nearest equivalent if a name differs.

Connect Meta Ads MCP to Claude

1. Open Claude and go to Settings, then Connectors.
2. Click Add custom connector.
3. Give it a clear name, such as Meta Ads.
4. Paste the server URL https://mcp.facebook.com/ads.
5. Click Add, then click the new connector to begin authorization.
6. Sign in through Facebook Login and select the business portfolios or ad accounts you want connected.
7. Open a new chat, click +, then Connectors, and confirm the Meta Ads connector is toggled on for that conversation.
8. Ask Claude to summarize my active campaigns. Live data confirms the connection is working.

Connect Meta Ads MCP to ChatGPT

1. Use a ChatGPT plan that supports connectors or custom MCP servers.
2. Open Settings, then the Connectors or MCP area.
3. Choose to add a new remote MCP server.
4. Paste https://mcp.facebook.com/ads as the server URL and save.
5. Complete the Meta OAuth step in the window that opens, then select your ad account.
6. Start a new chat and enable the Meta Ads connector for that conversation.
7. Test it with a prompt such as list my three most recent campaigns and their status.

Connect Meta Ads MCP to Cursor

1. Open Cursor's MCP configuration (Settings, then MCP, or edit the mcp.json file directly).
2. Add a new server entry pointing to the endpoint, as shown below.
3. Save the configuration and reload Cursor if prompted.
4. Trigger the connection. Cursor opens the Meta OAuth flow on first use.
5. Sign in and select your ad account to authorize.
6. The Meta Ads tools now appear to the Cursor agent. Test with a campaign-summary request.

{
  "mcpServers": {
    "meta-ads": {
      "url": "https://mcp.facebook.com/ads"
    }
  }
}

Other MCP-capable clients follow the same pattern: add https://mcp.facebook.com/ads as a remote MCP server, then complete Meta OAuth. Support is uneven, though, so a tool that does not expose a remote MCP server field will not connect this way. Use Meta's Ads CLI for those.

Troubleshooting: Why the Setup Won't Connect

Most setup failures map to one of the named causes below. Find your symptom in the table, then use the dedicated guide for the fix.

Which fix do you need? A quick decision path

Connection failed?
  -> Did the OAuth window open and complete?
       No  -> OAuth troubleshooting
       Yes -> Did a campaign read return data?
                No  -> Check token expiry, Business Manager, permissions
                Yes -> Do write actions work?
                         No  -> Grant ads_management
                         Yes -> Connected successfully

is_ads_mcp_enabled: false points to Meta's phased rollout not reaching your account yet. Users report it as a server-side rollout state, not something you misconfigured, and you cannot force it on.

To check your status, look for the Ads AI Connectors option inside Business Manager. If it is absent, your account is likely still in the rollout queue. Meta is releasing the feature by region and account tier, so newer or smaller accounts may see it later than established ones.

There is no manual override and no support ticket that reliably speeds it up. Recheck every few days. If you need access before the rollout reaches you, a managed server that has completed Meta App Review may be able to connect through its own approved app rather than the per-account flag; see the Meta Ads MCP alternatives guide for that path.

For the full catalog of connector behaviors and edge cases beyond setup, see known fixes and what works.

Before Contacting Meta Support

Run through this list first. Most connection failures trace back to one of these, and clearing them resolves the issue without a support ticket:

• OAuth completed and you selected an account.
• You are on the correct Business Manager.
• You are on the intended ad account.
• ads_management is granted, if you need write access.
• The token is under roughly 60 days old.
• is_ads_mcp_enabled is true for your account.

If all six are true and the connection still fails, the issue is likely server-side, and waiting or re-authorizing is usually the only remedy.

Common Setup Mistakes to Avoid

• Adding a trailing slash or extra path to mcp.facebook.com/ads instead of pasting the endpoint exactly.
• Authorizing the wrong Business Manager when several sit under one login.
• Testing write actions on a live campaign before confirming reads work.
• Skipping the ads_management scope and then wondering why write actions fail.

What Are the Limits and Risks to Know?

A working connection is not the whole picture. Keep these constraints in mind before you rely on it for live work.

• Write actions are live and hard to undo. The endpoint can create campaigns, change budgets, and pause ads directly on your account, and there is generally no draft mode or one-click undo. Confirm each change, and keep a human in the loop for anything that moves real money.
• Meta enforces API rate limits. Requests run against the same Marketing API throttling as any integration, so heavy or rapid actions can be slowed or temporarily blocked. Space out bulk changes.
• Reported data lags. Attribution and spend figures settle over hours, and conversions can keep attributing over a multi-day window, so a number the AI reads now is not final. Treat same-day figures as provisional.
• Platform policy still applies. The MCP does not bypass ad review, spending limits, or policy enforcement. A change the AI makes can still be rejected or flagged by Meta's normal checks.

Because these are ad-account actions, treat the AI's output as a strong draft to review, not a final decision. When a read looks off, it is more likely a latency or permission issue than a confirmed account change.

After Setup: Official Endpoint or a Managed Server?

Once you are connected, the choice is between running the raw endpoint yourself or letting a managed server handle it.

mcp.facebook.com/ads gives you raw, Meta-authenticated access. You own the OAuth connection, you handle the roughly 60-day token refresh, and you get exactly the tools Meta ships. It is the right choice when you want to connect an AI tool to your own account and run reads and simple changes yourself. Neither path asks you to complete Meta App Review for an account you already manage.

A managed server sits on top of that access. The AdAdvisor MCP, for example, has completed Meta App Review, adds optimization logic on top of the connection, and removes the token-maintenance chore so the link does not silently go stale. It brings 8 years in paid ads and more than $60M in managed ad spend to that layer, built by an ex-Meta engineer who shipped products inside the ads stack.

This guide stays on setup, so it does not rank the options here. For the full picture, see the best Meta Ads MCP servers ranking, or the head-to-head Meta MCP vs AdAdvisor breakdown.

Frequently Asked Questions

Summary

To set up the official Meta Ads MCP, paste mcp.facebook.com/ads into your AI tool's MCP settings, authorize with Meta through OAuth, and grant ads_management for write access. If you hit is_ads_mcp_enabled: false, your account is waiting on Meta's phased rollout. For the concept, see what the Facebook Ads MCP is; to compare servers, see the best Meta Ads MCP servers guide.

Sources

• Model Context Protocol specification: modelcontextprotocol.io
• Meta Marketing API authorization and permissions: developers.facebook.com/docs/marketing-apis
• Meta System User access tokens: developers.facebook.com/docs/marketing-api/system-users