RAP Sheet home
Install the bug reporting skill
Rank, 14 days: 2 on the Vercel sheet
60 people reported

All time, since Sep 3.

MCP returns 403 and empty teams after successful OAuth

“Project lookup with the confirmed project/team IDs now returns403: Not authorized: Trying to access resource under scope [TEAM].”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/vercel/issues/9328/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Fading. No reports in the last 7 days and 1 the week before, down from 17 a week at the mid-October peak.

In the ChatGPT Vercel integration, list_teams returns an empty array and project queries with explicit teamId or team slug fail.

Is this your bug?

File my report
Where
Vercel MCP
Error text
Not authorized: Trying to access resource under scope [TEAM]. You must re-authenticate to this scope or use a token with access to this scope.
Versions
59.11.1
Platforms
macOS, Web, Windows
How bad
Breaks a normal workflow. Some reports say it blocks them completely.

Not quite your bug?

  1. Team-scoped MCP queries fail2 people
  2. Vercel MCP team requests return 403, authorize_team_access tool missing3 people
  3. MCP project 404 not_found3 people

Original reports64, newest first

  1. Vercel MCP in ChatGPT returns 403 when listing deployments after team consent#51392
  2. ChatGPT Vercel MCP: deployment list still 403 after successful team authorization#51340
  3. # ChatGPT–Vercel MCP integration: persistent 403 team authorization error after successful OAuth#51306
  4. ChatGPT Vercel MCP – OAuth succeeds but workspace access returns 403 Forbidden#51238
  5. Vercel MCP OAuth 403 Forbidden — Team scope access denied despite Owner role#51184
  6. ChatGPT Vercel integration returns persistent 403 after reconnecting.#51166
  7. ChatGPT Vercel MCP: OAuth succeeds, but team access returns 403#51159
  8. ChatGPT Vercel MCP: 403 persists after successful OAuth authorization#51145
  9. ChatGPT Vercel MCP: 403 persists after successful OAuth authorization#51144
  10. ChatGPT–Vercel connection: empty teams list and 403 despite successful authorization#51131
Show all 64Show only the newest 10
  1. ChatGPT Vercel connection returns 403 after reconnecting and approving access#51108
  2. ChatGPT Vercel connection returns empty teams and 403 for deployments after OAuth reconnection#51068
  3. ChatGPT Vercel MCP returns no teams and team-scope403 after fresh OAuth authorization#51022
  4. ChatGPT Vercel connector: empty teams and 403 after reauthorization#50958
  5. ChatGPT/Codex Vercel connector: empty teams and 403 after reconnect — private follow-up requested#50935
  6. ChatGPT Vercel MCP: empty teams list and 403 with explicit teamId after OAuth#50929
  7. Vercel MCP OAuth returns 403 for existing Pro Team etome24#50880
  8. Vercel MCP integration returning 403 despite successful OAuth authorization#50859
  9. Persistent 403 Forbidden with ChatGPT Vercel MCP despite successful OAuth reconnection#50835
  10. ChatGPT Vercel MCP returns 403 for an authorized team after reconnecting#50765
  11. ChatGPT Vercel MCP – Project not accessible (403/404 errors) Hello Vercel Support,#50715
  12. Vercel MCP OAuth team scope not granted — teams: [] and 403 despite explicit team authorization#50713
  13. ChatGPT Vercel Integration Returns 403 Forbidden#50674
  14. Vercel MCP 403 Forbidden — Team Owner Cannot Access Projects via ChatGPT#50644
  15. ChatGPT Vercel MCP: team-scope 403 after reconnection; no grant controls in connected-app UI#50599
  16. ChatGPT Vercel MCP: create_project returns 403 for confirmed team Owner#50595
  17. ChatGPT Vercel MCP: authorized team missing, deployment requests return 403#50589
  18. ChatGPT Vercel OAuth: team-scoped Web Analytics requests return 403#50582
  19. Vercel MCP / ChatGPT Integration Returns 403 Forbidden#50576
  20. Vercel MCP — Team-scoped API returns 404/403 for existing project#50572
  21. ChatGPT Vercel MCP authenticates owner but lists no teams and returns 403#50559
  22. Subject: Vercel MCP – 403 Forbidden persists after OAuth reauthorization with Team access#50542
  23. Vercel MCP (ChatGPT) – 403 Forbidden on Team-Scoped API Requests Despite OWNER Access#50522
  24. ChatGPT OAuth connected, but Vercel MCP returns 403 for project access#50496
  25. Vercel MCP en Codex devuelve 403 para mi equipo#50430
  26. Vercel MCP Beta – ChatGPT cannot access existing projects (404 error)#50402
  27. wasted afternoon#50356
  28. ChatGPT Vercel connector returns zero teams and 403 after reconnect#50323
  29. ChatGPT Vercel MCP returns 403 for Team despite Owner access and successful OAuth#50291
  30. ChatGPT Vercel connection returns no teams and 403 after authorization#50276
  31. Vercel MCP: OAuth connected, but zero teams and team-scope 403 in Codex#50176
  32. ChatGPT Vercel MCP returns 403 after successful OAuth/reconnect#50122
  33. ChatGPT Vercel MCP Connector Cannot Access My Project#50019
  34. Vercel MCP OAuth returns 403 Forbidden despite valid team access#49978
  35. ChatGPT Vercel MCP — authorized team returns 0 projects and get_project has parameter mapping error#49944
  36. ChatGPT Vercel MCP returns 403 Forbidden after successful OAuth authorization#49807
  37. ChatGPT Vercel MCP OAuth succeeds but returns 0 teams#49745
  38. Codex MCP OAuth succeeds, but list_teams is empty and team requests return 403#49678
  39. ChatGPT Vercel MCP returns empty projects and 404 with explicit team scope#49644
  40. ChatGPT Vercel MCP OAuth incorrectly requires 2FA and returns 403/404 for valid team scope#49595
  41. Vercel MCP in ChatGPT: empty projects and 403 despite explicit teamId#49520
  42. ChatGPT Vercel MCP returns empty projects and 404 with explicit team scope#49331
  43. Vercel integration in ChatGPT: empty team list and “Failed to list projects” after reconnecting#49313
  44. ChatGPT Vercel MCP returns empty teams and 403 after authorization#49271
  45. Vercel MCP returns empty projects and 403 for team-owned project#49232
  46. ChatGPT Vercel MCP returns empty teams after successful OAuth#49188
  47. Vercel MCP con ChatGPT: no aparecen equipos y falla la consulta de proyectos#49156
  48. ChatGPT Vercel MCP: empty teams list and 403 after reauthorization#49054
  49. Vercel MCP in Codex: empty teams and 403 despite active OAuth connection#49042
  50. Official Vercel MCP in ChatGPT: empty teams and 403 after OAuth reconnection#49024
  51. Vercel MCP in ChatGPT Work: team access fails and OAuth registration rejects redirect URI#48983
  52. Vercel MCP in ChatGPT Work: team access fails and OAuth registration rejects redirect URI#48978
  53. Vercel MCP in ChatGPT returns empty projects and 404/403#48886
  54. Vercel MCP returns 0 teams and 403 for valid team/project#48813

Do you work on Vercel?

Claim its RAP Sheet to see what your users report and answer them in one place.

Claim a tool