mcp -multiverse

The Multiverse MCP Server lets you run multiple isolated instances (universes) of the same MCP server type so they can operate without conflicts. Each universe has its own configuration, environment, filesystem access, and function namespace, enabling you to run separate projects or environments (e.g., different databases, tokens, or root paths) using a single multi-instance server. Use the multiverse setup to define per-universe servers, path resolution rules, file watching for automatic restarts, and optional function hiding to tailor what clients can access. You can start multiple universes by launching separate MCP servers within the same multiverse.json configuration or by wiring multiple entries in Claude Desktop for automatic startup. The included examples show how to configure multiple instances of different server types and how to hide or disable specific servers or functions.

Prerequisites:

• Node.js (recommended LTS) and npm installed on your machine.
• Claude Desktop (if you plan to manage universes via Claude as described in the README).

Installation steps:

1. Ensure Node.js and npm are available:
   • node -v
   • npm -v
2. Install and/or prepare Claude Desktop and ensure it’s configured to read multiverse.json (per README instructions).
3. Create your multiverse.json configuration file describing one or more universes. Example structure is provided in the README. You don’t need to install a local package globally; the server is typically started via npx as shown in the mcp_config example.
4. Start the multiverse server by running the configured command (for example): npx -y @lamemind/mcp-server-multiverse@latest /path/to/your/multiverse.json

Notes:

• You can embed the multiverse JSON path directly in your configuration file for Claude Desktop to seed and restart instances automatically.
• If you prefer to pin a version, replace @latest with a specific version like @1.2.3 in the command arguments.

Tips and considerations:

• Each universe is isolated by its own configuration, environment variables, and root/file system view. Use pathResolution to hide sensitive root paths when exposing filesystem servers.
• You can enable fileWatch in a universe to automatically restart on changes in the watched directory.
• Use hideFunctions to restrict access to sensitive operations for any wrapped server.
• The enabled flag can be used to temporarily disable a universe without removing its configuration.
• When using npx, you can pin specific server packages (e.g., @lamemind/mcp-server-mysql) inside each universe's servers list to create isolated instances with unique settings.
• Ensure the JSON path you provide in each universe exists and is readable by the runtime process.