
Latest videos
See all →Showcase
Help
wwshinai221-8661 I am experiencing the same issue with ChatGPT Vercel MCP. My project interior-family-board is accessible in the Vercel dashboard under team wwshinai, but MCP returns 404 for project lookup and 403 for deployment listing. I have already reconnected ChatGPT, reauthorized team access, and verified that both use the same Vercel account. Please investigate the MCP installation's project access permissions. Failed request ID: iad1:hnd1:iad1:sfo1::7lwgv-1794369218159-197bd055aa0a
amoretto2008 I'm experiencing the same issue with ChatGPT's Vercel MCP integration. My project is visible in the Vercel dashboard, but the MCP integration returns 404 for project lookup and 403 for deployment access. I have confirmed the correct team and project, reauthorized access, and verified that the issue persists. Vercel Support directed me to the Community because Vercel MCP is in Beta. Could the Vercel MCP team investigate the project-level authorization and advise how to restore access to an existing project without recreating it? I can provide request IDs and project details privately if needed.
hilaltalaskurtoglu-2539 Additional information: My latest Production deployment status is Ready. The domain hilalogretmen.vercel.app shows Valid Configuration, and Production is selected. The HTTPS connection still fails on both Wi-Fi and mobile data with ERR_CONNECTION_RESET. This appears to be a TLS handshake or Vercel Edge routing issue rather than a build or DNS configuration issue. Could a Vercel engineer please investigate the Edge TLS response for this hostname?
hilaltalaskurtoglu-2539 I also deleted and recreated the domain with the same name, but the issue persists. Both the main project URL and the deployment-specific URL remain inaccessible. The deployment status is Ready, and the domain configuration is Valid Configuration. I have tested on both Wi-Fi and mobile data. The TLS handshake is reset in both cases. Please investigate this as a possible platform-level connectivity or Edge TLS issue.