Pipeboard
Meta ads MCP troubleshooting

Meta Ads MCP not working?

Meta runs its own ads MCP server at mcp.facebook.com/ads. When an AI client cannot connect to it, or connects but cannot use an ad account, it shows one of the errors below. Find yours to see what it means and what to do.

This page is about Meta’s own server. It is not about Pipeboard’s meta-ads-mcp project, which runs on the standard Meta Marketing API and does not return these errors.

Find your error

Meta’s help center lists four AI clients for this server: ChatGPT, Claude, Claude Code and Perplexity. All use the same URL, https://mcp.facebook.com/ads. Any other client needs a Meta developer app of your own.

Checked against Meta’s documentation and public bug reports on 15 October 2026.

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

The login worked. Meta’s ads MCP server is in open beta, and Meta turns it on one ad account at a time. This account is not on yet. It is not a permissions problem, and nothing on your side can switch it on. As of October 2026, Meta still says not everyone has access yet and has not given a date.

The order is hard to predict. Accounts in the same business often differ: people report idle accounts enabled while their main, high-spend account still waits.

What to do

  1. See which of your accounts are enabled in Meta Business Suite > Settings > Integrations > Ads MCP server. Accounts that are on list the actions agents may take; accounts still waiting show a dash. This page sets rules for agents. It cannot turn access on.
  2. If Ads MCP server is missing from that menu, Meta has not given your business access to the feature yet.
  3. If one of your accounts is enabled, ask the agent to work in that one.
  4. Keep the connector installed and try again later. Nothing breaks when Meta turns the account on.
  5. If you need the account now, use an MCP server that does not wait on Meta: see below.

The Facebook profile cannot reach the ad account

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

What it means

Meta does not document this message. The reports we found tie it to the Facebook profile used to log in: either it is the wrong profile, or it has no role on the ad account that lets it manage ads.

What to do

  1. Disconnect, connect again, and check which Facebook profile the login screen uses.
  2. In your business portfolio settings, check that this person has access to the ad account that includes managing campaigns. View-only access may not be enough.
  3. If the account belongs to a client’s business, ask its admin to give you that access, or to connect the account themselves.
  4. If the profile and access are right, check Meta Business Suite > Settings > Integrations > Ads MCP server to see whether the account is enabled yet.

We could not confirm the cause in Meta’s documentation. Treat this as the most likely explanation, not a certain one.

Your AI client is not on Meta’s list

invalid_client_metadata
Dynamic registration is not available for this client.

What it means

The first time an MCP client connects to a server, it usually registers itself on the spot (OAuth dynamic client registration). Meta’s server accepts that only from the clients it supports. It checks the address the login sends you back to after you approve (the redirect URL).

Claude and ChatGPT pass. Clients that come back to a local or app address — Cursor, Codex, mcp-remote and most desktop tools — get this error. invalid_client_metadata is the standard OAuth code for “the server rejected the details this client registered with”.

What to do

  1. Use one of the clients Meta supports: ChatGPT, Claude, Claude Code or Perplexity, with the server URL https://mcp.facebook.com/ads.
  2. Or connect with your own Meta app and give its app ID to your client as the OAuth client ID.
  3. Or use an MCP server that works in any client: see below.

The Meta app does not list your client’s return address

The provided redirect_uris are not registered for this client.

What it means

Your client logged in with a client ID — a Meta app — whose settings do not include the address the client wants Meta to send you back to after login. Claude Code users hit this in April and May 2026. Meta now lists Claude Code as supported, and setups that pass their own Meta app ID work.

What to do

  1. Follow the steps to connect with your own Meta app below.
  2. Add the exact redirect URL your client uses in the app’s Facebook Login for Business settings. It has to match character for character.
  3. If your client returns to an http://localhost address, keep the Meta app in Development mode. A live Meta app refuses localhost addresses, and in Development mode only people with a role on the app can log in.

Claude could not register with Meta

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’s registration with Meta failed. In the one public report (October 2026), the same server worked from a new Claude account and from Claude Code. That points to an old connector record on the account, not a problem on Meta’s side.

