Skip to content

Commit ea51900

Browse files
committed
docs: clarify MCP server scope (config vs runtime)
1 parent eeb3e7d commit ea51900

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

docs/mcp-servers.mdx

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,11 +50,20 @@ Configure servers in **Settings → Projects**:
5050
3. Use **Test** (play button) to verify before adding
5151
4. Use **Edit** (pencil) or **Remove** (trash) to manage existing servers
5252

53+
## Scope
54+
55+
MCP servers have two scopes:
56+
57+
- **Configuration** is per-project — The `.mux/mcp.jsonc` file lives in your project root and applies to all workspaces created from that project
58+
- **Runtime instances** are per-workspace — Each workspace runs its own server processes, so state in one workspace doesn't affect another
59+
60+
This means you configure servers once per project, but each workspace (branch) gets isolated server instances with independent state.
61+
5362
## Behavior
5463

5564
- **Hot reload** — Config changes apply on your next message (no restart needed)
56-
- **Per-workspace** — Each workspace maintains its own server instances
5765
- **Isolated** — Server processes run in the workspace directory with its environment
66+
- **Automatic lifecycle** — Servers start when first needed and stop when the workspace closes
5867

5968
## Finding MCP Servers
6069

0 commit comments

Comments
 (0)