Vercel Support directed me to the community for an MCP Beta authorization issue.

Account authentication succeeds, and the same account can access its existing resources through the Vercel web dashboard. However, the connector cannot access team-scoped resources.

Observed behavior:

• Reconnect for the existing connected account completes login without showing a team-selection or team-consent screen.
• list_teams returns an empty list.
• get_project with an explicit teamId returns a forbidden/team-authorization response. Specifying the corresponding team slug instead has the same result.
• The response instructs the agent to call authorize_team_access or authorize_team_sso, but neither tool is exposed in this connection's available tool list.

Expected behavior: A supported team-authorization flow should be available, or the indicated authorization tool should be exposed so the user can approve the intended team.

Could the Vercel MCP team confirm the supported authorization path when reconnect skips team consent and the indicated tools are unavailable?

This report intentionally omits account names, team/project names and IDs, URLs, request/error identifiers, precise timestamps, screenshots, credentials, and customer data. It contains only the general technical behavior. No production configuration or deployment changes are requested.