What to do

  1. Remove the connector, then add it again with the URL https://mcp.facebook.com/ads.
  2. If it still fails, connect with your own Meta app and enter its app ID as the OAuth Client ID in the connector’s advanced settings.
  3. Or connect from Claude Code instead.

Connected, but it still does not work

It asks you to log in again

Meta’s login lasts about 60 days, and Meta does not give clients a token to renew it. When it expires, reconnect.

An action is denied

A business admin can block actions per ad account, such as creating campaigns or setting budgets above a limit, in Meta Business Suite > Settings > Integrations > Ads MCP server. “Limited” next to an account means some actions are blocked. Ask the admin which ones.

An ad account is missing

During the Meta login you choose which ad accounts to share. Reconnect and select the missing account.

405 Method Not Allowed, or a 400 when connecting

The server only accepts the Streamable HTTP transport. Older clients that open an SSE stream, or send requests the server cannot parse, fail here. Update the client, or use one Meta supports.

The ads were created but are not running

Meta creates every ad paused. Review it in Ads Manager and set it live yourself.

Connect with your own Meta app

This is how clients outside Meta’s list connect, and how you fix registration and redirect errors. You do not need it for ChatGPT, Claude, Claude Code or Perplexity on their default setup.

  1. Create or open an app at developers.facebook.com/apps and add the use case “Create & manage ads with ads MCP server”.
  2. In the app’s Facebook Login for Business settings, add the redirect URL your AI client uses.
  3. Claude Code: run this command.
    claude mcp add --transport http --client-id <META_APP_ID> meta-ads https://mcp.facebook.com/ads
  4. ChatGPT: choose OAuth as the authentication method, enter https://mcp.facebook.com/ads as the server URL, and enter your app ID as the OAuth Client ID in the advanced OAuth settings.
  5. Scripts and servers can skip the login and send a user or system user access token in the Authorization: Bearer header. The token needs ads_mcp_management plus ads_read or ads_management. Only Employee-role system users work.

If the app will manage other businesses’ ad accounts, it also needs Advanced Access to ads_mcp_management through Meta’s App Review. Source: Meta’s Get started guide.

If you cannot wait

Use Pipeboard on any account you can manage

Pipeboard is a separate MCP server. It reaches Meta through the standard Marketing API, so it does not depend on Meta’s rollout or on its list of clients. If you can manage an ad account in Ads Manager, Pipeboard can manage it from your AI client.

Sign up, connect the same Facebook login you use for Ads Manager, and paste the MCP URL Pipeboard gives you into Claude, ChatGPT, Cursor, Windsurf or Claude Code.

FeatureMeta’s ads MCP servermcp.facebook.com/adsPipeboard
Works on every ad account you can manageOpen beta, not every account
ChatGPT, Claude and Claude Code
Cursor, Windsurf and other MCP clients, without your own Meta app
Google, TikTok, Snap and Reddit ads
Source code on GitHub
Free to start

Comparison as of October 2026.

Watch: Meta’s connector or Pipeboard, set up in minutes

Frequently asked questions

Is it safe to connect my ad account to Meta’s ads MCP server?

Meta says so: “it’s unlikely that an account would be banned simply for using it.” Bans come from breaking Meta’s advertising policies, not from the connection.

When will Meta enable my ad account?

Meta has not said. The server is in open beta, access is rolling out gradually, and Meta offers no date and no way to ask for it.

Can I use Meta’s server and Pipeboard together?

Yes. They are separate connections. Keep Meta’s connector for the accounts it covers and use Pipeboard for the rest.

How does Pipeboard reach Meta if not through mcp.facebook.com?

Through the standard Meta Marketing API, the same API ad tools have used for years. It needs only your normal access to the ad account. Pipeboard is a Badged Meta Business Partner.

Is there a free plan?

Yes. It includes 30 AI tool executions a week and 2 ad accounts, with no credit card. See pricing for paid plans.

Sources