Repository navigation
MCP remote servers not configurable as expected #1595
Description
When I try to use the linear MCP server as a remote connection, it keeps saying "MCP server linear failed to start". Running it as a local server seems to work without problems.
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
// Does not work
"linear": {
"type": "remote",
"url": "https://mcp.linear.app/sse"
}
// Works
// "linear": {
// "type": "local",
// "command": [
// "bunx",
// "-y",
// "mcp-remote",
// "https://mcp.linear.app/sse"
// ]
// }
}
}Metadata
Metadata
Assignees
Labels
No labels
Activity
thdxr commentedon Aug 4, 2025
does this require auth? we haven't implemented that yet
samuelbriole commentedon Aug 5, 2025
It might be linked to #988
rmoriz commentedon Aug 8, 2025
I've created PR #1729 which adds verbosity on DEBUG level about MCP connection errors. In my case, the remote MCP was not handling mandatory (by MCP standard) method
notifications/initializedand returned a negative HTTP code, which was the root cause for opencode to disregard it.thdxr commentedon Aug 12, 2025
We're closing this issue as we've resolved the MCP remote server configuration issues. We are tracking auth-related aspects separately in other issues. If you're still experiencing problems with MCP remote server configuration, please feel free to open a new issue with specific details.
fix desktop bootstrap config startup (anomalyco#1595)