Skip to content

Commit 331a6c0

Browse files
cliffhallclaude
andcommitted
docs(filesystem): qualify the two-server read-only workaround for Roots clients
Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: cliffhall <[email protected]>
1 parent ea2997b commit 331a6c0

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎src/filesystem/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ The server then registers only the tools annotated `readOnlyHint: true` (see [To
3636

3737
The flag may appear anywhere among the arguments. `--` ends the options, so a directory literally named `--read-only` can be given after it.
3838

39-
Read-only mode covers every allowed directory. To make only some of them read-only, run two servers: one with `--read-only` for the directories to protect, and one without it for the rest. With Docker, a bind mount's `ro` flag also makes a single directory read-only at the operating-system level.
39+
Read-only mode covers every allowed directory. To make only some of them read-only, run two servers: one with `--read-only` for the directories to protect, and one without it for the rest. That separation holds only while the writable server keeps its command-line directories: a 2025-era client that supports Roots replaces them (see Method 2), so it could expose a protected directory to the writable server. Where that matters, make the protected directories read-only at the operating-system level as well, with file permissions or, with Docker, a bind mount's `ro` flag.
4040

4141
### Method 2: MCP Roots (Deprecated, 2025-era clients only)
4242
A client that connects with a 2025-era protocol version (the `initialize` handshake) and supports [Roots](https://modelcontextprotocol.io/docs/learn/client-concepts#roots) can dynamically update the Allowed directories.

0 commit comments

Comments
 (0)