Meta Ads MCP URL Not Working? Errors and Fixes

If your Meta Ads MCP connection fails, start with the URL itself, then the sign-in profile, then whether Meta has enabled your ad account. Those three checks explain most "meta ads mcp not working" reports. This guide walks through them in order, for Claude, Claude Code and ChatGPT.

MCP (Model Context Protocol) is an open standard that lets an AI assistant connect to outside tools and data. Meta's ads connector is a hosted MCP server: the assistant signs in to your Meta account and can then read, and in some cases change, your ad data. If the basics are new to you, start with the article "Meta Ads MCP: Connect Claude or ChatGPT to Your Ad Account".

A note on evidence. Meta's developer documentation covers setup, scopes and the server's purpose. Most troubleshooting fixes below come from vendor blogs and community reports, not from Meta. Several of those vendors sell competing products. Treat each fix as "reported to work", and expect details to change while the product is in beta.

What is the Meta Ads MCP URL and where do you get it?

The Meta Ads MCP server is hosted by Meta, so you do not install anything. You paste one server address into your AI client. Meta's developer documentation (the overview and get-started pages) lists that address. Sources disagreed on details in the past, so this article does not repeat it. Copy it from Meta's current documentation or the Meta Business Help Center instead of from a blog post or a forum answer.

What reports agree on:

• There is one URL for every client. No regional or per-assistant variants are reported.
• It must be exact. A trailing slash, an extra path or a copied space is listed as a common setup mistake.
• Meta also runs a separate server for developers building Meta apps (app settings, App Review, webhooks, changelog). It has no ad tools. If you pasted that address, you will connect fine and find no campaigns. This distinction comes from a vendor source, so verify it in Meta's docs.

Why does opening the URL in a browser show an error?

An error in the browser is not a sign that something is broken. Two vendor sources report an HTTP 405 in a browser and a 401 (unauthorized) when no sign-in has happened, and both call this normal. The address is built for MCP clients, not for people. The only real test is adding it to a client and completing the Facebook sign-in.

How do you connect Meta Ads MCP in Claude, Claude Code and ChatGPT?

Claude (custom connector)

1. Open Customize, then Connectors, then Add custom connector.
2. Name it and paste the exact URL from Meta's documentation.
3. Sign in with Facebook and select the business portfolios you want to share.
4. In each new chat, click "+", open Connectors and confirm the connector is toggled on.

Custom connectors are reported to be available on all Claude plans, with one at a time on the free plan. On Team or Enterprise plans, an organization Owner reportedly has to add the connector first. Plan rules change, so check Anthropic's current help pages.

Claude Code

Meta's get-started page documents a command in this shape: claude mcp add --transport http --client-id <META_APP_ID> meta-ads <URL from Meta docs>. The --client-id flag takes the ID of your own Meta developer app. Early Claude Code users reported errors in April and May 2026, and Meta now lists Claude Code as supported.

ChatGPT

Meta's documentation says to enter the URL as the Server URL. Menu names differ between sources (one says "Plugins on the web", others say "custom MCP server"), and I could not verify the current labels. Look for the place where ChatGPT lets you add an MCP server by URL, which may depend on your plan and workspace settings.

Other clients

For Codex and other MCP clients, one vendor reports that Meta's documented route since July 2026 is to use your own Meta developer app. Verify this in Meta's get-started page.

Which errors are most common, and what fixes them?

Symptom	Reported cause	Reported fix
"Couldn't register with Meta's login service" (Claude)	Stale connector record. Based on one public report, so low confidence.	Remove and re-add the connector. If it persists, enter your own app ID as the OAuth Client ID in advanced settings, or use Claude Code.
redirect_uris are not registered for this client (Claude Code)	Default sign-in does not work for that client. Reported in a public issue in April 2026.	Add --client-id <META_APP_ID> with your own Meta app.
"Your ad account is not enabled yet"	Meta is reported to enable the server per ad account during beta.	Nothing on your side switches it on. Check Business Suite, Settings, Integrations for an Ads MCP server entry. If it is missing, wait or ask Meta support.
"You can't connect to Ads MCP server with this account."	Wrong Facebook profile, or a profile with no role on the ad account.	Reconnect and check which profile the login screen uses.
Connects, but no tools or empty data	Connector off in this chat, ad account not ticked at login, or account not enabled.	Toggle the connector on, redo login and tick the account.
Writes blocked	A business admin may have restricted actions on that ad account.	Ask the admin, and check Meta's documentation for current controls.

What should you check first when Meta Ads MCP is not working?

Work through this list in order. Each step takes a minute or two.

1. Re-copy the URL. Paste it again from Meta's documentation into a plain text editor first, to strip spaces and trailing characters.
2. Remove the connector and add it again. Stale records are a reported cause of registration errors.
3. Check the Facebook profile. Log out of Facebook in the browser if you use several profiles. The profile must have a role on the ad account or business portfolio.
4. Tick the right assets at login. If you skip the ad account in the permission dialog, the connector connects but returns nothing.
5. Confirm the connector is on in the current chat. In Claude, it is a per-chat toggle.
6. Check whether the account is enabled. If you see the "not enabled yet" message, the problem is on Meta's side.
7. Try another client. If Claude's connector fails but Claude Code works with your own app ID, the issue is the default sign-in path, not your account.

How do permissions and scopes cause failures?

The connector inherits the access of the Facebook user who signs in. If that person cannot see an ad account in Ads Manager, the assistant cannot see it either. Limit exposure by selecting only the business portfolios you need.

If you use your own Meta app or a token, scopes matter. Secondary sources attribute these to Meta's get-started page:

• ads_mcp_management plus either ads_read or ads_management as the minimum.
• ads_read is enough for reporting. ads_management is needed to change things.
• Optional scopes such as catalog_management and business_management reportedly unlock more tools.
• To manage other businesses' ad accounts, the app reportedly needs Advanced Access to ads_mcp_management through App Review.

For your own app, the redirect URL in Facebook Login for Business settings must match your MCP client. A mismatch produces redirect errors. Meta's docs also say you need to add the "Create & manage ads with ads MCP server" use case to the app.

For token-based access, one vendor reports that system-user tokens work only with the Employee role, and that Admin-role tokens are rejected. Treat this as unverified.

Is it safe to keep troubleshooting with write access on?

Use read-only access while you debug. Reporting needs only read scopes, and a connection that can create or edit campaigns is a larger risk than one that can only read. If you or an agency need write access later, add it deliberately and review what the assistant plans to change before approving. The article "MCP Permissions: Read-Only vs Read-Write for Ads and Stores" explains the trade-offs.

Also be careful with third-party "fixes" that ask you to paste access tokens into a website or install an unknown proxy. A token is a password to your ad account.

What can this connector not do?

• It cannot fix account-level enablement. If Meta has not enabled your account, no setting on your side changes that.
• It does not make bad data good. Reports reflect what your pixel and conversion data record.
• Tool counts and categories are not stable. Meta's docs describe seven categories, while third parties cite around 29 tools. Check the docs for the current list.
• Beta status and pricing are not clearly stated in current sources. Meta's docs list no MCP fee, and normal ad spend applies.

When should you contact Meta instead?

Contact Meta support or check the Business Help Center when the "not enabled" message persists, when the Integrations menu item never appears, or when App Review blocks Advanced Access. For client-side bugs, check the issue tracker of the client you use.