Mux MCP server
{
"mcpServers": {
"mcpmux": {
"type": "http",
"url": "http://localhost:45818/mcp"
}
}
}{
"mcpServers": {
"mcpmux": {
"type": "http",
"url": "http://localhost:45818/mcp"
}
}
}{
"mcpServers": {
"mcpmux": {
"type": "http",
"url": "http://localhost:45818/mcp"
}
}
}{
"servers": {
"mcpmux": {
"type": "http",
"url": "http://localhost:45818/mcp"
}
}
}{
"mcpServers": {
"mcpmux": {
"type": "http",
"url": "http://localhost:45818/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.1.1
What it does
McpMux is a local gateway that centralizes MCP server configuration for multiple AI clients (Cursor, Claude Desktop, VS Code, Windsurf, and others). Instead of configuring each client separately with duplicate API keys and server settings, you configure servers once in McpMux and every client connects through a single HTTP endpoint.
- Manage MCP servers from a single dashboard and have all connected AI clients automatically pick up changes without restarting.
- Store API credentials encrypted in your OS keychain instead of duplicated across plain-text config files for each client.
- Create isolated workspaces with different server configurations and switch between them instantly across all connected clients.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.