Hello Vercel MCP team,
The connected Vercel app in ChatGPT completes sign-in, but cannot read an expected team-owned project.
Observed behavior:
- A read-only GET /v9/projects/{idOrName} request supplied the intended project identifier and explicit teamId.
- It returned HTTP 403 before reconnection and again after reconnection on October 11, 2026.
- Sanitized error: Not authorized: Trying to access resource under scope [EXPECTED_TEAM]; must re-authenticate to the scope or use a token with access.
- The response reported saml:false and ssoEnforced:false.
- Account Settings → Sign in with Vercel lists ChatGPT as Owned by Vercel MCP. Its menu offers only Developer Website and Disconnect. Clicking the app name opens no details.
The private Vercel Support agent proposed a personal-only OAuth grant as the cause, then clarified that it cannot inspect internal request logs or the OAuth token database and that its diagnosis was an inference. It directed the report to Community. We have no engineering trace confirming the effective principal or grant.
The official MCP tools documentation requires granting the client access to the owning team: https://vercel.com/docs/agent-resources/vercel-mcp/tools
Could the MCP team provide the exact current workflow for reviewing and granting the existing ChatGPT connection access to the intended team? If the authorization flow offers no team selector, what is the supported repair or secure engineering escalation? We have not yet verified whether such a selector is available in the current flow.
The existing connector is the repair target. The failure prevents project inspection through that connector; no production outage is being claimed.
Project/team identifiers, account email, deployment URLs, request IDs, screenshots, credentials, source code and customer data are omitted from this public draft. The two request traces were supplied in private Support; please provide a secure channel if engineering needs them.