Loading...
Multiverse MCP Server enables running multiple isolated instances of MCP servers with unique namespaces and configurations, enhancing flexibility and isolation.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
Multiverse MCP Server enables running multiple isolated instances of MCP servers with unique namespaces and configurations, enhancing flexibility and isolation.
The Multiverse MCP Server provides a layer of isolation and configuration management, improving safety compared to running multiple servers directly. However, the security of the underlying MCP servers and the configuration of the Multiverse server itself are crucial. It is safe when properly configured with restricted access and careful monitoring, but risky if misconfigured or used with inherently unsafe MCP servers.
Performance depends heavily on the underlying MCP servers and the resources allocated to each instance. Consider resource limits and monitoring to prevent performance bottlenecks.
Cost depends on the resources consumed by the underlying MCP servers. Running multiple instances may increase costs associated with compute, storage, and API usage.
{
"mcpServers": {
"job-multiverse": {
"command": "npx",
"args": [
"-y",
"@lamemind/mcp-server-multiverse@latest",
"/path/to/your/job-multiverse.json"
]
},
"side-project-multiverse": {
"command": "npx",
"args": [
"-y",
"@lamemind/mcp-server-multiverse@latest",
"/path/to/your/side-project-multiverse.json"
]
}
}
}MYSQL_PORTGITHUB_PERSONAL_ACCESS_TOKENnpxExecutes npm package binaries, used to start the underlying MCP servers.
Can execute arbitrary code if the package is malicious or vulnerable.
fileWatchMonitors file changes and restarts the server, useful for development.
If configured improperly, may cause excessive restarts or expose sensitive files.
pathResolutionMaps paths to hide the root path from the client.
Only affects the paths exposed to the client, not the actual filesystem access.
None
cloud
The Multiverse MCP Server provides a layer of isolation and configuration management, improving safety compared to running multiple servers directly. However, the security of the underlying MCP servers and the configuration of the Multiverse server itself are crucial. It is safe when properly configured with restricted access and careful monitoring, but risky if misconfigured or used with inherently unsafe MCP servers.
Autonomy is dependent on the underlying MCP servers configured within the Multiverse setup. The Multiverse server itself primarily manages configuration and isolation.
Production Tip
Monitor the resource usage of each isolated server instance to prevent resource exhaustion and ensure optimal performance.
The `functionsPrefix` is used to namespace the functions exposed by each server, preventing naming conflicts when running multiple instances.
You need to restart the Multiverse server for configuration changes to take effect. If `fileWatch` is enabled, changes to the configuration file will trigger an automatic restart.
Yes, you can configure different versions of the same MCP server in each isolated instance.
`pathResolution` allows you to hide the root path from the client by mapping internal paths to external representations.
The Multiverse server will continue to run, but the functions exposed by the crashed server will be unavailable. You may need to manually restart the crashed server.
The number of MCP servers you can run is limited by the available system resources, such as CPU, memory, and disk space.
Yes, you can use environment variables to configure the underlying MCP servers. These variables are defined in the `env` section of the configuration file.