ChatGPT Vercel MCP OAuth incorrectly requires 2FA and returns 403/404 for valid team scope

Hello Vercel Support,

I am experiencing what appears to be an OAuth/team authorization issue with the official Vercel MCP connection in ChatGPT.

Account / environment

Vercel account/workspace: klamtjava-3321 Plan: Hobby User role: Owner Personal Two-Factor Authentication: Active Authenticator App (TOTP): Enrolled Vercel dashboard access works normally Projects are visible and accessible manually in the Vercel dashboard

Problem

During the ChatGPT → Vercel OAuth authorization flow, the team/project entry:

klamtjava-3321's projects

remains locked and displays:

Set up 2FA

even though 2FA is already enabled and active on the account.

Clicking the locked team/project entry results in a 404 page.

I have already:

confirmed personal 2FA is Active, confirmed I am the Owner of the workspace, signed out and back into Vercel, disconnected and reconnected the ChatGPT/Vercel connection, repeated the OAuth authorization, verified the Members page does not show a missing-2FA warning.

The OAuth screen still incorrectly reports Set up 2FA.

MCP behavior

From ChatGPT, the Vercel MCP connector currently behaves as follows:

list_teams

returns an empty team list.

When the known team ID is supplied explicitly:

team_qF6hJf1KHIh71TCW0rTWAXdh

list_projects returns:

403 Forbidden

with:

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

This happens despite repeated OAuth reauthorization.

Expected behavior

The OAuth authorization page should recognize that 2FA is already enabled, allow ChatGPT access to the klamtjava-3321 project scope, and Vercel MCP should be able to list the workspace and its projects.

Actual behavior

OAuth UI incorrectly shows Set up 2FA project/team entry remains locked clicking it returns 404 MCP list_teams returns no teams explicit team-scoped project access returns 403

Impact

This blocks ChatGPT from inspecting and managing Vercel project configuration for an existing monorepo. The websites themselves are not experiencing a production outage.

I can provide screenshots showing:

Vercel personal 2FA status = Active team Members page showing the account as Owner OAuth authorization page incorrectly showing Set up 2FA the 403 MCP response

There appear to be other recent reports of similar ChatGPT/Vercel MCP team-scope authorization failures.

Could you please check whether the OAuth authorization for mcp.vercel.com is correctly receiving/recognizing the team scope and 2FA state?

Thank you.

Hi there! I'm just a bot here to share some info that might help you before a human arrives.

If your account is eligible, you can use our new self-service recovery flow:

Go to vercel.com/login
Choose to sign in using the email + one-time password (OTP) option.
Select Use another sign-in method
Verify your identity using the GitHub, GitLab, or Bitbucket account previously linked to your Vercel account
Follow the remaining prompts to complete the recovery process

If you've ever set up a passkey, possibly on another device, you can use that to get back into your account and update 2FA settings yourself. You can also use recovery codes if you've stored those in a safe place that you can still access.

If you are unable to access your account using the steps above, you can open a support case using the Start 2FA recovery option on the Two-Factor Authentication login screen. Please do not publicly post account details, like your email address, that could help an attacker gain access to your account in the future. There's no need to open an additional case if you already have one open.

Thanks for your patience while the team works to resolve all cases as quickly as possible while keeping everyone’s accounts safe and secure. A human should be here soon to help.