mcpmux_list_spacesLABSCO SUMMARY
Routing by folder is the idea that earns it a place, not the config deduplication.
Every client reporting the folder it is working in means the same assistant gets database tools in your backend repo and search tools in a docs folder, without you switching anything. The self-management tools are gated the right way round: discovery runs silently, and anything that changes your setup shows the exact tool diff and waits for a click.
What it is
A desktop gateway for MCP servers. You install servers from a built-in registry, keep their credentials in the OS keychain, and point every client at a single local endpoint; routing decides which tools each session actually sees.
What you get
- A local gateway on localhost:45818 that every MCP client connects to with one config block
- A built-in registry of servers to install with a click, credentials entered once
- Spaces — isolated environments, each with their own servers, credentials and permissions, switched from the sidebar
- Workspaces — map a folder to a toolset, so opening your backend repo and opening a docs folder give the agent different tools
- FeatureSets — curated bundles that control exactly which tools, prompts and resources are exposed
- A live view of connected clients, with per-app routing and the ability to revoke a connection
- mcpmux_list_spaces, mcpmux_list_all_tools, mcpmux_search_tools, mcpmux_list_feature_sets — the meta-tools an assistant uses to discover what is available
- mcpmux_manage_feature_set and mcpmux_bind_current_workspace — the assistant proposes a toolset and pins it to a folder; both are writes and both ask for approval first
Requirements
Windows 10+, macOS 12+ or Linux, and at least one MCP client. Install the desktop app from the download page — it runs in the system tray and creates a default Space for you. Credentials are encrypted with AES-256-GCM and held in the OS keychain rather than in plain-text JSON. Start the gateway from the dashboard, then point each client at the local endpoint.
Setup effort
One command — curl -fsSL https://install.mcpmux.com | bash
USE CASES
01
Adding a server without editing four config files
Install it once in the app and let every connected client see it immediately.
02
Keeping work and personal contexts apart
Put each set of servers and credentials in its own Space and switch between them from the sidebar.
03
Cutting an over-large toolset down
Have the assistant search what is available, compose a focused bundle, and pin it to the current folder — approving each write.
04
Giving a cautious client fewer powers
Build a read-only bundle and route the folder that client works in to it.
05
Auditing what is connected
See every AI app attached to the gateway, how it is routed, and revoke the ones you do not recognise.
5 tools
Listed in project docs. Your client may show a different list.
mcpmux_list_all_toolsmcpmux_search_toolsmcpmux_manage_feature_setmcpmux_bind_current_workspaceBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation. The built-in tool reference lists six, including mcpmux_list_feature_sets, and they appear only after you enable Tool Optimization for a Space on the Built-in page. Other tools come from the backend servers you install.
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
Download McpMux for your platform (Windows, macOS, Linux) - Linux: curl -fsSL https://install.mcpmux.com | bash; macOS via Homebrew: brew install --cask mcpmux/tap/mcpmux
Add servers - use the Discover tab to browse 100+ servers
Paste the config - copy the snippet from the Dashboard into your AI clients
MCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"mcpmux": {
"url": "http://localhost:45818/mcp"
}
}
}GitHub Copilot in VS Code
GITHUB COPILOT IN VS CODE · JSON
{
"servers": {
"mcpmux": {
"url": "http://localhost:45818/mcp"
}
}
}Windsurf
WINDSURF · JSON
{
"mcpServers": {
"mcpmux": {
"serverUrl": "http://localhost:45818/mcp"
}
}
}
