[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Events](/events) · [Live](/live) [Help](/c/help/9) # ChatGPT Vercel MCP returns empty projects and 404 with explicit team scope 0 views · 0 likes · 6 posts Grupomedicovalencia22 4821 (@grupomedicovalencia2) · 2026-09-24 Vercel MCP in ChatGPT cannot access an existing team project.Vercel Support directed me to Community for a Vercel MCP beta issue. An existing team-owned project is accessible in the authenticated Vercel dashboard but cannot be found through the connected Vercel app in ChatGPT. The connected Vercel account matches the dashboard account. Observed behavior: list_teams returns the correct team. list_projects with the verified team ID explicitly supplied in teamId returns {"projects":[],"pagination":{"count":0}}. Retesting with the verified team slug in teamId also returns an empty list. get_project with the verified project ID/name and explicit team scope returns 404 Project not found. Disconnecting and reconnecting the integration and verifying the account did not resolve it. Expected: access to projects within the authorized team scope, consistent with dashboard access. This is a connector project-lookup issue, not a deployed website returning 404. Could engineering investigate team-scope propagation, project-access grants, or connector routing? If a different parameter schema or authorization step is required, please clarify the exact supported flow. Missing teamId alone does not explain these tests: it was explicitly provided. Private identifiers and credentials are omitted. Please provide a secure channel if engineering needs identifiers. system (@system) · 2026-09-24 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](https://community.vercel.com/t/debugging-404-errors/437) A human should be around soon to offer more advice. But you can also get helpful information quickly by asking [v0](https://v0.app/). Nicosuaya 2179 (@nicosuaya-2179) · 2026-10-12 I am seeing the same issue on a Pro team where the connected account is a confirmed Owner. Vercel Support directed me here. Read-only checks on October 12, 2026: - list_teams returns the correct team, and get_team succeeds. - list_projects without a team selector returns the existing team-owned project. - The returned project accountId and the team ID from list_teams are identical in a character-by-character comparison. - list_projects with that exact teamId returns an empty list. Using the verified slug also returns an empty list. - get_project for the existing project succeeds without an explicit team selector, but returns 404 with the correct teamId or slug. Before pausing writes, create_git_project with an explicit teamId and deploy:false returned 403, saying the account did not have permission to create the project. No project or deployment was created. Two OAuth reconnections did not resolve it. During the latest consent flow, the team row visibly showed Authorized before Allow Access was completed. The connection lists Projects Read/Write permissions. Could the Vercel MCP team clarify whether the Authorized badge can still coexist with a restricted project grant, what the team-row Configure control covers, and how an end user can inspect the effective project scope of an existing ChatGPT grant? Is there a supported fix for the different results with implicit versus explicit team scope? This is an MCP/API authorization issue, not a website-level 404. I am not trying to bypass the explicit scope or change production settings. Account details, repository names, team/project IDs, request IDs, source code, and credentials are omitted from this public reply. Please indicate a secure channel if identifiers are needed. Update: list_deployments, limited to one result for the same existing project, also succeeds without a team selector and returns 403 when the exact verified teamId is supplied. The asymmetry therefore affects both project and deployment reads. Djm 1808 (@djm-1808) · 2026-10-16 I’m experiencing the same issue through the Vercel app in ChatGPT Work. Read-only checks on **15 October 2026** show: - The connector identifies the correct Vercel account. - `list_teams` returns the correct team, and `get_team` succeeds. - `list_projects`, with the correct `teamId` explicitly supplied, returns `{"projects":[],"pagination":{"count":0}}`. - `get_project`, using `idOrName` with either the project ID or name and explicit team scope, returns **404 — Project not found**. - Looking up an existing deployment with explicit team scope also returns 404. The project is accessible through my Vercel dashboard. I disconnected and reconnected the app, completed OAuth consent, and checked the connection under “Sign in with Vercel”. Its listed permissions include projects, deployments and team data. Repeating the project-listing test in a fresh ChatGPT conversation still returns zero projects. The 404 occurs in the connector’s project lookup. This is blocking deployment work through ChatGPT. Could the Vercel MCP team investigate the effective team/project authorization and confirm the supported resolution? I can provide account, team, project and request IDs privately through a secure support channel. Grupomedicovalencia22 4821 (@grupomedicovalencia2) · 2026-10-16 Actualización del 16 de octubre: confirmamos que la cuenta conectada es propietaria del equipo correcto. Consultar el proyecto y despliegue por sus IDs funciona sin selector de equipo, pero devuelve 404 al incluir el equipo correcto. La respuesta exitosa confirma que el proyecto pertenece a ese mismo equipo. Los registros de ejecución y compilación siguen inaccesibles. Solicitamos revisar el manejo del alcance y proporcionar un canal privado para compartir los identificadores de solicitud. No se modificaron permisos ni credenciales. Djm 1808 (@djm-1808) · 2026-10-20 Does anyone @system actually read and respond to these posts? Our inability to connect will kill our business in a week. If I dont hear from #vercel support this week we will have to rebuild on an alternate platform