v4.2.0

SagerNet/sing-boxv4.2.0Jul 20, 2025by ravitemer

AI Summary

Focuses on expanding VS Code compatibility and configuration flexibility for the MCP Hub, allowing for seamless integration with existing IDE workflows.

Key Highlights

Full support for `.vscode/mcp.json` configuration format with JSON5 support.
Added VS Code-style environment variable syntax (e.g., `${env:VARIABLE_NAME}`).
Support for predefined variables like `${workspaceFolder}` and `${userHome}`.
Seamless migration path ensuring existing `.vscode/mcp.json` files work directly.

New Features

VS Code Configuration Compatibility
JSON5 support for config files
VS Code environment variable syntax support
VS Code input variables via MCP_HUB_ENV

Full Release Notes


### Added

- **VS Code Configuration Compatibility**: Full support for `.vscode/mcp.json` configuration format
  - Support for `"servers"` key alongside existing `"mcpServers"` key
  - VS Code-style environment variable syntax: `${env:VARIABLE_NAME}`
  - VS Code predefined variables: `${workspaceFolder}`, `${userHome}`, `${pathSeparator}`, `${workspaceFolderBasename}`, `${cwd}`, `${/}`
  - VS Code input variables via `MCP_HUB_ENV`: support for `${input:variable-id}` syntax
  - JSON5 support for config files: comments and trailing commas now allowed
  - Seamless migration path: existing `.vscode/mcp.json` files work directly with MCP Hub

### Enhanced

- **Configuration System**: Enhanced environment variable resolution with VS Code compatibility
  - Proper priority system: predefined variables → process.env → MCP_HUB_ENV
  - Predefined variables available for placeholder resolution but not passed to server environments
  - Comprehensive test coverage for all VS Code variable types and scenarios