ChatGPT Vercel MCP: OAuth succeeds, but team access returns 403

I am experiencing the same issue when connecting Vercel MCP to ChatGPT.

Environment

• Client: ChatGPT Vercel integration
• Vercel account: 247newscheck-1274
• Team slug: 247-news-check
• Team ID: team_NN1ccWHLhCesfsMYfAfv9jKW
• Project: 247newscheck
• Project ID: prj_unpO0y9NNXKwfAykJ2jrY4xtnImW

Observed behaviour

1. OAuth authentication succeeds.
2. The authenticated-user request returns my expected Vercel account.
3. list_teams returns an empty list.
4. Retrieving the project and its deployments through the default context succeeds.
5. Explicit requests using the team ID or team slug return 403 Forbidden, stating that the connection is not authorized for scope 247-news-check.
6. Disconnecting and reconnecting the ChatGPT integration has not resolved the issue.

My production deployment is Ready, and the production website is accessible. This appears to be a team-scope authorization issue rather than a deployment failure.

Could the Vercel team clarify whether this is a known limitation or bug in the Beta OAuth integration, and advise how ChatGPT can obtain the correct team-scoped authorization?

I have not included credentials, tokens, or other secrets. I can provide additional diagnostic details if needed.