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.
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.
- 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
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.
One command — curl -fsSL https://install.mcpmux.com | bash