Vercel MCP OAuth team scope not granted — teams: [] and 403 despite explicit team authorization - Help

Hello, I am reporting an OAuth/team-scoping issue with the Vercel MCP Beta used from ChatGPT Work/Codex. Vercel account

User: arnaudq20
Email: arnaudquirin2@gmail.com Team
Name: Digital Mind AI
Slug: digital-mind-ai2 In the Vercel web UI, this account can access the team and its projects, including:
digital-mind-business-suite-staging
digital-mind-business-suite
digital-mind-business-suite-dr-replay However, through Vercel MCP:
identity lookup succeeds;
team listing returns teams: [];
direct team access returns 403 forbidden;
project metadata returns 403 forbidden;
deployments return 403 forbidden;
runtime logs return 403 forbidden. The affected STAGING project is: prj_VCP7RWrpMQDp9xJWr61T58Palw0p I already disconnected and reconnected the Vercel integration. During the new OAuth authorization, the Digital Mind AI team was explicitly displayed and selected, and the authorization screen showed both read/write and read-only team permissions. I then approved the authorization with Allow Access. Despite that, the MCP credential still does not receive access to the team scope and continues returning teams: []. The API responses indicate:
saml: false
ssoEnforced: false So this does not appear to be caused by SAML/SSO enforcement or by Deployment Protection. Example Request ID: bom1:sfo1::df75g-1791968146932-7ef0330d684c Could the Vercel MCP team please investigate whether the OAuth team scope is being propagated correctly to the MCP credential? I can provide additional request IDs or reproduction details if needed. Thanks.

Hello, I am reporting an OAuth/team-scoping issue with the Vercel MCP Beta used from ChatGPT Work/Codex. Vercel account

User: arnaudq20
Email: arnaudquirin2@gmail.com Team
Name: Digital Mind AI
Slug: digital-mind-ai2 In the Vercel web UI, this account can access the team and its projects, including:
digital-mind-business-suite-staging
digital-mind-business-suite
digital-mind-business-suite-dr-replay However, through Vercel MCP:
identity lookup succeeds;
team listing returns teams: [];
direct team access returns 403 forbidden;
project metadata returns 403 forbidden;
deployments return 403 forbidden;
runtime logs return 403 forbidden. The affected STAGING project is: prj_VCP7RWrpMQDp9xJWr61T58Palw0p I already disconnected and reconnected the Vercel integration. During the new OAuth authorization, the Digital Mind AI team was explicitly displayed and selected, and the authorization screen showed both read/write and read-only team permissions. I then approved the authorization with Allow Access. Despite that, the MCP credential still does not receive access to the team scope and continues returning teams: []. The API responses indicate:
saml: false
ssoEnforced: false So this does not appear to be caused by SAML/SSO enforcement or by Deployment Protection. Example Request ID: bom1:sfo1::df75g-1791968146932-7ef0330d684c Could the Vercel MCP team please investigate whether the OAuth team scope is being propagated correctly to the MCP credential? I can provide additional request IDs or reproduction details if needed. Thanks.