The problem it solves is narrow and real: point two instances of one server at two databases and their tools collide by name and their scopes bleed together. Prefixing every function per universe fixes the collision, and `hideFunctions` doubles as a safety valve — you can register a GitHub server with `delete_repository` simply absent from what the client can call. Platform coverage is honest in the README: verified on Windows, unverified elsewhere.
A middleware MCP server that wraps other MCP servers so identical ones can run at once. Each wrapped instance lives in its own "universe" with a separate configuration, filesystem scope and function-name prefix, defined in a JSON file.
- Multiple instances of one server type running together — two `mcp-server-mysql` pointed at different databases, two `mcp-server-git` with different tokens, two filesystem servers on different roots
- A function-name prefix per universe (`functionsPrefix`), so `read_file` from one instance and another never clash as the client sees them
- A root path hidden from the client through `pathResolution`, rewriting the arguments named in `applyTo`
- Automatic graceful restart on file changes for a server under development, via `fileWatch`
- Specific functions hidden from a wrapped server with `hideFunctions` — for example removing `delete_repository` from a GitHub instance
- An instance left in the config but switched off with `enabled: false`
Node and npm, and the Claude Desktop app for the documented setup. Each multiverse is added to `claude_desktop_config.json` as an `npx -y @lamemind/mcp-server-multiverse@latest` entry pointed at your universe JSON file. The package is `@lamemind/mcp-server-multiverse` at 1.1.4. The README marks Windows as verified; macOS and Linux are listed but unchecked. Prompts and Resources are on the to-do list, not yet supported.
One command — npx -y @lamemind/mcp-server-multiverse@latest /path/to/your/job-multiverse.json