Subject: Vercel MCP – 403 Forbidden persists after OAuth reauthorization with Team access - Help

Hi Vercel team,

I'm experiencing a persistent 403 Forbidden error when accessing my Vercel team resources through the official Vercel MCP integration with ChatGPT.

The connection appears successful, but team-scoped operations continue to fail.

Environment:

Integration: ChatGPT by Vercel MCP
Team name: Inmersa
Team slug: inmersa1
Project name: inmersa
Team plan: Hobby

Issue:

The MCP integration exhibits the following behavior:

list_teams returns an empty array (teams: []).
list_projects can retrieve my project without an explicit teamId.
When specifying the correct teamId in a project request, Vercel returns 403 Forbidden.
The Vercel Dashboard works correctly, and I can access my team and project normally through the browser.

Troubleshooting already completed:

Disconnected and reinstalled the Vercel plugin in ChatGPT.
Revoked the previous ChatGPT OAuth authorization under Vercel Account Settings → Sign in with Vercel.
Started a fresh OAuth authorization in an InPrivate browser session.
Confirmed that my team, Inmersa, appeared in the OAuth authorization screen.
Explicitly selected the team and completed the authorization using "Allow Access".
Repeated the MCP API tests after successfully reconnecting.

Unfortunately, the same 403 error persists.

Exact API error:

403 Forbidden

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

Request ID:

iad1:sfo1::59txf-1791641626619-c71d4758c28a

Expected behavior:

After explicitly authorizing access to my team during OAuth, list_teams should return the authorized team, and team-scoped project operations should work.

Actual behavior:

list_teams remains empty, and requests specifying the authorized team return 403 Forbidden.

Since the reauthorization flow was completed successfully, could you investigate whether this is an issue with OAuth team scope propagation, authorization state, or MCP token permissions?

Is there a known issue affecting Vercel MCP integrations with Hobby teams?

Thanks for your help.