You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every AI client has its own MCP config file. Same servers, same credentials — duplicated everywhere.
16
+
You use Cursor, Claude Code, VS Code, and Windsurf. They all support MCP. But every client has its own config file — and none of them talk to each other.
17
17
18
18
```
19
19
Cursor → config.json → github, slack, db + API keys
20
-
Claude Desktop → config.json → github, slack, db + API keys (again)
21
-
VS Code → settings.json → github, slack, db + API keys (again)
22
-
Windsurf → config.json → github, slack, db + API keys (again)
20
+
Claude Code → config.json → github, slack, db + API keys (copy-paste)
21
+
VS Code → settings.json → github, slack, db + API keys (copy-paste)
22
+
Windsurf → config.json → github, slack, db + API keys (copy-paste)
23
23
```
24
24
25
-
Add a server? **Update every client.** Rotate an API key? **Update every client.** New project? **Reconfigure everything.**
25
+
Add a server? **Edit four files.** Rotate an API key? **Edit four files.** New teammate, new machine, new project? **Start from scratch.**
26
26
27
-
And all those credentials? Sitting in **plain-text JSON files**on disk.
27
+
And those API keys? Sitting in **plain-text JSON files**anyone can read.
28
28
29
29
## The Fix
30
30
31
-
McpMux is a desktop app that runs a local gateway. Configure your servers once, point all clients to one URL.
31
+
McpMux is a desktop app that runs a local MCP gateway. You configure servers once — every AI client connects to the same URL.
32
32
33
33
```
34
34
Cursor ─┐
35
-
Claude Desktop ─┤──→ McpMux (localhost) ──→ all your MCP servers
35
+
Claude Code ─┤──→ McpMux (localhost:45818) ──→ all your MCP servers
36
36
VS Code ─┤ encrypted credentials
37
37
Windsurf ─┘ one config, one place
38
38
```
39
39
40
-
Add a server in McpMux and every client has it instantly. No files to edit.
40
+
Add a server in McpMux and it appears in Cursor, Claude, VS Code, and Windsurf instantly. No files to edit. No credentials to copy.
41
41
42
42
---
43
43
44
44
## How It Works
45
45
46
-
**1.** Install servers from the built-in registry (or add manually)
46
+
**1.** Install servers from the built-in registry — or add your own
47
47
48
-
**2.** Paste one config into your AI clients:
48
+
**2.** Paste one config into each AI client (the last config you'll ever need):
49
49
50
50
```json
51
51
{
@@ -58,114 +58,77 @@ Add a server in McpMux and every client has it instantly. No files to edit.
58
58
}
59
59
```
60
60
61
-
**3.** Done. All tools from all servers are available in every client.
61
+
**3.** Done. Every tool from every server is available in every client, right now.
62
62
63
-
McpMux routes calls to the right server, refreshes OAuth tokens automatically, and keeps credentials encrypted in your OS keychain. You don't think about it.
63
+
McpMux routes calls to the right server, refreshes OAuth tokens automatically, and keeps credentials encrypted in your OS keychain — you never think about it again.
64
64
65
65
---
66
66
67
67
## Features
68
68
69
-
### Server Management
69
+
### All Your Servers, One Place
70
70
71
-
Add, remove, and monitor all your MCP servers in one place. See connection status, auth type, and transport at a glance.
71
+
No more duplicating server configs across Cursor, Claude, VS Code, and Windsurf. Install a server in McpMux and it's immediately available everywhere. Expand any server to inspect its tools, prompts, and resources. See live connection status. OAuth tokens refresh automatically in the background.
72
72
73
-
73
+
74
74
75
-
### Server Registry
75
+
### 100+ Servers, One Click
76
76
77
-
Browse and one-click install from a curated registry of MCP servers. Filter by category, auth type, or hosting. Cached for offline use. You can also browse the full registry at [mcpmux.com](https://mcpmux.com).
77
+
Stop hunting for MCP server repos and hand-writing transport configs. Browse a curated registry of 100+ servers — GitHub, Slack, PostgreSQL, Docker, Notion, AWS, Azure, and more. Click install, enter your credentials, and the server is live across every AI client you use. You can also browse the full registry at [mcpmux.com](https://mcpmux.com).
80
80
81
-
### Spaces
81
+
### Workspaces That Keep Things Separate
82
82
83
-
Isolated workspaces with their own serversand credentials. Switch between "Work" and "Personal" in one click — your AI clients follow automatically.
83
+
Create isolated Spaces — each with their own servers, credentials, and permissions. A "Work" space for company databases and internal APIs. A "Personal" space for side projects. Switch in one click from the sidebar and every connected AI client follows automatically. No more accidentally querying your personal database from a work project.
84
84
85
-
85
+
86
86
87
-
### Feature Sets
87
+
### Control What Each Client Can Do
88
88
89
-
Control exactly which tools, prompts, and resources are available. Create custom permission bundles like "Read Only" or "Dev Tools" and assign them to clients.
89
+
Not every AI client should have the same power. Create Feature Sets — permission bundles that control exactly which tools, prompts, and resources a client can access. Build a "Read Only" set for cautious workflows, a "React Development" set with just GitHub and Filesystem, or a "Full Stack Dev" set with everything. Assign them per-client so each tool only goes where you want it.
See every AI client connected to your gateway. Manage OAuth registrations and control which space each client can access.
95
+
Cursor, VS Code, Windsurf, Claude Code — see every AI client connected to your gateway in real time. Click any client to manage its workspace, grant or revoke feature sets, and see exactly which tools it can access. New clients authenticate via OAuth with a one-click approval flow.
0 commit comments