MCP OAuth: opencode mcp auth doesn't refresh token in active sessions

[duke8253]

Description

After re-authenticating an OAuth MCP server with opencode mcp auth , the new token is written to disk but the running MCP connection still uses the stale one.

opencode mcp debug confirms: shows authenticated with a valid token and future expiry, but the HTTP connection test returns 401 Unauthorized. The only workaround is restarting opencode entirely.

Expected: opencode mcp auth should refresh the active MCP connection with the new token, or there should be an opencode mcp reconnect command to re-establish the connection.

Plugins

none

OpenCode version

1.4.1

Steps to reproduce

1. Connect to an OAuth-enabled MCP server (Streamable HTTP transport)
2. Wait for the token to expire or be invalidated server-side
3. Run opencode mcp auth <server> — completes successfully
4. MCP calls still fail with auth errors
5. opencode mcp debug <server> shows valid token but 401 on test

Screenshot and/or share link

No response

Operating System

macos 26.4

Terminal

iTerm2

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Remote MCP OAuth: browser never opens for re-authentication after session loss #16893: Remote MCP OAuth re-authentication after session loss (browser never opens)
• Reauthentication with Jira MCP via Oauth doesn't work #5953: Reauthentication with MCP OAuth doesn't work
• Opencode not handling expired refresh_tokens #13998: Not handling expired refresh tokens (closed)

If your issue is specifically about the running session not picking up a newly written token (stale in-memory connection), it may be distinct from these — but please review to confirm.

[duke8253]

This issue might be a duplicate of existing issues. Please check:

• Remote MCP OAuth: browser never opens for re-authentication after session loss #16893: Remote MCP OAuth re-authentication after session loss (browser never opens)
• Reauthentication with Jira MCP via Oauth doesn't work #5953: Reauthentication with MCP OAuth doesn't work
• Opencode not handling expired refresh_tokens #13998: Not handling expired refresh tokens (closed)

If your issue is specifically about the running session not picking up a newly written token (stale in-memory connection), it may be distinct from these — but please review to confirm.

It's not a duplicate of any of them.

In my case, the authentication succeeds without any problems, meaning it opens a browser and all checks are fine. But after the authentication, opencode still can't fetch anything through the mcp server, and I had to close the process to do a full restart of opencode.

[aks24k]

Having same problem for JIRA mcp.