anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Feature Request: Add HTTP Streamable transport support for remote MCP servers #5015

New Issue
Closed
opened 2026-02-16 17:47:43 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 17:47:43 -05:00
Owner
Copy Link
Copy Source

Originally created by @chindris-mihai-alexandru on GitHub (Jan 12, 2026).

Originally assigned to: @rekram1-node on GitHub.

Summary

The current type: "remote" MCP configuration only supports SSE (Server-Sent Events) transport. However, the MCP protocol now includes HTTP Streamable transport (also called http or streamable-http), which is used by several major MCP servers including Sanity.

Problem

When configuring Sanity's hosted MCP server:

{
  "mcp": {
    "sanity": {
      "type": "remote",
      "url": "https://mcp.sanity.io",
      "oauth": {}
    }
  }
}

OpenCode fails with:

SSE error: Non-200 status code (405)

This is because Sanity uses HTTP Streamable transport, not SSE. The 405 "Method Not Allowed" occurs because OpenCode sends a GET request expecting SSE, but Sanity expects POST requests for HTTP streaming.

Current Workaround

Using mcp-remote as a local proxy:

{
  "mcp": {
    "sanity": {
      "type": "local",
      "command": ["npx", "-y", "mcp-remote", "https://mcp.sanity.io", "--transport", "http-only"],
      "timeout": 60000
    }
  }
}

This works but adds unnecessary overhead and complexity.

Proposed Solution

Add native support for HTTP Streamable transport in remote MCP configuration:

{
  "mcp": {
    "sanity": {
      "type": "remote",
      "transport": "http",  // or "streamable-http"
      "url": "https://mcp.sanity.io",
      "oauth": {}
    }
  }
}

Or alternatively, a new type:

{
  "mcp": {
    "sanity": {
      "type": "http",  // new type alongside "remote" (SSE) and "local"
      "url": "https://mcp.sanity.io",
      "oauth": {}
    }
  }
}

Reference

Other MCP clients already support this:

  • Claude Code: claude mcp add -t http sanity https://mcp.sanity.io
  • Cursor: { "type": "http", "url": "https://mcp.sanity.io" }
  • VS Code: { "type": "http", "url": "https://mcp.sanity.io" }

See: https://www.sanity.io/docs/compute-and-ai/mcp-server

Environment

Originally created by @chindris-mihai-alexandru on GitHub (Jan 12, 2026). Originally assigned to: @rekram1-node on GitHub. ## Summary The current `type: "remote"` MCP configuration only supports **SSE (Server-Sent Events)** transport. However, the MCP protocol now includes **HTTP Streamable** transport (also called `http` or `streamable-http`), which is used by several major MCP servers including Sanity. ## Problem When configuring Sanity's hosted MCP server: ```json { "mcp": { "sanity": { "type": "remote", "url": "https://mcp.sanity.io", "oauth": {} } } } ``` OpenCode fails with: ``` SSE error: Non-200 status code (405) ``` This is because Sanity uses HTTP Streamable transport, not SSE. The 405 "Method Not Allowed" occurs because OpenCode sends a GET request expecting SSE, but Sanity expects POST requests for HTTP streaming. ## Current Workaround Using `mcp-remote` as a local proxy: ```json { "mcp": { "sanity": { "type": "local", "command": ["npx", "-y", "mcp-remote", "https://mcp.sanity.io", "--transport", "http-only"], "timeout": 60000 } } } ``` This works but adds unnecessary overhead and complexity. ## Proposed Solution Add native support for HTTP Streamable transport in remote MCP configuration: ```json { "mcp": { "sanity": { "type": "remote", "transport": "http", // or "streamable-http" "url": "https://mcp.sanity.io", "oauth": {} } } } ``` Or alternatively, a new type: ```json { "mcp": { "sanity": { "type": "http", // new type alongside "remote" (SSE) and "local" "url": "https://mcp.sanity.io", "oauth": {} } } } ``` ## Reference Other MCP clients already support this: - **Claude Code**: `claude mcp add -t http sanity https://mcp.sanity.io` - **Cursor**: `{ "type": "http", "url": "https://mcp.sanity.io" }` - **VS Code**: `{ "type": "http", "url": "https://mcp.sanity.io" }` See: https://www.sanity.io/docs/compute-and-ai/mcp-server ## Environment - OpenCode version: 1.1.14 - macOS version: 15.7.4 - Affected MCP server: Sanity (https://mcp.sanity.io)
yindo closed this issue 2026-02-16 17:47:43 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#5015
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?