mcp-env-mux

# mcp-env-mux Merge multiple instances of the same MCP server across environments into a single endpoint with a unified `env` parameter. ## Problem When you connect the same MCP server (e.g., Coralogix, Datadog) from multiple environments (prod, staging, dev), each instance exposes identical tool definitions. Your MCP client sees every tool duplicated per environment, wasting context window tokens and creating a confusing tool list. ## Solution mcp-env-mux sits in front of your MCP backends as a proxy. It discovers tools from each backend, merges identical definitions into a single tool with an injected `env` parameter, and routes calls to the correct backend based on the caller's `env` selection. One tool instead of N copies. ## Quick Start ### Without auth ```bash # Install pip install -e . # Set your API keys as environment variables export BACKEND_PROD_API_KEY="your-prod-key" export BACKEND_STAGING_API_KEY="your-staging-key" # Create a config file (see Configuration below) # Validate your config and check for schema mismatches mcp-env-mux --config config.json --test-schema # Start the proxy mcp-env-mux --config config.json ``` ### With auth enabled ```bash # Optional: set Azure client secret via env var export AZURE_CLIENT_SECRET="your-azure-client-secret" # Start the proxy with an auth-enabled config mcp-env-mux --config config.json ``` When the `auth` block is present in the config, the proxy enables JWT Bearer auth, OAuth login routes, RBAC enforcement for tool calls, and a UI for minting long-lived bot tokens. The proxy also exposes operational HTTP endpoints: - `/metrics` (or your configured metrics path) for Prometheus metrics - `/healthz` for process liveness - `/readyz` for startup readiness > For Azure / Microsoft Entra ID setup from scratch, including **both** required redirect URIs (`/auth/callback` and `/ui/callback`), see **`AZURE_SETUP.md`**. ## Configuration The config file is JSON with a required `environments` object and an …