The existing ChatGPT connection owned by Vercel MCP is connected, and its consent detail lists deployment read/write, authorized-project read/write, team-data read, and offline access. The same user can read the existing project's General settings and current production deployment in the Vercel dashboard. The exact project ID and team ID were verified from those pages and used in the read-only MCP requests.
Observed on November 10, 2026 (Asia/Shanghai):
- list_projects, filtered to the correct team and project name, returns an empty list.
- get_project by exact project name and team returns 404 Project not found.
- GET /v2/connect/projects/{projectId}/connectors returns 403: "The App installation does not have access to this project."
- Request ID: iad1:sin1:iad1:sfo1::2sq6k-1794318396596-d9f059a602fd
Reauthorization already failed to restore access. The existing connection detail offers Disconnect and Developer Website, but no project-resource selector/editor was found. Production and the existing Git integration work. No project or app was recreated, no broader permissions or alternate credentials were used, and no protection or billing setting was changed.
The official support assistant says Vercel MCP is Beta and directs persistent grant/resource-access issues to this community for product-team review. Please trace the request ID and identify the failed installation-to-project access check. Can the existing grant be repaired, or is there a documented minimum correction restoring metadata read access for this existing installation?
No account email, internal project/team IDs, tokens, code, logs, environment data, screenshots, or files are included. If internal identifiers are needed, please provide a private channel first.