Meta Ads MCP Not Working? Common Errors and Fixes (2026)

Most Meta Ads MCP problems come down to three things: the wrong auth option, the wrong server URL, or an ad account that is not in the beta yet. Fix those and the connection works. The server URL is https://mcp.facebook.com/adsCopyCopied, the auth is always OAuth, and you log in with a Facebook profile that has admin or advertiser access to the ad account.

Below are the exact errors people hit and what fixes each one. If you have not connected yet, start with the Meta MCP setup guide and come back here if something breaks.

Nine times out of ten, one of these is off:

• The URL is exactly https://mcp.facebook.com/adsCopyCopied. No trailing slash, no wwwCopyCopied, no typos.
• Auth is set to OAuth, not No Auth or Mixed.
• You logged in with a Facebook profile that has admin or advertiser access to the ad account.
• Your AI plan can add custom connectors. Claude allows one on the Free plan and more on paid plans. ChatGPT needs developer mode, which OpenAI lists for Pro, Plus, Business, Enterprise and Education on the web.
• During the Meta login, you granted access to the specific ad account you want to query.

If all five are right and it still fails, find your exact error below.

This one is about permissions, not the URL. Meta is telling you the Facebook profile you logged in with does not have the right access to the ad account, or you picked the wrong profile during login.

Fix it:

1. 1.When the message offers to choose a different account, do it. Pick the profile that actually manages the ad account.
2. 2.If you only have one profile, check your role. Open Meta Business Manager, go to the ad account, and confirm you are an admin or advertiser. A "viewer" or "analyst" role is not enough to connect.
3. 3.Ask the account owner to bump your role if you are stuck on viewer access.

Personal ad accounts created under a personal profile usually work. The trouble is almost always shared or agency accounts where your role is too limited.

The connector is live, but it cannot see your ad account. Two usual causes:

• You picked No Auth instead of OAuth. No Auth means no login happened, so Meta has no idea who you are. Delete the connector and recreate it with OAuth.
• You skipped the ad account during the grant step. OAuth ran, but you did not tick the ad account you want. Redo the login and approve the right account.

After fixing, start a fresh chat and ask "What is my total spend this month?" A real number means you are in.

For the standard setup you don't. Meta's announcement says the MCP route needs no developer credentials, API setup or coding, and its server advertises dynamic client registration, which lets compatible clients register themselves. You pick OAuth and log in through the popup.

There is one documented exception. Meta's developer docs also describe connecting with your own Meta app, and in that route you enter the app ID as the OAuth client ID (Claude Code uses --client-idCopyCopied, and ChatGPT has an Advanced OAuth Settings field). If a client refuses to continue without a client ID, that is the route to use: create an app at developers.facebook.com/apps, add the "Create & manage ads with ads MCP server" use case, and set the redirect URL your client specifies.

If a tutorial tells you to copy a client secret or a long-lived token, it is describing the Marketing API, the Ads CLI or a third-party server, not Meta's chat connector.

The MCP is in open beta, and Meta is rolling it out in waves. Some accounts and regions are not switched on yet. There is no public date for general availability.

If you cannot find it or the login dead-ends:

• Confirm you have admin access to a real ad account with spend history. Brand-new accounts are more likely to be gated.
• Try a different ad account under the same Business Manager.
• Wait a few days and try again. Beta access genuinely appears later for some accounts.

There is no waitlist button to press. Access shows up on Meta's schedule, not yours.

Meta's developer docs list uploading creatives as part of ad creation, but they do not say how a file gets from your chat into the account, so do not count on attaching a file in the chat.

What to do:

1. 1.Upload the creative in Ads Manager or the asset library first.
2. 2.Then ask the MCP to build the campaign or ad set and attach that existing creative.
3. 3.Confirm the result in Ads Manager. Meta says new campaigns, ad sets and ads are created paused, so nothing spends until you activate them.

Write actions can also be flaky in beta. If a launch or edit stalls, check Ads Manager to see what actually happened before you retry. Running the same command twice can create duplicates.

ChatGPT needs one extra switch that Claude does not. If the app will not save or connect:

• Developer mode is off. In ChatGPT on the web, open Settings, then Security and login, and turn on Developer mode. Without it, you cannot create a custom MCP app. On Business plans only workspace admins and owners can enable it, and on Enterprise and Edu an admin has to grant access first.
• You are on mobile. OpenAI says MCP apps are web only.
• You created the app without OAuth. Recreate it and set Authentication to OAuth.
• You skipped the risk checkbox. ChatGPT will not finish the app until you tick "I understand and want to continue."

When you have tried the fixes and it is still broken, a clean reset clears most ghost states:

1. 1.Remove the connector or app from Claude or ChatGPT.
2. 2.Log out of the Meta account in your browser, or open a private window.
3. 3.Add the connector again with the URL https://mcp.facebook.com/adsCopyCopied and OAuth.
4. 4.Log in fresh and grant the ad account.

A stale or half-finished OAuth session is a common reason a connector looks added but never responds.

What is the Meta Ads MCP server URL? The server URL is https://mcp.facebook.com/adsCopyCopied. Use it exactly, with no trailing slash. Paste it into Claude as a custom connector or into ChatGPT as a custom app with OAuth.

Do I need a Meta developer app or API keys for the MCP? Not for the standard setup. The MCP uses a hosted OAuth login and Meta's announcement says no developer credentials are needed. If your client insists on an OAuth client ID, Meta documents a route that uses your own Meta app's ID. If a guide asks for a client secret or a long-lived token, it is describing the Marketing API, the CLI or a third-party server.

Why does it say I can't connect with this account? Your Facebook profile does not have admin or advertiser access to that ad account, or you chose the wrong profile. Pick the correct profile, or fix your role in Business Manager.

When will my ad account get MCP access? There is no public date. The MCP is in open beta and rolling out in waves. Confirm you have admin access to an established ad account, try a different account, and check back in a few days.

Can the MCP upload and launch a brand-new creative? Meta's developer docs list uploading creatives as part of ad creation, but they do not describe uploading a file from the chat. The safe route is to upload the asset in Ads Manager first, then ask the MCP to build the ad with it. It does not design or write the creative, and new ads are created paused.

The connector shows as added but does nothing. What now? Remove it, clear your Meta login in a private window, then re-add it with https://mcp.facebook.com/adsCopyCopied and OAuth. A half-finished OAuth session is the usual cause.