ChatGPT Vercel MCP: 403 persists after successful OAuth authorization

Hello Vercel team,

Vercel support directed me to the community because this issue involves Vercel MCP Beta.

My project opens normally in the Vercel dashboard. However, the ChatGPT integration returns 403 Forbidden when querying the project.

Already checked:

Reconnected using the correct Vercel account.
The intended team appeared on the OAuth consent screen before clicking “Allow access”.
ChatGPT confirmed the connection was successful.
Vercel Account Settings > Sign in with Vercel also shows ChatGPT connected.
Querying the project with either explicit teamId or team slug still returns 403.
The connected-app menu only offers Developer website and Disconnect; there is no team-permission editor.

Error: “Not authorized: Trying to access resource under scope ‘carmotosg2-cloud’. You must re-authenticate to this scope or use a token with access to this scope.”

Failed operation: GET /v9/projects/{idOrName} Request ID: gru1:sfo1::rj26g-1792589658565-66f2e3ecb32d Date: October 21, 2026 saml: false ssoEnforced: false

Could you investigate why the completed OAuth authorization does not allow access to the intended team? I can provide the team and project IDs privately if needed.

This blocks publishing updates to our ERP. Reconnecting has already been tested without resolving the issue.

Hello, I’m experiencing a similar 403 error with the ChatGPT Vercel connector.

My project is heartgate-private-beta, under team mykepanama-5445. I can access it in the Vercel dashboard, but requests through ChatGPT targeting this team fail with:

“Not authorized: Trying to access resource under scope ‘mykepanama-5445’. You must re-authenticate to this scope or use a token with access to this scope.”

I have reconnected several times, deleted all active ChatGPT tokens in Vercel, and removed and reinstalled the connector. The error persists.

In my case, reconnecting returns me directly to ChatGPT without showing a consent screen or team selection.

Request ID: fra1:sfo1::288s4-1792596156063-a58f043c30ed

Could your team investigate? The recommended reconnection and token deletion steps have already been tried without success.

investigating now. in the meantime could you try revoking and then granting access to the selected team and see if that works?

Hello Vercel team,

Vercel support directed me to the community because this issue involves Vercel MCP Beta.

My project opens normally in the Vercel dashboard. However, the ChatGPT integration returns 403 Forbidden when querying the project.

Already checked:

Reconnected using the correct Vercel account.
The intended team appeared on the OAuth consent screen before clicking “Allow access”.
ChatGPT confirmed the connection was successful.
Vercel Account Settings > Sign in with Vercel also shows ChatGPT connected.
Querying the project with either explicit teamId or team slug still returns 403.
The connected-app menu only offers Developer website and Disconnect; there is no team-permission editor.