Vercel MCP returns project 404 after successful team authorization

Vercel MCP cannot access an existing project after successful team authorization. The same project is visible in the authenticated Vercel dashboard.

Verified on 2026-11-01 around 09:15 UTC:

get_auth_user matches the browser account.
list_teams returns the correct team.
The existing ChatGPT OAuth connection displays Projects read/write, Deployments read/write, and Team read.
authorize_team_access was approved and the browser showed You're signed in.
Immediately afterward, get_project with the exact projectId/teamId still returned 404 not_found; list_projects for that team/project returned an empty list.

The official support portal directs MCP Beta issues here and did not create a private case. How can the Vercel MCP team investigate the effective resource grant or request routing and provide a durable fix? Account/project identifiers and request traces can be supplied through an appropriate private channel.

No credentials, account IDs, project IDs, app client IDs, domain names, or tokens are included. No source, deployment, or security setting changes are requested.

There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

https://community.vercel.com/t/debugging-404-errors/437

Vercel Community

Debugging 404 Errors

Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found. There are...

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.