Skip to content

ServerFS v0.15.0

Choose a tag to compare

@github-actions github-actions released this 19 Oct 07:32

ServerFS v0.15.0

v0.15.0 makes ServerFS standards-first and vendor-neutral while preserving the existing security model and native-platform boundaries.

Highlights

  • Standard MCP connectivity: native stdio and Streamable HTTP are first-class interfaces; the Python MCP SDK is pinned to 2.3.0.
  • Real host interoperability: live acceptance passed with Claude Code 2.1.302, Codex 0.163.0, Qoder 1.1.65, and ChatGPT through the existing OpenAI Secure MCP Tunnel.
  • OpenAI Tunnel remains optional: existing ChatGPT Tunnel deployments remain supported, while generic MCP clients no longer depend on the Tunnel.
  • Safer generic Linux HTTP: compose.http.yml publishes loopback by default, with explicit Host/Origin allowlists; public exposure requires a separate TLS/authentication ingress boundary.
  • ChatGPT live regression: revision-guarded filesystem mutations, binary transfer, file parameter ingress, and Agent Bridge delegation all passed on the v0.15 runtime.
  • Native platform validation: Windows shared-core/native lifecycle gates passed; macOS gained a real stdio process E2E and its native/ServiceManagement gates passed.
  • Security invariants unchanged: explicit workdirs, read-only-by-default policy, revision guards, and separately gated binary/file-ingress/Agent capabilities remain intact.

Compatibility

  • Existing OpenAI Secure MCP Tunnel deployments remain supported.
  • Windows and macOS remain current-user scoped and non-elevated.
  • Existing filesystem, binary, and Agent tool contracts remain compatible.

Windows installation assets (Python >= 3.12; no Rust/MSVC/Docker required)

The three release wheels install into two isolated environments, matching the
frozen ServerFS/Agent-Bridge process boundary (the supervisor selects the Bridge
interpreter through SERVERFS_BRIDGE_PYTHON; the packages never share one dependency
graph):

file installs into sha256
serverfs_mcp-0.15.0-py3-none-any.whl ServerFS env 493beaa8a8f055945e57e80ec8da94bb8f0d682cc0259ca7ac1fdeb8f5a713db
serverfs_windows_native-0.15.0-cp312-abi3-win_amd64.whl ServerFS env 7ce5e456b61ec509c2ba4cea9cfc6bf1ac686f758624111b62224710188084cf
serverfs_agent_bridge-0.15.0-py3-none-any.whl Agent Bridge env 16871717e36578503aa1559cca6d667bf71d7321fe26f2e0a5349cb91bf6216c

ServerFS environment (product + native kernel):

uv venv --python 3.12 .venv-serverfs
uv pip install --python .venv-serverfs/Scripts/python.exe https://github.com/NTLx/ServerFS_MCP/releases/download/v0.15.0/serverfs_mcp-0.15.0-py3-none-any.whl https://github.com/NTLx/ServerFS_MCP/releases/download/v0.15.0/serverfs_windows_native-0.15.0-cp312-abi3-win_amd64.whl

Agent Bridge environment (Bridge + provider SDKs; it must NOT contain the product):

uv venv --python 3.12 .venv-bridge
uv pip install --python .venv-bridge/Scripts/python.exe https://github.com/NTLx/ServerFS_MCP/releases/download/v0.15.0/serverfs_agent_bridge-0.15.0-py3-none-any.whl

Point the ServerFS supervisor at the Bridge interpreter (set this in the environment
that starts serverfs supervisor; it is not a provider setting and does not belong in
[agent] config):

$env:SERVERFS_BRIDGE_PYTHON = "<path>\.venv-bridge\Scripts\python.exe"

Verified native-wheel storage alternative:

serverfs bootstrap native-wheel --url "https://github.com/NTLx/ServerFS_MCP/releases/download/v0.15.0/serverfs_windows_native-0.15.0-cp312-abi3-win_amd64.whl" --sha256 7ce5e456b61ec509c2ba4cea9cfc6bf1ac686f758624111b62224710188084cf