Multiverse MCP Server

Multiverse MCP Server is an MCP server that acts as a middleware proxy for running multiple, isolated instances of Model Context Protocol servers simultaneously. It connects upstream MCP clients, such as Claude Desktop, to various child MCP servers including filesystem, database, and Git integrations under distinct namespaces. Software engineers and AI developers use this server to manage multiple project environments or separate identical server types without collisions. It allows users to run identical MCP server commands with differing credentials or root directories by applying prefix namespaces to exposed tools. The proxy also features file watching capabilities to restart development servers automatically, relative path resolution to conceal local root paths, and granular function masking to disable dangerous commands or suppress unused tools across individual instances.

Category: AI & LLM Tooling

Tags: middleware, namespaces, orchestration, proxy

Visit Multiverse MCP Server

How to install and configure Multiverse MCP Server

1. Ensure Node.js, npm, and Claude Desktop are installed on your system. 2. Create a JSON configuration file (for example, job-multiverse.json) defining your child servers, command arguments, environment variables, prefixes, or file-watch settings. 3. Open your Claude Desktop configuration file (~/Library/Application Support/Claude/claude_desktop_config.json on macOS or C:\Users\<username>\AppData\Roaming\Claude\claude_desktop_config.json on Windows). 4. Add an entry under mcpServers pointing to your configuration: json { "mcpServers": { "job-multiverse": { "command": "npx", "args": [ "-y", "@lamemind/mcp-server-multiverse@latest", "/path/to/your/job-multiverse.json" ] } } } 5. Restart Claude Desktop to automatically launch the configured instances.

What you can do with Multiverse MCP Server

• Running duplicate database servers simultaneously by routing to separate MySQL instances with unique credentials and function name prefixes. * Restricting Claude's tool surface by applying the hideFunctions setting to remove sensitive actions like repository deletion or file overwriting. * Isolating project workspaces with multiple filesystem servers while using pathResolution to hide full machine directories from the client. * Developing custom MCP servers locally using fileWatch to trigger automatic graceful reloads whenever index files are modified. * Toggling child server instances on or off during testing workflows by changing the enabled boolean without removing server definitions.

Key facts

• https://github.com/lamemind/mcp-server-multiverse
• AI & LLM Tooling, Developer Tools & Code Intelligence
• middleware, namespaces, orchestration, proxy

Part of MCP Servers

How do I install Multiverse MCP Server?

You can run it using npx with the package @lamemind/mcp-server-multiverse@latest. In your Claude Desktop configuration file, define a server entry that executes npx with the path to your custom multiverse JSON configuration file, which specifies child servers and settings.

What can Multiverse MCP Server do?

It serves as an orchestration proxy that launches and manages child MCP servers. It prefixes tool names to prevent conflicts between multiple instances of the same tool, hides selected functions, watches files to restart local development servers, and rewrites paths using path resolution.

Which MCP clients work with Multiverse MCP Server?

It works with any Model Context Protocol client that supports stdio-based servers. The documentation specifically details setup instructions for the Claude Desktop application across macOS and Windows.

Is Multiverse MCP Server open source?

Yes, Multiverse MCP Server is open source and licensed under the MIT License. The code and issue tracker are publicly accessible on GitHub under the repository lamemind/mcp-server-multiverse.