Skip to content

Architecture

Linux filesystem
Docker bind mounts
│ read-only by default
ServerFS MCP
│ internal network only
OpenAI Secure MCP Tunnel
│ outbound-only
ChatGPT

The MCP container has no published ports and no Internet egress. The OpenAI tunnel has a separate outbound network for control-plane traffic.

ChatGPT file parameter
│ temporary HTTPS URL
ServerFS MCP
│ dedicated internal network only
serverfs-file-ingress
│ policy-checked HTTPS/443 egress only
Temporary file host

The sidecar is opt-in. It has no workdir mounts, OpenAI/tunnel credentials, or published port. The main MCP container never receives Internet egress; it sends only the temporary URL and byte ceiling to the sidecar. Host authorization is either an exact administrator-configured hostname or the separately enabled constrained OpenAI Azure Blob account family measured from real ChatGPT file parameters. Generic wildcards are rejected. The sidecar then validates globally routable DNS answers, pins the connection to a validated IP while verifying TLS for the original hostname, revalidates every redirect, and enforces timeout and byte ceilings before returning raw bytes.

ServerFS MCP container
│ read-only Unix socket mount
Host Agent Bridge
├── Codex
└── Claude Code

The Bridge runs as a user-scoped host service and owns its runtime socket, locks, installed releases, configuration, and state outside the repository checkout.

Agent task / provider approval
Host Agent Bridge
│ minimized structured state
TypeSafe Jev API
│ probabilities / confidence / Noul
Advisory result only

Jev runs from the host Bridge, not the MCP container. Task Preflight and Runtime Router share one task-submission request; Approval Advisor runs only after a provider creates an approval request. These outputs never become authorization or runtime-selection authority.

ServerFS exposes narrow operations rather than a generic execution primitive:

  • filesystem read tools
  • guarded file mutations
  • bounded whole-file binary transfer
  • optional isolated ChatGPT file ingress
  • structured Agent task RPC
  • optional host-side Jev advisory decisions

Every optional capability is separately gated. Jev does not change the 11 / 13 / 19 / 21 MCP tool surfaces because it is an internal Agent Bridge advisor, not an MCP capability surface.