McpMux: one gateway for MCP servers
McpMux
A desktop app with a local MCP gateway: set servers up once and Cursor, Claude and VS Code connect through a single URL
- 27 ★ on the repository
- Last commit
- GPL-3.0
Broad access
Why this level
- The app stores keys and tokens of every connected server and passes every tool call through itself
- Self-update on launch is on by default, and a new version gets the same rights
Install
- Works in
Manual install
{"mcpServers":{"mcpmux":{"type":"http","url":"http://localhost:45818/mcp"}}}The single block for each client, from the README.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The app stores keys and tokens of every connected server and passes every tool call through itself
- Self-update on launch is on by default, and a new version gets the same rights
This is third-party code. Review the repository files before installing.
What it does
McpMux is a desktop app written in Rust and Tauri 2 for Windows, macOS and Linux. It runs a local MCP gateway at http://localhost:45818/mcp, and every client, whether Cursor, Claude Desktop, VS Code, Windsurf or Claude Code, gets all servers from one config. Add a server in McpMux and it appears in every client with no restart. Servers install from a built-in registry of more than a hundred entries or are added by hand. Keys and OAuth tokens live in the operating system keychain, and clients' plain JSON files do not hold them. Workspaces (Spaces) separate servers, credentials and permissions, for example for work and for personal projects. Feature Sets limit which tools, prompts and resources a client sees, and a folder binding picks the set for the open project. Built-in tools mcpmux_list_spaces, mcpmux_list_all_tools, mcpmux_search_tools, mcpmux_manage_feature_set and mcpmux_bind_current_workspace help an agent assemble a short toolset for itself. A request starting with `@mux` triggers them, and changes go through an approval dialog.
Who it is for. Developers who use several AI clients and are tired of copying the same set of MCP servers and keys into four configs.
Good fit when
- The same GitHub, Slack and PostgreSQL are needed in Cursor, Claude and VS Code, and a key has to be changed in each client
- API keys sit in plain JSON files and you want them in the system keychain
- Work databases and personal projects must stay apart so a query from a home repository never reaches a work database
- An agent is handed a hundred tools and picks the wrong ones: a short set per folder cuts token use
- A read-only mode needs a set with the write tools switched off
Not a fit when
- You have one client and one or two servers: the client's own config is simpler than any gateway
- You need to run on a server without a graphical interface: McpMux ships as a desktop app
- You need cloud sync of settings: the authors say it is coming later
Example request
@mux build a minimal toolset for this Next.js repository and pin it to the current folderMCP
- Transport
- http
- Authentication
- OAuth
Limitations
McpMux installs as an app: installers are at mcpmux.com/download and the README has no install command. The gateway listens on 127.0.0.1 only, so it serves clients on the same machine.
The license is GPL v3, and the app updates itself on launch by default, which can be switched off in settings. Cloud sync is, by the authors' account, still planned. Every tool call goes through the intermediary, so its permissions and bugs affect every connected client. The registry name com.mcpmux matches the project domain.
How to disable. Remove the mcpmux entry from each client's config and quit the app. Keys of servers added to McpMux live in the system keychain, so revoke them there or at the services themselves.
FAQ
How do I connect Cursor or Claude to McpMux?
Install the app, add servers and paste one block into the client config: a mcpmux server with type http and address http://localhost:45818/mcp. The snippet is ready on the McpMux dashboard.
Where are server keys stored?
In the operating system keychain: DPAPI on Windows, Keychain on macOS and libsecret on Linux. Field-level AES-256-GCM encryption is added for data in the database.
What is a Feature Set?
A set that defines which tools, prompts and resources a client sees. You can build a read-only set or one with GitHub and the filesystem for a React project.
What does the @mux prefix do in a request?
It triggers the built-in optimization tools: the agent searches tools, builds a set and binds it to the folder. Reads run silently and any change needs approval.
Is the gateway reachable from the network?
No, it is bound to 127.0.0.1. All MCP traffic stays on your machine.
Discussion
No questions or reviews yet.
Related
MCP serversadd-mcp writes an MCP server into the configs of 25 agents with one command: Claude Code, Codex, Cursor, VS Code, Zed and more
An MCP server that lets an agent read files, search code and run commands in a workspace
A command-line debugger for MCP servers from Giant Swarm: a REPL for tools, OAuth 2.1 and an MCP server mode for Cursor
A lightweight CLI to discover, inspect and call MCP server tools straight from the shell
A fast MCP server in Rust extended with WebAssembly plugins: plugins load from OCI, files, http(s) and s3, and OCI signatures can be verified
A transparent proxy between an AI client and an MCP server: shows every JSON-RPC frame in the terminal, checks a capture in CI and exports spans
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| McpMux: one gateway for MCP servers (this card) | yes | OAuth | 27 | |
| MetaMCP | no | API key | 2,762 | a gateway service for team use, whereas McpMux installs as a desktop app and relies on the system keychain |
| Docker MCP Gateway | yes | not required | 1,631 | runs servers in Docker containers, while McpMux needs no containers |
| mcp-proxy | no | not required | 2,823 | a bridge between MCP transports with no interface and no server registry |
README in short
The README describes the problem of duplicated configs across clients, the gateway design, workspaces, feature sets, self-tuning through @mux and the security model. It links to the site with the server registry, the download page and Discord. The license is GPL v3.