Log inSubmit server
MCP Server Multiverse logo

MCP Server Multiverse

by lamemind

Runs isolated instances of MCP servers with separate namespaces, configuration, filesystem paths, and optional function filtering.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Server Multiverse

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "lamemind-mcp-server-multiverse": {
      "command": "npx",
      "args": [
        "-y",
        "@lamemind/mcp-server-multiverse@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @lamemind/mcp-server-multiverse@latest

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 24d ago.

Overview

The lamemind/mcp-server-multiverse MCP server wraps multiple MCP server instances behind isolated namespaces and configurations. It launches configured child servers from JSON, prefixes their functions, and can map paths or hide selected functions. Use it when one client needs separate instances of the same server type, such as databases, Git repositories, or filesystem roots. It also supports disabling configured servers and restarting watched servers during development.

Use cases

  • Run separate MySQL server instances for different databases
  • Expose multiple filesystem roots with distinct namespaces
  • Test a local MCP server with automatic restarts
  • Restrict wrapped servers by hiding selected functions

Key features

  • Isolated MCP server instances
  • Configurable function prefixes
  • JSON-based child server configuration
  • Function hiding and server disabling
  • File-watched server restarts
  • Path argument resolution

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 77d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9h ago via OSV.dev · @lamemind/mcp-server-multiverse@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars82Stargazers on the source repository.
npm downloads46Package downloads in the last 30 days.
Last commit7mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Server Multiverse works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Server Multiverse

lamemind/mcp-server-multiverse is an MCP server that connects an MCP client to multiple configured child MCP servers. Its main tools are the wrapped servers’ functions, exposed with unique prefixes; it also supports isolated configurations, path resolution, function hiding, disabled entries, and file-watched restarts.

Install it through an MCP client configuration using npm and `npx`. In Claude Desktop, add a server entry that runs `npx -y @lamemind/mcp-server-multiverse@latest` and passes the path to a JSON configuration file.

Create separate multiverse configurations or separate parent entries, then give each child server its own command, arguments, environment, and function prefix. This supports cases such as two MySQL instances pointing at different databases.

Add a `hideFunctions` array to the child server entry. Functions listed there are not registered by the parent server and are unavailable to the MCP client.

Related MCP servers

All in Aggregators All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Server Multiverse AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/lamemind-mcp-server-multiverse?style=directory)](https://allmcps.com/mcp/lamemind-mcp-server-multiverse)
HTML Embed
<a href="https://allmcps.com/mcp/lamemind-mcp-server-multiverse"><img src="https://allmcps.com/api/badge/lamemind-mcp-server-multiverse?style=directory" alt="MCP Server Multiverse on AllMCPs" /></a>