2 people reported

All time, since Sep 25.

MCP log reads return 403

“I am experiencing a persistent HTTP 403 Forbidden error when accessing deployment build logs and runtime logs through the ChatGPT Vercel MCP integration.”

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/9125/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

MCP log tools return 403 despite successful OAuth. list_deployment_events and get_runtime_logs fail for team Owners, while project settings and deployment details read successfully through MCP.

Is this your bug?

File my report
Where
MCP server
Error text
Not authorized: Trying to access resource under scope ‘reitojike’.
How bad
Breaks a normal workflow.

Not quite your bug?

  1. MCP returns 403 and empty teams after successful OAuth60 people
  2. MCP returns 404 user and 403 team errors after OAuth2 people
  3. MCP project creation 4032 people

Original reports2, newest first

  1. Vercel MCP returns 403 Forbidden when reading deployment logs#50919
  2. Project-specific Vercel MCP OAuth succeeds, but build and runtime logs return 403#49712

Do you work on Vercel?

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