Vercel MCP in ChatGPT: empty projects and 403 despite explicit teamId

The Vercel support form directed me to the community because Vercel MCP is in Beta.

I am using the Vercel connection in ChatGPT’s Work view to develop an existing staging website.

The connection appears authorized in both ChatGPT and Vercel. I can open the project dashboard in my browser.

The last recorded read-only test in ChatGPT reported:

list_teams successfully returned my team.
list_projects returned an empty list even when the correct teamId was explicitly included.
list_deployments returned 403 Forbidden with both the projectId and teamId explicitly included.
get_project reported that idOrName was missing, although the tool exposed to ChatGPT accepts projectId and teamId.

We have reviewed the connection settings, confirmed browser access, repeated the test in a new conversation, and retried with explicit team context.

Could someone investigate whether the connector forwards teamId correctly and maps projectId to the required idOrName parameter?

The cause has not been established. This blocks staging development; it is not a production outage.

I can provide the detailed request/error report and account identifiers privately to Vercel staff.

Confirming the get_project parameter mismatch from a separate account on September 22, 2026, using the installed Vercel connector in the Codex desktop app on Windows. Vercel support directed this report here because MCP is in Beta.

In this test, list_teams, list_projects, and list_deployments all succeeded. I did not reproduce the empty-project list or 403 errors in the original post; the shared defect is specifically get_project.

Reproduction:

Obtain valid project and team IDs from the successful list calls.
Call get_project with the advertised fields: {"projectId":"VALID_PROJECT_ID","teamId":"VALID_TEAM_ID"}. These strings are placeholders here; actual valid IDs were used in the test.
The response is: "Input validation error: Invalid arguments for tool get_project: idOrName: Invalid input: expected string, received undefined" (isError=true).
Retrying with an additional idOrName field alongside projectId and teamId produced the same error. Whether the client adapter drops the unadvertised field has not been established.

Expected: the advertised input schema should return project details. The public MCP tool reference also documents projectId and teamId: https://vercel.com/docs/agent-resources/vercel-mcp/tools

vercel.com

Tools

Explore Vercel MCP tools for projects, deployments, domains, sandboxes, and more.

Impact: individual project details are unavailable through this connector, while project/deployment listing works. This is not a production outage or a general authentication failure.

Please route this to the MCP/connector integration team to align the exposed schema with the handler, map projectId to idOrName if required, and add a contract test using the advertised arguments. Please also confirm whether the mismatch is in Vercel MCP or the Codex connector adapter. No credentials, account/project IDs, or customer data are included in this public report.

Thank you for independently reproducing the get_project mismatch and for distinguishing it from the other symptoms.

A fresh read-only test of my connection on September 22 still shows:

list_teams succeeds. list_projects returns an empty list with the correct team ID explicitly included. list_deployments returns 403 Forbidden with both the recorded project ID and team ID explicitly included. get_project returns the same missing-idOrName validation error.

Your report corroborates the project-lookup mismatch across accounts. My project-listing and deployment-access failures remain an additional unresolved issue; I am not assuming they share the same cause.

Could a maintainer confirm which team owns the schema/handler mismatch and whether a fix is being tracked? Please also advise whether the listing/access failures should be investigated in a separate thread and what sanitized diagnostic information would help.

I can provide account identifiers through an appropriate private support channel.

I'm experiencing a similar issue with the ChatGPT–Vercel MCP integration.

My Vercel account has owner-level access to the team, the GitHub repository is accessible, and the GitHub Vercel App is installed with access to all repositories. However, creating a Git-connected Vercel project through the connector returns "403 Forbidden" with the message: "You don't have permission to create the project."

The request still failed when I supplied the explicit team ID and set deployment to disabled. No project was created and no deployment occurred.

Other reports in this thread describe a "get_project" argument-schema mismatch, empty project listings, and deployment-access failures. I understand these may be separate defects.

Could the Vercel MCP/connector team investigate the project-creation authorization failure and advise how to provide the request ID and account diagnostics privately?

I have not changed the repository's default branch, changed permissions, or deployed to production to work around this issue.

Reproduction:

Obtain valid project and team IDs from the successful list calls.
Call get_project with the advertised fields: {"projectId":"VALID_PROJECT_ID","teamId":"VALID_TEAM_ID"}. These strings are placeholders here; actual valid IDs were used in the test.
The response is: "Input validation error: Invalid arguments for tool get_project: idOrName: Invalid input: expected string, received undefined" (isError=true).
Retrying with an additional idOrName field alongside projectId and teamId produced the same error. Whether the client adapter drops the unadvertised field has not been established.

Expected: the advertised input schema should return project details. The public MCP tool reference also documents projectId and teamId: https://vercel.com/docs/agent-resources/vercel-mcp/tools

vercel.com

Tools

Explore Vercel MCP tools for projects, deployments, domains, sandboxes, and more.

Impact: individual project details are unavailable through this connector, while project/deployment listing works. This is not a production outage or a general authentication failure.

I'm experiencing a similar issue with the ChatGPT–Vercel MCP integration. My Vercel account has owner-level access to the team, the GitHub repository is accessible, and the GitHub Vercel App is installed with access to all repositories. However, creating a Git-connected Vercel project through the connector returns "403 Forbidden" with the message: "You don't have permission to create the project." The request still failed when I supplied the explicit team ID and set deployment to disabled. No project was created and no deployment occurred. Other reports in this thread describe a "get_project" argument-schema mismatch, empty project listings, and deployment-access failures. I understand these may be separate defects. Could the Vercel MCP/connector team investigate the project-creation authorization failure and advise how to provide the request ID and account diagnostics privately? I have not changed the repository's default branch, changed permissions, or deployed to production to work around this issue.