You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
MCP client doesn't follow specification for Authentication #1492
When opencode tries to connect to a remote MCP if the POST request to the endpoint returns 401 an authentication flow should start opening a browser allowing the user to authenticate with the mcp server.
Currently it just hangs, even preventing the chat from start (possibly related to #1001#854 )
Enterprise MCP Testing: Authentication Gap Confirmed
We've conducted extensive enterprise MCP testing and can confirm this authentication gap has significant real-world impact.
Our Finding: When connecting to Atlassian MCP servers (https://mcp.atlassian.com/v1/sse), OpenCode hangs exactly as described instead of initiating OAuth flow.
Workaround Required: Had to deploy mcp-remote as a local proxy to bridge the authentication gap:
Reference Implementation: Claude Code handles this correctly with native SSE transport + OAuth flows, providing seamless multi-instance enterprise authentication.
Impact: This gap forces enterprise users to rely on third-party proxy solutions, creating additional complexity and potential coordination issues for multi-tenant scenarios.
Activity
clouatre commentedon Sep 14, 2025
Enterprise MCP Testing: Authentication Gap Confirmed
We've conducted extensive enterprise MCP testing and can confirm this authentication gap has significant real-world impact.
Our Finding: When connecting to Atlassian MCP servers (
https://mcp.atlassian.com/v1/sse), OpenCode hangs exactly as described instead of initiating OAuth flow.Workaround Required: Had to deploy mcp-remote as a local proxy to bridge the authentication gap:
{ "atlassian_server": { "type": "local", "command": ["mcp-remote", "https://mcp.atlassian.com/v1/sse"], "enabled": true } }Reference Implementation: Claude Code handles this correctly with native SSE transport + OAuth flows, providing seamless multi-instance enterprise authentication.
Impact: This gap forces enterprise users to rely on third-party proxy solutions, creating additional complexity and potential coordination issues for multi-tenant scenarios.
Technical details: Our comprehensive testing documented at OpenCode MCP Feasibility Report
the-vampiire commentedon Oct 4, 2025
experiencing this issue with the cloudflare MCP. it briefly shows an error then does nothing (chat continues but MCP is locked out).
ran with
--print-logsand got thisminimal reproduction
opencode.json{ "$schema": "https://opencode.ai/config.json", "mcp": { "cloudflare-docs-mcp": { "type": "remote", "url": "https://docs.mcp.cloudflare.com/sse", "enabled": true }, "cloudflare-bindings-mcp": { "type": "remote", "url": "https://bindings.mcp.cloudflare.com/sse", "enabled": true } } }then issue this command
opencode run 'please try using the cloudflare MCP tools' --print-logserror occurs even if you are authenticated through
wrangler loginrekram1-node commentedon Oct 4, 2025
Yeah @thdxr has been working on remote mcp support, should be here soon.
the-vampiire commentedon Oct 5, 2025
if it helps i'm also experiencing an issue when using the remote-mcp package (that cloudflare suggests as a fallback).
rekram1-node commentedon Oct 6, 2025
@the-vampiire is it a separate issue or same issue
the-vampiire commentedon Oct 7, 2025
same one. just wanted to let you know if it helps with debugging.
i tried:
testing in claude code w 4.5 it worked fine.
thdxr commentedon Mar 25, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
feat(landing): markdown negotiation, API catalog, WebMCP (anomalyco#1492