Repository navigation
mcp: remote server with no stored credentials reports "connected"; failures surface as a 404 saying "correct the request" #53804
Description
Description
Configured the Vercel remote MCP in a project opencode.json
("vercel": {"type": "remote", "url": "https://mcp.vercel.com"}) but never ran
opencode mcp auth vercel. From that state every signal points the wrong way:
opencode mcp list→✓ vercel connected- auth-scoped tool calls (
get_auth_user) fail with the upstream
404: not_found. User not found.onGET /v2/user, carrying
remediation: {action: "correct_request"}/ "Correct the request before
retrying" — there is nothing wrong with the request; the server has no identity list_teamsandget_git_deployment_contextreturn{"teams": []}as a
success, which reads as an account/permissions problem
Nothing points at opencode mcp auth <name>. An agent instructed to "surface
the sign-in" has no mechanism to surface one. I only found the cause by reading
~/.local/share/opencode/mcp-auth.json: keys are ["supabase"] — no vercel
entry, i.e. never authenticated, not an expired token.
Expected: either opencode mcp list reports needs_auth for a server with no
stored credentials (the state #53607 describes), or the failed call's error
names opencode mcp auth vercel — the command that fixed #27761.
Environment: opencode v2.0.24, shell /bin/zsh. Related: #27761, #53607.
Plugins
superpowers (plugin); vercel (MCP)
OpenCode version
v2.0.24
Steps to reproduce
- Add to
opencode.json:"vercel": {"type": "remote", "url": "https://mcp.vercel.com"} - Do not run
opencode mcp auth vercel opencode mcp list→✓ vercel connected- Call any auth-scoped tool (e.g.
get_auth_user) →404: not_found. User not found.
withremediation: correct_request
Screenshot or share link
N/A — error payloads quoted above (requestIds available on demand)
Operating System
macOS 26 (Darwin 25.6.0, arm64)
Terminal
VS Code (TERM_PROGRAM=vscode, xterm-256color)
Activity
opencode-agent commentedon Oct 7, 2026
Thanks for the detailed report. I couldn't reproduce this on v2.0.24.
What I tried:
{"mcp": {"servers": {"vercel": {"type": "remote", "url": "https://mcp.vercel.com"}}}}and ranopencode mcp list. It prints⚠ vercel needs authentication, not✓ connected.https://mcp.vercel.comanswers a request without a token with a401and aWWW-Authenticatechallenge, and that is how OpenCode detects that you need to sign in."mcp": {"vercel": {...}}, withoutservers), v2 reportsNo MCP servers configured.Two details point to the
opencodeyou used possibly not being v2:~/.local/share/opencode/mcp-auth.jsonis where v1 (opencode-ai) stores MCP credentials. v2 keeps them in thecredentialtable ofopencode.db, so a missingvercelkey in that file doesn't tell you anything about v2.vercelentry directly undermcpis the v1 config shape.Could you share:
which opencodeandopencode --version, run in the same VS Code terminal where you saw✓ vercel connected. If an agent ran the tools, how was OpenCode started there?mcpsection of youropencode.json, with any secrets removed, and whether you have a global config at~/.config/opencode/opencode.json.opencode mcp logout verceland thenopencode mcp list.Related: #53607 (v2 doesn't import v1 MCP credentials from
mcp-auth.json) and the open PR #53468 (sets servers that return 401 only on tool calls toneeds_auth, with a hint to runopencode mcp auth <name>).opencode-agent commentedon Oct 10, 2026
I'm closing this as not planned because we haven't heard back.
On v2.0.24 with no stored credentials, a Vercel remote MCP server configured under
mcp.serversshows as⚠ vercel needs authentication, not✓ connected.mcp-auth.jsonis v1's credential store, and avercelentry directly undermcpis the v1 config shape. That makes me think theopencodeyou ran may have been v1 (opencode-ai).If it still happens on v2, please comment here with the output of
which opencodeandopencode --versionfrom the same terminal, plus yourmcpconfig with secrets removed, and we can reopen it. Related: #53607 and #53468.