Filesystem
safe read + guarded mutation surface
SECURE MCP FOR LINUX WORKDIRS
Expose only the Linux workdirs you choose. Read-only by default, with guarded writes, bounded binary transfer, isolated ChatGPT file ingress, and an optional native Agent Bridge.
v0.7.1/srv/projectsread-only by defaultuser-owned socketPROGRESSIVE CAPABILITY
ServerFS grows by explicit opt-in. Each added surface is bounded, independently gated, and visible in the tool contract.
safe read + guarded mutation surface
bounded whole-file transfer
structured Codex / Claude delegation
binary + Agent Bridge enabled
ARCHITECTURE
Every layer has one job. Optional powers are explicit, narrow, and independently gated.
SECURITY BY CONSTRUCTION
ServerFS does not rely on one sandbox or one network assumption. Filesystem policy, transport validation, container isolation, and Agent boundaries reinforce each other.
Narrow primitives. Explicit boundaries. No ambient authority.
Read-only by default
✓No shell or generic executor
✓Scoped workdir boundary
✓Revision-guarded mutation
✓No recursive delete
✓Transport Host / Origin validation
✓Internal-only MCP network
✓Agent Bridge is opt-in
✓OPTIONAL AGENT BRIDGE
ServerFS brokers structured tasks over a user-owned Unix socket. Codex and Claude keep their native environment; optional Jev advisors add task preflight, routing, and approval context without becoming an authority or changing the MCP tool surface.
Explore Agent Bridge Explore Jev Advisorsbridge.sock$ git clone https://github.com/NTLx/ServerFS_MCP.git
$ cd ServerFS_MCP
$ cp .env.example .env
$ docker compose pull
$ docker compose up -d
✓ serverfs-mcp healthy
✓ openai-tunnel connectedSELF-HOSTED
Start with the 11-tool filesystem surface. Add binary transfer, isolated ChatGPT file ingress, the Agent Bridge, or host-side Jev advisors only when the deployment actually needs them.
Read the deployment guideSERVERFS MCP