lamemind/mcp-server-multiverse

A middleware server that enables multiple isolated instances of the same MCP servers to coexist independently with unique namespaces and configurations.
The Multiverse MCP Server creates isolated operational spaces where identical MCP servers can run simultaneously without conflicts. Each "universe" maintains its own configuration, filesystem access, and function naming, enabling developers to run multiple instances of the same server type while maintaining complete separation between different contexts or projects.
Key Features
Run Multiple Instances
Run multiple instances of the same MCP server type independently and simultaneously. Each instance operates in its own isolated universe with separate configurations. This enables scenarios like:
- Multiple MySQL servers mcp-server-mysql pointing to different databases
- Multiple Git servers mcp-server-git with different Personal Access Tokens
- Multiple filesystem servers mcp-server-filesystem accessing different root paths
Automatic Server Restart
Register your MCP server with file watching capability during development. When enabled, the server automatically detects changes in the specified directory and performs a graceful restart, making development and testing seamless.
JSON-based Configuration System
Define your multiverse setup using a simple and flexible JSON configuration format. Each server instance can be configured with its own:
- Command and arguments
- Environment variables
- Path resolution rules
- File watching settings
Hosted deployment
A hosted deployment is available on Fronteir AI.
Installation
First, ensure you've downloaded and installed the Claude Desktop app and you have npm installed.
Next, add this entry to your claude_desktop_config.json
- on Mac, found at ~/Library/Application\ Support/Claude/claude_desktop_config.json
- on Windows, found at C:\Users\ \AppData\Roaming\Claude\claude_desktop_config.json
Now add how many multiverse servers you want to run. For example, if you want to run two instances of mcp-server-multiverse, one for your job and one for your side project, you can add the following configuration:
This config allows Claude Desktop to automatically start the mcp-server-multiverse instances when you start the app.
Configuration Examples
Create two isolated instances of mcp-server-mysql with different databases
Your job-multiverse.json file
~~~JSON
{
"serverName": "JobMultiverse",
"functionsPrefix": "job",
"servers": [
{
"command": "npx",
"args": [
"-y",
"@benborla29/mcp-server-mysql"
],
"env": {
"MYSQL_HOST": "127.0.0.1",
"MYSQL_PORT": "3306",
"MYSQL_USER": "root",
"MYSQL_PASS": "",
"MYSQL_DB": "my-job-db"
}
}
]
}
~~~
Your side-project-multiverse.json file
~~~JSON
{
"serverName": "SideProjectMultiverse",
"functionsPrefix": "side-project",
"servers": [
{
"command": "npx",
"args": [
"-y",
"@benborla29/mcp-server-mysql"
],
"env": {
"MYSQL_HOST": "127.0.0.1",
"MYSQL_PORT": "3306",
"MYSQL_USER": "root",
"MYSQL_PASS": "",
"MYSQL_DB": "side-project-db"
}
}
]
}
~~~
Create an isolated instance of mcp-server-filesystem
- The mcp-server-filesystem's functions will be exposed with side-project prefix, e.g. side-project_read_file, side-project_write_file.
- The root path can be hidden from the client (e.g. Claude Desktop) by using the pathResolution configuration.
Note that pathResolution is optional and is only needed if you want to hide the root path from the client.
Your multiverse.json file
~~~JSON
{
"serverName": "MySideProject",