What is Multiverse MCP Server?
A middleware server that enables multiple isolated instances of the same MCP servers to coexist independently with unique namespaces and configurations. Each "universe" maintains its own configuration, filesystem access, and function naming, allowing developers to run multiple instances of the same server type (e.g., MySQL, Git, filesystem) without conflicts.
How to use Multiverse MCP Server?
Install via npm, add entries to your claude_desktop_config.json, and point each entry to a JSON configuration file that defines the wrapped servers. The server is invoked with npx -y @lamemind/mcp-server-multiverse@latest <config.json>. The JSON configuration supports command, arguments, environment variables, path resolution, file watching, function hiding, and server enabling/disabling.
Key features of Multiverse MCP Server
- Run multiple isolated instances of the same MCP server type.
- Automatic server restart with file watching during development.
- JSON-based configuration system for each universe.
- Hide specific functions from wrapped servers.
- Temporarily disable servers with the enabled flag.
- Path resolution hides absolute paths from the client.
Use cases of Multiverse MCP Server
- Run multiple MySQL servers pointing to different databases without interference.
- Use several Git servers with different personal access tokens side by side.
- Serve multiple filesystem MCP servers with distinct root directories and hidden paths.
- Develop and test a custom MCP server with automatic restart on file changes.
- Restrict access to dangerous functions (e.g.,
delete_repository) while exposing other capabilities.
コメント