Skip to content

ServerFS MCP v0.6.0

Latest

Choose a tag to compare

@NTLx NTLx released this 22 Sep 16:51
· 2 commits to main since this release

ServerFS MCP v0.6.0 adds an optional TypeSafe Jev advisory suite to the host-side Agent Bridge while preserving ServerFS's deterministic authorization and provider-native approval boundaries.

Highlights

  • Adds Agent Task Preflight: structured Jev evaluation of task atomicity, mutation scope, stop conditions, verification evidence, and execution fit.
  • Adds Runtime Router advice across direct_serverfs_tool, codex, claude, and human_review without adding runtime=auto or changing the explicitly requested runtime.
  • Adds Approval Advisor for real provider approval requests, scoring necessity, bounded scope, destructive/irreversible risk, sensitive access, and external side effects while leaving the final approval decision explicit.
  • Minimizes Jev traffic: Preflight + Runtime Router share one task-submission request; Approval Advisor runs only when a provider creates an approval; identical approval payloads within one task reuse cached advice.
  • Jev remains opt-in, advisory-only, and fail-open. Empty SERVERFS_JEV_API_KEY means no TypeSafe client and no Jev requests. Jev cannot authorize workdirs, override runtime allowlists, bypass writer leases/provider safety checks, or auto-approve/deny.
  • Pins jev-1.13.0 with typesafe-sdk==0.7.1 for reproducible calibration. Both serverfs-mcp and serverfs-agent-bridge packages are version 0.6.0.
  • Updates the English/Chinese website and documentation with the Jev architecture, configuration, data-minimization rules, live validation, and request-economy model.

Upgrade

  • The MCP public tool schema is unchanged; no ChatGPT plugin refresh is required solely for v0.6.0.
  • Existing deployments remain Jev-free when SERVERFS_JEV_API_KEY is empty.
  • To enable Jev, configure the key in the existing untracked repository .env, update the user-scoped Agent Bridge with the normal installer flow, and restart the Bridge only after confirming no active writer-lease tasks.
  • Production container deployments should pin SERVERFS_IMAGE=ghcr.io/ntlx/serverfs_mcp:0.6.0. The main MCP container still has no Internet egress.

Validation

  • Root test suite: 803 passed
  • Agent Bridge: 102 passed
  • Ruff lint/format: pass for root and Agent Bridge
  • Site build: 19 pages
  • Compose Agent overlay render: pass
  • Edge Container workflow: success (35756109776), digest sha256:d447b37b5b1b80edf95a5fbac8e25ad2e580a7b541f4c81b134371621b5ab279
  • Stable tag Container workflow: success (35756224477), digest sha256:625d6f141930adde74cbd31ab816222bafd8653932ad0d9ce1842c37f03cec37
  • Both published image manifests passed linux/amd64 + linux/arm64 verification.