Multiverse MCP Server

Name: Multiverse MCP Server
Author: lamemind

@lamemind

About Multiverse MCP Server

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

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "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"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Multiverse MCP Server?

A middleware server that enables multiple isolated instances of the same MCP servers to coexist independently with unique namespaces and configurations. Each "universe" maintains its own configuration, filesystem access, and function naming, allowing developers to run multiple instances of the same server type (e.g., MySQL, Git, filesystem) without conflicts.

How to use Multiverse MCP Server?

Install via npm, add entries to your claude_desktop_config.json, and point each entry to a JSON configuration file that defines the wrapped servers. The server is invoked with npx -y @lamemind/mcp-server-multiverse@latest <config.json>. The JSON configuration supports command, arguments, environment variables, path resolution, file watching, function hiding, and server enabling/disabling.

Key features of Multiverse MCP Server

Run multiple isolated instances of the same MCP server type.
Automatic server restart with file watching during development.
JSON-based configuration system for each universe.
Hide specific functions from wrapped servers.
Temporarily disable servers with the enabled flag.
Path resolution hides absolute paths from the client.

Use cases of Multiverse MCP Server

Run multiple MySQL servers pointing to different databases without interference.
Use several Git servers with different personal access tokens side by side.
Serve multiple filesystem MCP servers with distinct root directories and hidden paths.
Develop and test a custom MCP server with automatic restart on file changes.
Restrict access to dangerous functions (e.g., delete_repository) while exposing other capabilities.

FAQ from Multiverse MCP Server

What is Multiverse MCP Server and how does it differ from a single MCP server?

It allows multiple isolated instances of the same MCP server type to run simultaneously with separate namespaces, configurations, and function prefixes, preventing conflicts that would occur when running the same server type multiple times.

What are the dependencies and runtime requirements?

Requires npm and the Claude Desktop app. The server is run as a sub‑server of Claude Desktop via claude_desktop_config.json.

Where is the configuration stored?

Configuration is defined in JSON files on the local filesystem, referenced from claude_desktop_config.json. Each JSON file specifies the universe name, function prefix, and list of wrapped servers.

How do I hide specific functions from a wrapped server?

Use the hideFunctions array in a server’s configuration block. Listed functions will not be registered or available to the client (e.g., Claude Desktop).