Meta Ads MCP Not Working? Errors Explained and Fixed

Meta's official Ads MCP server, at https://mcp.facebook.com/ads, lets AI apps like Claude and ChatGPT work with your ad account directly. It's free and in open beta, which also means it doesn't work for everyone yet. This page goes through the error messages people run into, what each one actually means, and what you can do about it. Most of these fixes don't involve AdChat at all. If you just want something that works today, there's a short section at the end.

Find your error

Your ad account is not enabled yet

is_ads_mcp_enabled: false

Ads MCP is gradually being rolled out. Please check back at a later date to use Ads MCP with this Ad Account.

What it means: your login worked, but Meta hasn't switched on the Ads MCP for this particular ad account. Meta is releasing it gradually, account by account, and hasn't published a schedule. Nothing is wrong with your setup.

What to do:

• Check other accounts. If you manage several ad accounts, ask about a different one. Availability is per account, so another may already be enabled.
• Look in Business Suite. Meta's help center says that if you don't see Ads MCP server under Settings, then Integrations, in Meta Business Suite, you don't have access to the feature yet.
• Wait and retry. There's no form to request access and no way to speed it up. Try again every week or so.
• Use a Marketing API tool meanwhile. Third-party MCP servers built on Meta's standard Marketing API don't depend on this rollout. More on that below.

Wrong Facebook profile or no access

You can't connect to Ads MCP server with this account.

What it means: the Facebook profile you logged in with can't reach the ad account. Usually you're logged in to the wrong profile in your browser (a personal profile instead of a work one), or your profile has no role on the ad account.

What to do:

1. Open facebook.com in the same browser and check which profile is logged in. Log out and back in with the right one if needed.
2. Open Ads Manager with that profile. If you can't see the ad account there, you don't have a role on it.
3. Ask the business admin to give you access to the ad account in Meta Business Suite.
4. Remove the connector in your AI app and connect again.

Your AI app is not supported

invalid_client_metadata

Dynamic registration is not available for this client.

What it means: when you add a remote MCP server, many AI apps try to register themselves automatically with the server's login system. Meta only allows this for the apps it supports. Its help center lists ChatGPT, Claude, Claude Code and Perplexity. Other apps, such as Cursor, Codex and desktop tools that use local redirect addresses, are turned away with this error.

What to do:

• Use a supported app if you can. ChatGPT, Claude, Claude Code and Perplexity are the documented options.
• Bring your own Meta app. Meta's developer docs explain how to create your own Meta developer app and pass its app ID as the OAuth client ID. In Claude Code, that looks like:

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

For other apps, look for an "OAuth client ID" field in the connector's advanced settings. This route takes some developer setup, and your Meta app also needs the right redirect URL (see the next error).

Redirect URL mismatch

The provided redirect_uris are not registered for this client.

What it means: you're using your own Meta developer app, but its settings don't include the exact web address your AI app sends you back to after login. Meta rejects any return address it doesn't recognize.

What to do: find the redirect URL your AI app uses (check its documentation, or the error details), then add that exact URL in your Meta app's Facebook Login for Business settings. Meta's docs note this must match your chosen client; for ChatGPT, follow OpenAI's specification. Small differences, such as a trailing slash or http versus https, count as a mismatch.

Claude cannot register

Couldn't register with Meta's login service. You can try again or add an OAuth Client ID in the connector settings.

What it means: Claude tried to register with Meta's login and it didn't go through. Claude is on Meta's supported list, so this is often a hiccup with the saved connector rather than a hard block.

What to do:

1. Remove the Meta connector from Claude completely.
2. Add it again with the URL https://mcp.facebook.com/ads and log in.
3. If it keeps failing, do what the message suggests: create your own Meta developer app and enter its app ID as the OAuth Client ID in the connector's advanced settings.

Connected but not working

Your login expired. Meta's login for the Ads MCP lasts about 60 days. After that, requests fail until you reconnect. Remove and re-add the connector, or use your app's reconnect button.

Actions are denied. If reading works but creating campaigns or changing budgets is refused, a business admin may have blocked those actions. Admins with full control of a business portfolio can allow or block specific actions per ad account in Meta Business Suite under Settings, then Integrations, then Ads MCP server. Meta shows Limited next to "Take actions in this ad account" when something is blocked. Ask your admin to check.

An ad account is missing. The AI can only see accounts your Facebook profile has a role on. Check in Ads Manager, and ask for access if needed.

Your new ads aren't running. That's by design. Meta creates ads paused, so you review them before they spend money. Turn them on in Ads Manager or ask the AI to activate them.

If you can't wait: use AdChat on any ad account

If your account isn't enabled yet, or your AI app isn't on Meta's list, a third-party MCP server can fill the gap. AdChat is one option. It's an approved Meta app that uses Meta's standard Marketing API, so it works on any ad account you can manage in Ads Manager, with no rollout to wait for.

Meta's server is free and has extras AdChat doesn't, like catalog tools and per-account admin rules. You can use both: AdChat now, and Meta's server once your account is enabled. See the full AdChat vs Meta Ads MCP comparison, or start a free trial.

FAQ

When will Meta enable the Ads MCP on my ad account?

Meta hasn't published dates. It's rolling out gradually per ad account, so the only way to know is to try again later.

Can I ask Meta to enable my account sooner?

There's no documented way to request early access. Accounts are enabled on Meta's schedule.

Is it safe to connect my ad account to Meta's Ads MCP?

It's Meta's own service, ads are created paused, and admins can block specific actions per account. As with any AI tool, review changes before turning anything on.

Why does Cursor fail with "Dynamic registration is not available"?

Cursor isn't on Meta's supported list, so automatic registration is refused. Either create your own Meta developer app and use its app ID as the OAuth client ID, or use an MCP server that supports Cursor directly.

Can I use Meta's Ads MCP and AdChat together?

Yes. They're separate connections and don't interfere with each other. Just say in your prompt which one you want to use.

Sources

• Meta, "Introducing Meta Ads AI Connectors" (April 29, 2026, updated July 16, 2026): https://www.facebook.com/business/news/meta-ads-ai-connectors
• Meta Business Help Center, "Manage ads from an AI agent with Meta ads AI connectors": https://www.facebook.com/business/help/1456422242197840
• Meta for Developers, "Ads MCP server: Get started": https://developers.facebook.com/documentation/ads-commerce/ads-ai-connectors/ads-mcp-server/ads-mcp-server-get-started

Want something that works on your account today? Try AdChat free for 7 days. Sign up. Questions? Email [email protected].