MCP with oauth doesn't work

[klaudworks]

Description

Configured MCP like this inside my project:

"mcp": {
  "jira": {
    "type": "remote",
    "url": "https://mcp.atlassian.com/v1/sse"
  }
},

opencode mcp auth jira shows:

opencode mcp auth jira

┌  MCP OAuth Authentication
│
▲  No OAuth-enabled MCP servers configured
│
●  Add OAuth config to a remote MCP server in opencode.json:
│
●
│    "mcp": {
│      "my-server": {
│        "type": "remote",
│        "url": "https://example.com/mcp",
│        "oauth": {
│          "scope": "tools:read"
│        }
│      }
│    }
│
└  Done

I thought it may also help to try to invoke the tools and then the Oauth process will start but the agent doesn't know the tools.

OpenCode version

1.0.150

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

macOS 26.1

Terminal

iTerm 2

[github-actions]

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

• [FEATURE]: Allow to enable MCP on a per-agent basis #5373: [FEATURE]: Allow to enable MCP on a per-agent basis (related MCP configuration challenges)
• [FEATURE]: Support MCP servers that require POST-based or non-standard SSE handshake #5371: [FEATURE]: Support MCP servers that require POST-based or non-standard SSE handshake (related MCP server compatibility)
• Remote MCPs with auth header broke in latest update #5328: Remote MCPs with auth header broke in latest update (related to MCP authentication in recent versions)
• {env:...} variable substitution inconsistently fails for specific MCP server URLs #5299: {env:...} variable substitution inconsistently fails for specific MCP server URLs (related to MCP configuration and environment variables)

Feel free to ignore if none of these address your specific case.

[jmhill]

I got the same issue (opencode mcp auth atlassian failed with the same message about No Oauth-enabled MCP servers configured), but when I set up opencode.json to use the local proxy instead, I was able to use Atlassian MCP. Not a solution, but hopefully a workaround that could help.

{
	"$schema": "https://opencode.ai/config.json",
	"mcp": {
		"atlassian": {
			"type": "local",
			"command": ["npx", "-y", "mcp-remote", "https://mcp.atlassian.com/v1/sse"]
		}
	}
}

[daraghscopey]

I got a similar issue in trying to connect the linear remote mcp server.

I had to add this "oauth": {} to the config, and then when I ran opencode mcp auth linear it properly kicked off the auth flow.

{
    "$schema": "https://opencode.ai/config.json",
    "mcp": {
        "linear": {
            "type": "remote",
            "url": "https://mcp.linear.app/mcp",
            "enabled": true,
           "oauth": {}
        }
    }
}

[klaudworks]

thank you. adding "oauth": {} actually fixed it.