v4.2.0

ravitemer/mcp-hubv4.2.0Jul 20, 2025by ravitemer

AI Summary

Added full VS Code configuration compatibility including support for .vscode/mcp.json format, VS Code-style environment variables, and JSON5 support for config files.

Key Highlights

Full support for .vscode/mcp.json configuration format with 'servers' key
VS Code-style environment variable syntax: ${env:VARIABLE_NAME}
VS Code predefined variables: ${workspaceFolder}, ${userHome}, ${pathSeparator}, etc.
VS Code input variables via MCP_HUB_ENV support
JSON5 support for config files: comments and trailing commas allowed

New Features

VS Code Configuration Compatibility
Enhanced Configuration System with VS Code variable resolution

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