mcp-registry/lamemind/mcp-server-multiverse

    ==================
      
       /// MCP ///
      /// LAM ///
        
    ==================
        
    [server:online]
    [protocol:ready]

lamemind/mcp-server-multiverse

by lamemind

Middleware MCP server that lets you run many isolated copies of the same MCP server side-by-side (each with its own namespace, env vars, fs root, etc.).

68
14
Open Source

Installation

1. Clone the repository
git clone https://github.com/lamemind/mcp-server-multiverse.git cd mcp-server-multiverse
2. Install dependencies
# with npm npm install # or with yarn yarn
3. Build the TypeScript source (if repository is published as TS)
npm run build # or yarn build # this will emit JavaScript to ./dist
4. Configuration
- Copy the example environment file (if present) or create one:
- Key variables you may find or create:
- Adjust per-namespace configs in /config/* if such directory exists.
cp .env.example .env PORT=3000 # HTTP port the multiverse server will listen on MCP_TARGET_URL=... # Base URL of the downstream MCP server MULTIVERSE_NAMESPACES=uk,eu,us # Comma-separated list of isolated instances DEFAULT_NAMESPACE=uk # Fallback namespace
5. Run the server in dev mode
npm run dev # ts-node/ nodemon watch mode
6. Run the compiled build (production)
NODE_ENV=production node dist/index.js
7. Docker (optional)
docker build -t mcp-server-multiverse . docker run -d -p 3000:3000 --env-file .env mcp-server-multiverse

Documentation

License: MIT License
Updated 7/30/2025