Additional read-only diagnostics — October 10, 2026, approximately 4:50 PM Pacific / 23:50 UTC.
We reproduced a difference based solely on whether an explicit team selector is supplied.
Project: quintascent-picio-pilot-v1 Project ID: prj_HkwvurhrAMytl7Xb74iiDmCLAM4q Team slug: quitascent Team ID: team_IKgnMSNmT2TNQeoQoCmPyZ5b
Results:
Both failed project lookups identify operation GET /v9/projects/{idOrName} and report: “Not authorized: Trying to access resource under scope "quitascent". You must re-authenticate to this scope or use a token with access to this scope.”
Request IDs:
Error metadata: saml=false; ssoEnforced=false. The connector additionally labels the failure INVALID_ARGUMENT, while the underlying API error is 403 forbidden.
The Vercel account UI shows quitascent as the default team. The ChatGPT application, owned by Vercel MCP, displays permission to read Vercel team data and read/change authorized projects.
Could you trace these request IDs and check why implicit/default-team project access succeeds while explicitly selecting the same owning team fails? Is this expected authorization behavior, a missing team-specific grant, or a connector scope-resolution issue?
These tests were read-only. No credentials, deployment protections, or project settings were changed.
Additional comparison using Vercel Agent’s separate credentials:
• Project lookup succeeds with both the owning team ID and slug “quitascent.” • Team listing includes quitascent, and direct team lookup succeeds. • The project’s accountId matches the supplied team ID. • Deployment listing succeeds.
ChatGPT MCP still shows the contrasting behavior documented above: project access without an explicit team selector succeeds, but explicit team ID/slug access returns 403, and team listing is empty.
Vercel Agent could not inspect ChatGPT’s effective OAuth grant or token context. Please check whether the ChatGPT connection has an effective grant for this specific team and whether explicit team selectors are resolved correctly. The displayed “read team data” permission alone does not settle that question.
No settings or resources were changed in either diagnostic.