The error message is misleading here, and it is worth separating this from the other 403 threads.

There are two different failures being discussed as one:

1. Client approval. A client that registers through the public registration endpoint cannot authorize at all. That affects people building their own client.
2. Team scope. An approved client such as ChatGPT or Codex authenticates fine, list_teams comes back empty, and any call with an explicit teamId returns 403 with "re-authenticate to this scope".

Yours is the second, and reconnecting cannot fix it. Here is why.

There is no team scope anywhere in the OAuth layer:

• https://mcp.vercel.com/.well-known/oauth-protected-resource advertises scopes_supported: ["openid"]
• https://vercel.com/.well-known/oauth-authorization-server advertises openid, email, profile, offline_access

None of those covers a team. So "re-authenticate to this scope" cannot be naming an OAuth scope, because no scope binding a grant to a team is advertised. Whatever does bind the grant happens outside that set, which is exactly why repeating consent gives you the same binding every time. It also means there is no way to see, before or after authorising, which team your grant actually covers.

It has been reported on Hobby and on Pro, so it is not a plan limit, and your saml: false / ssoEnforced: false rules out SSO enforcement.

Until it is fixed, calls that omit teamId do work, which is consistent with the grant being bound to your personal scope rather than the team.

I wrote both failures up with the full discovery output here: https://community.vercel.com/t/two-different-403s-client-approval-and-team-scope-are-separate-problems/50539