Skip to content

v2.0.1 — OpenCode compatibility and explicit server startup

Choose a tag to compare

@AlaeddineMessadi AlaeddineMessadi released this 14 Sep 22:37
· 14 commits to main since this release
6466858

Breaking changes

  • Automatic server startup is now opt-in. To retain the previous behavior, set OPENCODE_AUTO_SERVE=true in your MCP client configuration. Otherwise, start OpenCode explicitly with opencode serve --port 4096 or share a TUI started with opencode --port 4096.

Changed

  • Upgrade @opencode-ai/sdk to 1.18.31 and refresh compatible dependencies.

  • Automatic server startup is now opt-in with OPENCODE_AUTO_SERVE=true. By default, connect to an explicitly managed server or a TUI started with opencode --port 4096. This prevents MCP from silently launching a second instance alongside existing TUI sessions (#18).

  • Auto-start only supports loopback HTTP endpoints; remote servers must be started on their own host.

Fixed

  • Normalize local project-init protection checks on Windows, including drive roots, native system directories and case differences.

  • Forward model variants at the prompt body top level, and remove the unsupported shell variant option (community PR #15, @AveryanAlex). Slash commands now send their model as a provider/model string.

  • Format current OpenCode tool-state and diff-patch responses, and recognize tool-only activity without reporting a false credentials failure.

  • Handle stdin closure and SIGHUP when MCP clients disconnect (community PR #16, @potch8228).

  • Preserve POSIX, Windows drive and UNC project paths across client/server OS boundaries. Reject ambiguous relative paths instead of resolving against the MCP process (#13).

  • Let OpenCode validate project directory existence on its own machine, enabling remote servers and containers (#14).

  • Use the asynchronous prompt endpoint in opencode_fire and opencode_run, so dispatch does not wait for inference before returning or polling (#20).

Validation

  • Linux and Windows CI on Node 22 and 24.
  • 370 tests passed; 3 skipped.
  • Dependency audit: zero vulnerabilities.
  • Installed npm tarball smoke test: MCP handshake reports 2.0.1 with 80 tools, 10 resources, and 6 prompts.

Install with npx opencode-mcp@latest.

Version 2.0.0 was unavailable because npm retains a historical publication of that version; 2.0.1 is the published release.