@@ -13,23 +13,42 @@ Create `.mux/mcp.jsonc` in your project root:
1313{
1414 " servers" : {
1515 // Knowledge graph for persistent memory
16- " memory" : " npx -y @anthropic-ai/mcp- server-memory" ,
17- // Access external APIs
18- " github " : " npx -y @modelcontextprotocol/server-github " ,
16+ " memory" : " npx -y @modelcontextprotocol/ server-memory" ,
17+ // Browser automation and screenshots
18+ " chrome " : " npx -y chrome-devtools-mcp@latest --headless " ,
1919 },
2020}
2121```
2222
2323Each entry maps a server name to its shell command. The command must start a process that speaks MCP over stdio (NDJSON format).
2424
25+ ## Slash Commands
26+
27+ Manage MCP servers directly from chat:
28+
29+ | Command | Description |
30+ | ---------------------------- | ----------------------------------- |
31+ | ` /mcp add <name> <command> ` | Add a new MCP server |
32+ | ` /mcp remove <name> ` | Remove an MCP server |
33+ | ` /mcp edit <name> <command> ` | Update an existing server's command |
34+
35+ Examples:
36+
37+ ```
38+ /mcp add memory npx -y @modelcontextprotocol/server-memory
39+ /mcp add chrome npx -y chrome-devtools-mcp@latest --headless
40+ /mcp remove github
41+ /mcp edit chrome npx -y chrome-devtools-mcp@latest --headless --isolated
42+ ```
43+
2544## Settings UI
2645
2746Configure servers in ** Settings → Projects** :
2847
29481 . Select a project from the dropdown
30492 . Add servers with name and command
31- 3 . Use ** Test** to verify before adding
32- 4 . View available tools after successful test
50+ 3 . Use ** Test** (play button) to verify before adding
51+ 4 . Use ** Edit ** (pencil) or ** Remove ** (trash) to manage existing servers
3352
3453## Behavior
3554
0 commit comments