4 people reported
All time, since Aug 13.
MCP connection returns HTTP 500 after OAuth authorization
“Your account was authorized, but Vercel returned an error when connecting.”
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/10559/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
Connecting Claude or Claude Code to https://mcp.vercel.com fails after authorizing; reconnecting and re-authenticating still fail.
Is this your bug?
File my report- Where
- MCP endpoint
- Error text
Your account was authorized, but Vercel returned an error when connecting.- Versions
- 56.3.1
- How bad
- Stops work: a core feature can't be used. Some reports say it blocks them completely.
Not quite your bug?
Original reports4, newest first
- Vercel MCP OAuth Connection Error with Claude Custom Connector (Reference: ofid_b6618c465d50b361)#47688
- Vercel MCP connector failing to connect#47685
- Your account was authorized, but Vercel returned an error when connecting.#47681
- Persistent HTTP 500 when connecting to mcp.vercel.com (Claude Code MCP client)#47680