Problem

When configuring the Unity MCP server for use with Opencode, only the http transport appears to work. There is no documented or functional way to configure the server to use stdio transport, which is the standard transport method for most MCP clients.

Expected Behavior

It should be possible to configure the Unity MCP server with a stdio transport in opencode.json, something like:

json

{
  "mcpServers": {
    "unity": {
      "command": "dotnet",
      "args": ["run", "--project", "/path/to/unity-mcp"],
      "transport": "stdio"
    }
  }
}

Actual Behavior
Only http/sse transport configuration works with Opencode.
When attempting to start a stdio session, the configuration values remain set to HTTP defaults, causing a mismatch between the client's expected transport and the server's actual transport.

Environment

Unity MCP version: 9.6.6
Opencode version: 1.4.11
OS: Mac OS

Additional Context

Most MCP clients (e.g., Claude Desktop, Cursor) default to stdio transport. Adding support for it would improve compatibility.