Vercel MCP in ChatGPT Work: team access fails and OAuth registration rejects redirect URI

I’m experiencing two issues using Vercel MCP from ChatGPT Work in a ChatGPT Business workspace.

Environment: Vercel Pro team, Owner account. The project is accessible in the Vercel dashboard. Observed on 8 September 2026.

Existing Vercel connection: team resources unavailable list_teams returns the correct team. list_projects returns an empty list despite an explicit teamId. get_project returns 404 despite explicitly supplying both projectId and teamId. list_deployments returns 403: “You don't have permission to list the deployment.” The IDs have been checked against the dashboard. Reconnecting OAuth did not resolve this.

Project-scoped connection: OAuth registration rejected Following Vercel’s support chatbot guidance, I tried creating a separate OAuth connection using:

https://mcp.vercel.com//

Creation fails with:

“Dynamic client registration failed: registration endpoint returned 400 (invalid_redirect_uri: The provided redirect URIs are not approved for use by this authorization server.)”

Advanced OAuth settings show:

Dynamic Client Registration (DCR) selected. Registration endpoint: https://api.vercel.com/login/oauth/register CIMD unavailable because the server does not advertise support. Could the MCP team investigate the rejected ChatGPT Work callback URI and the separate access failures with explicit team parameters? What supported connection method should we use?

The support case form directs Vercel MCP issues to Community. Actual team and project identifiers can be provided through an approved private channel.

There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

https://community.vercel.com/t/debugging-404-errors/437

Vercel Community

Debugging 404 Errors

Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found. There are...

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

I have now tested the exact documented endpoint:

https://mcp.vercel.com

Authentication: OAuth. No path or trailing slash.

ChatGPT Work still returns: “Dynamic client registration failed: registration endpoint returned 400 (invalid_redirect_uri: The provided redirect URIs are not approved for use by this authorization server.)”

The same registration failure therefore occurs on the standard endpoint.

Please investigate which callback URI ChatGPT Work submits and why it is rejected. Separately, please verify the authenticated identity and effective team/project permissions behind the existing connector’s 403/404 failures with explicit, verified IDs.

Please provide a private channel for any account details or diagnostic information you need.