Hello Vercel Team,
I was directed here by Vercel Support because Vercel MCP is currently in Beta.
I'm experiencing an authorization issue with the official Vercel MCP server in OpenAI Codex on Windows.
Environment
- MCP endpoint: https://mcp.vercel.com
- MCP client: OpenAI Codex
- Team name: Inmersa
- Team slug:
inmersa1 - Team ID:
team_qFTnw1Efh7du7UlFYH4Hkh31 - Project:
inmersa
AI Client: OpenAI Codex (VS Code extension, Windows)
MCP Server: Official Vercel MCP (https://mcp.vercel.com)
Authentication: OAuth
Issue: OAuth authentication completes successfully in Codex, but the Vercel MCP returns 404 User not found and 403 Forbidden when accessing my Vercel team and project.
The issue persists even after reauthorization and starting a fresh Codex session. The Vercel CLI works correctly with the same team and project.
Results:
list_teams: returns an empty listget_auth_user: returns404 not_found: User not found- Project lookup:
403 Forbidden - Deployment lookup:
403 Forbidden
Exact error:
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.
Troubleshooting already completed
- Confirmed the Vercel CLI is installed, authenticated, and can access the team and project.
- Verified the team slug and ID.
- Confirmed that the MCP uses the official endpoint with no additional bearer token, authorization headers, or duplicate configuration.
- Successfully completed OAuth logout/login and reauthorization.
- Started a fresh Codex session and reproduced the same failures.
- Confirmed that the production deployment is READY and GitHub integration works.
The CLI and MCP have independent authentication credentials. Only MCP access is failing.
Expected behavior
After successful OAuth authorization, the MCP should identify the authenticated user, list accessible teams, and retrieve project and deployment information.
Actual behavior
The MCP reports User not found and rejects requests for my team, despite successful OAuth authorization.
Request
Could the Vercel engineering team investigate whether the MCP OAuth subject is correctly associated with my Vercel user and whether the OAuth grant has effective access to team inmersa1?
Similar authorization issues have been reported by other community members.
Request IDs for investigation
The following request IDs were captured during a fresh Codex session after successfully renewing OAuth authorization.
Project lookup (403 Forbidden):
iad1:sfo1::swxcs-1791562320833-6c872ce8ada0
Deployment lookup (403 Forbidden):
iad1:sfo1::g4d2f-1791562321835-af7d21615fb7
Both requests failed with an authorization error for team scope inmersa1.
Please use these request IDs to investigate the MCP OAuth identity mapping and team-scope authorization failure.
I would appreciate confirmation of whether this is a known MCP Beta issue or whether additional account-level configuration is required.
Thank you.
