4 people reported
All time, since Sep 23, including 1 thumbs-up on GitHub.
MCP OAuth resource double-encoded
“MCP OAuth fails in the VS Code extension for any HTTP MCP server whose URL has a query string.”
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/claude-code/issues/3063/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 OAuth resource parameter double-encoded when URL has query string. The authorize URL carries resource=...%253F..., so servers like Supabase reply "Resource must be a valid MCP endpoint".
Is this your bug?
File my report- Where
- VS Code extension
- Error text
{"message":"resource: Resource must be a valid MCP endpoint"}- Versions
- 2.1.296
- Platforms
- macOS, Windows
- How bad
- Breaks a normal workflow.
Original reports3, newest first
- VS Code extension double-encodes MCP OAuth authorize URL (resource=...%253F...), breaking servers with query strings#103535
- MCP OAuth: resource parameter is double-encoded when the server URL has a query string (Supabase returns 422)#101205
- VS Code extension double-encodes MCP OAuth resource parameter when server URL has a query string (still present in 2.1.280)#96488