Under every tutorial for Meta's Ads MCP there is a cluster of comments that all describe the same wall. The setup completes, the connector appears, and then: “It says no access to meta ads manager.” “I connected it but I still can't access it.” “It can see my account name but can't do anything.” “I can't find the Facebook connector in my paid Claude account.” These read like four different bugs. Three of them are one thing, and the fourth is not yours to fix.
Short answer: connecting proves who you are, not what you are allowed to touch. The setup step is Facebook Login, which establishes identity. Permission to read a specific ad account is granted separately, under Business Settings → Ad accounts → People. A connector that finishes cleanly and then reports no access is almost always that gap — not a broken install. The one exception is an account that comes back with is_ads_mcp_enabled: false, which is a Meta-side rollout flag and cannot be fixed from your end.
Connecting is identity, not access
The setup path is Facebook Login. What it establishes is which Facebook user is on the other end of the connection. That is a separate fact from whether that user is allowed to touch a given ad account — Meta has always kept those apart, and the MCP inherits the distinction rather than smoothing it over. So a connection that completes successfully and then cannot read an ad account is not a contradiction. It is the normal shape of a permissions gap.
The check that catches most of them
Business Settings → Ad accounts → pick the account → People. The exact user you authorised with has to be listed there, with a role. Not admin of the Page. Not admin of the Business. Assigned to the ad account. Those three are separate grants and people conflate them constantly, because in the Ads Manager UI you rarely feel the difference — you are usually already assigned to the account you use every day, so nothing ever forces you to notice that it was a distinct step.
- If the ad account belongs to someone else's Business and you have partner access, the partner has to assign you to that ad account specifically. Access to the Business is not access to its ad accounts.
- If you authorised with a different Facebook account than the one you normally work in — easy to do when a browser is already signed into a personal profile — the connection is fine and simply belongs to the wrong person.
- If you re-authorise, watch the screen where Meta lists your businesses and assets. It is a real selection step, and it is very easy to click straight through it with nothing ticked.
The one-question test
Ask it to list the ad accounts it can see. The answer separates two problems that look identical from the outside. An empty list, returned calmly, means the connection works and the permission is missing — the request went to Meta, Meta answered, and the answer was “nothing.” An outright permission error means the call itself was refused, which points back at scopes or at a connection that did not complete the way you think it did. Same symptom on your screen, opposite fixes.
This distinction is worth more than it looks, and not only here. “I could not reach the data” and “I reached it and there was none” produce the same sentence from a model and require different work from you. Whenever something reports nothing, find out which one it was before you start fixing.
The one you cannot fix
Some people get a specific answer instead: the ad account comes back with is_ads_mcp_enabled set to false, and a message that Ads MCP is being rolled out gradually and to check back later. That is not a permission you can grant yourself. If you see it, the account is simply not switched on yet — the accounts you can see and the accounts that are enabled are two different sets, and no amount of re-authorising changes the second one. We have not found a documented way to request it; treat waiting as the only honest advice until Meta says otherwise.
“The connector has no tools”
This one is worth separating from the rest. It describes a connector that is added and authenticated but exposes nothing to call, which is a state on the client side rather than a fact about your Meta permissions. Remove the connector and add it again before you go digging through Business Settings — you can burn an hour on a permissions hunt for a problem that was never about permissions.
Once it can see the account
The next surprise tends to be reporting. Ask for clicks, CTR or cost per conversion in plain English and you can get back something thin, because these are not in the default field set. Name them: clicks and inline_link_clicks — the second is link clicks specifically, which is usually what people mean — ctr, inline_link_click_ctr, cpc, and for conversions actions together with cost_per_action_type. Cost per conversion is not a single field. It comes back as a list keyed by action type, so you have to say which action you care about — purchase, lead, complete_registration — and read that entry out of the list.
And if a field still comes back empty, apply the same test as before: check whether that ad set has ever recorded that action at all. Zero purchases means no purchase entry exists, which reads as “not available” and is really “zero.” Different problem, different fix.
The honest summary
Connected is not the same as permitted, permitted is not the same as enabled, and “no data” is not the same as “no access.” Work down those three in that order and most of these comment-section walls resolve in a few minutes. The one that does not — the rollout flag — is worth recognising quickly precisely because there is nothing to do about it, and the hours people spend re-authorising into that wall are the expensive part.