ChatGPT–Vercel MCP integration: persistent 403 team authorization error after successful OAuth

Hello Vercel team,

I am experiencing a persistent authorization issue when using the official Vercel MCP integration with ChatGPT.

Vercel team

• Team slug: mgutierrezrechee-4423
• Team ID: team_0JMJ5qYVfAAcZiRHCOkna4GY
• Account: Hobby plan

Problem

ChatGPT successfully completes the Vercel OAuth authorization flow. The authorization page correctly displays my account and team, and I explicitly grant access.

However, when ChatGPT attempts to list or access my Vercel projects, the integration returns:

Not authorized: Trying to access resource under scope "mgutierrezrechee-4423". You must re-authenticate to this scope or use a token with access to this scope.

Troubleshooting already performed

1. Confirmed that the Vercel account and team are accessible through the Vercel dashboard.
2. Uninstalled the Vercel integration from ChatGPT.
3. Reinstalled it and completed a fresh OAuth authorization.
4. Explicitly selected the correct Vercel team during authorization.
5. Retested access after reconnecting. The 403 error persists.

The Vercel projects themselves work normally in the dashboard.

I have also found reports in the Vercel Community describing very similar symptoms: successful OAuth authorization, empty team listings, and 403 errors when accessing team-scoped resources.

Questions

• Is this a known issue with the Vercel MCP server or its OAuth team-scope handling?
• Is there a way to explicitly authorize or reauthorize a specific team for an MCP client?
• Could you investigate why the OAuth authorization succeeds but the MCP server still rejects access to the selected team?

Please let me know if you need additional diagnostic information.

Thank you.