# lamemind/mcp-server-multiverse [Health: Active]

**Category:** 🔗 Aggregators  
**Repository:** https://github.com/lamemind/mcp-server-multiverse  
**GitHub Stars:** 82  
**npm Downloads (last month):** 46  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/lamemind-mcp-server-multiverse

## Description
A middleware server that enables multiple isolated instances of the same MCP servers to coexist independently with unique namespaces and configurations.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-server-multiverse": {
    "command": "npx",
    "args": ["-y","@lamemind/mcp-server-multiverse@latest"]
  }
}
```

## Documentation

## What lamemind/mcp-server-multiverse does

The lamemind/mcp-server-multiverse MCP server acts as middleware between an MCP client and one or more configured MCP servers. Each configured group runs in its own universe, with a distinct server name, function prefix, environment, and optional path rules. This lets a client use separate instances of the same server type without merging their resources into one namespace.

Typical configurations include two MySQL servers connected to different databases, Git servers using different personal access tokens, or filesystem servers rooted at different directories. The wrapped servers provide the actual domain functions; Multiverse organizes how those functions are exposed to the client.

As a listing in the 💻 Developer Tools category, it fits projects that need controlled composition of local MCP services rather than a new database, filesystem, or source-control API by itself.

## How it works

The lamemind/mcp-server-multiverse MCP server reads a JSON configuration containing a server name, a function prefix, and a list of child servers. Each child entry specifies a command and arguments, with optional environment variables and additional behavior. Child processes are started according to that configuration, and their functions are exposed through the parent MCP server.

Function prefixes distinguish otherwise identical tools. For example, a filesystem server configured with the prefix `side-project` can expose names such as `side-project_read_file` and `side-project_write_file`. `pathResolution` can replace configured root paths in selected function arguments, including `path`, `paths`, or `repo_path`, so the client does not need to receive the original root value.

A child entry can set `enabled` to `false` to keep it in the file while preventing it from starting. `hideFunctions` removes selected functions from the parent server’s registration and from the client’s available tool list. With `fileWatch` enabled, changes under the configured watch path trigger a graceful restart of that child server.

## Setup and configuration

The documented setup uses npm and Claude Desktop. Add an `mcpServers` entry to Claude Desktop’s `claude_desktop_config.json`, invoking the package with `npx` and passing the path to a multiverse JSON file. Multiple parent instances can be added as separate client entries, each with its own configuration file.

A child configuration can launch commands through `npx`, `node`, or `uvx`, depending on the wrapped server. Its `env` object passes environment variables to that child, while `args` supplies command-line arguments. The examples use separate files for job and side-project databases, and show filesystem, GitHub, and locally developed servers.

A hosted deployment is also listed on Fronteir AI. The provided setup instructions specifically document local installation through Claude Desktop; they do not describe additional deployment requirements.

## Tools and capabilities

The lamemind/mcp-server-multiverse MCP server supports:

- Running several instances of the same MCP server type at once.
- Assigning prefixes to avoid function-name collisions.
- Giving each child server separate commands, arguments, and environment variables.
- Hiding selected functions from clients.
- Temporarily disabling child servers with `enabled`.
- Watching a directory and restarting a child server after changes.
- Rewriting configured path arguments with `pathResolution`.

## Limitations and notes

Multiverse does not replace the wrapped MCP servers or define their domain capabilities. Database access, filesystem operations, Git actions, and other functions depend on the child server selected in the configuration.

Environment variables shown in the examples, such as MySQL or GitHub credentials, belong to the wrapped servers. They are not presented as universal variables required by Multiverse itself. Path rewriting is optional and only applies to the function arguments named in `applyTo`.

It also does not state a software license.

_Full upstream README: https://allmcps.com/mcp/lamemind-mcp-server-multiverse/readme_