MCP Docker servers fail to connect after upgrade from v1.1.6 to v1.1.7+ #8171

Description

Docker-based MCP servers that were working correctly in OpenCode v1.1.6 fail to connect after upgrading to v1.1.7. The MCP server container starts successfully and reports healthy status, but OpenCode cannot establish connection. Tools become unavailable with no error message displayed.

Expected Behavior

Docker-based MCP servers should connect and register tools just as they did in v1.1.6. The server should show all tools available and respond to operations.
Actual Behavior

• MCP server container starts successfully (logs show "Server healthy")
• Container reports model loaded, tools registered
• OpenCode shows no MCP tools available OR connection fails silently
• No explicit error message in OpenCode UI
• Downgrading to v1.1.6 restores functionality immediately

Configuration

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "memory-mcp": {
      "type": "local",
      "command": [
        "docker", "run", "--rm", "-i",
        "--name", "memory-mcp",
        "-v", "memory-mcp-data:/data",
        "-v", "/path/to/project:/project:ro",
        "-e", "RECONNECT_TIMEOUT=60",
        "ghcr.io/pomazanbohdan/memory-mcp-1file:latest"
      ],
      "enabled": true
    }
  }
}

Related Issues

• #6909 — MCP timeout after v1.1.1 update (same pattern: MCP fails after version upgrade)
• #829 — Unstable MCP servers, no retry mechanism (OpenCode gives up on connection)
• #731 — MCP hangs without health checks
• #834 — SSE remote servers fail
• oh-my-opencode #493 — MCP detected as type=remote instead of local after reinstall

Additional Context

• Issue appeared immediately after upgrading from v1.1.6 to v1.1.7
• Rolling back to v1.1.6 restores full functionality
• Docker container runs correctly outside OpenCode (tested manually with docker run)
• No changes to configuration between versions
• Similar pattern reported in oh-my-opencode Formatter for Kotlin #493 (MCP detected as type=remote instead of local after reinstall)

OpenCode version

v1.1.7+

Steps to reproduce

1. Have a working MCP configuration with Docker-based server (type: local, command: docker run ...)
2. Verify MCP works in OpenCode v1.1.6 (all tools available, operations succeed)
3. Upgrade OpenCode from v1.1.6 to v1.1.7
4. Start a new OpenCode session
5. Observe MCP section - server appears disconnected or tools unavailable

Operating System

• OS: Linux (Ubuntu)
• OpenCode Version: v1.1.7 (fails) / v1.1.6 (works)
• MCP Server: Docker container (STDIO transport)