Hello Vercel Community,
I’m investigating a read-only access discrepancy between the Vercel plugin in Codex and the Vercel CLI.
Environment:
- Vercel plugin:
vercel/vercel-plugin0.54.1 - Vercel CLI: 66.5.0
- MCP endpoint:
https://mcp.vercel.com - Plan: Hobby
- Three existing team-owned projects
Both connections return the same user ID and team ID. The default team matches, and the user has confirmed OWNER membership. Identifiers are omitted from this public post.
Using the existing CLI login, these read-only commands succeed:
vercel whoami --jsonvercel project ls --scope <TEAM_SLUG> --json --limit 100vercel api /v9/projects/<PROJECT_ID> --method GET --scope <TEAM_SLUG>The CLI lists all three projects and returns their deployment histories. Direct project GETs return the expected owning team.
The plugin instead returns:
- Zero projects when queried using either team ID or slug.
- Zero deployments.
- HTTP 404
not_foundfor the same exact project IDs.
Existing authorization checks:
- The ChatGPT connection exists under Sign in with Vercel, is owned by Vercel MCP, and was recently used.
- Its displayed permissions include reading/changing authorized projects, deployments and team data.
- The inspected grant page does not expose the effective authorized-project list.
- No conflicting local Vercel server override was found.
The exact cause remains unknown. Could this involve an incomplete/stale resource grant or MCP team-context handling? Is there a read-only way to inspect which team/projects this ChatGPT connection actually authorizes?
Exact identifiers and the failing request ID can be provided privately to Vercel Support. No credentials or token values are included