Repository navigation
ServerFS v0.17.1
ServerFS v0.17.1
Overview
v0.17.1 is a focused maintenance release that closes three Linux/Docker operational gaps without changing the MCP tool surface, workdir authorization model, OAuth/API-Key semantics, or native Windows/macOS lifecycle behavior.
Highlights
- Tunnel readiness and control-plane diagnostics (#15):
openai-tunnelhas an explicit Compose healthcheck using the pinned tunnel client's readiness command with successful control-plane-poll evidence. New diagnostics distinguish container liveness,/readyz, MCP state, control-plane polling, response delivery, and local queue/dispatcher evidence. - Read-only host observability (#16): new English/Chinese guidance documents
host collectors -> sanitized status directory -> read-only ServerFS workdir -> MCP client, including allowlisting, redaction, atomic writes, permissions, and periodic refresh without granting Agent Bridge or shell authority. - Restricted-network ARM64 deployment (#17): new English/Chinese guidance separates Docker daemon/registry pull proxying from ServerFS/OpenAI Tunnel runtime proxying and documents a safe offline
linux/arm64pull/inspect/save/transfer/load/verify flow with exact release pinning. - Documentation, examples, package metadata and the website are aligned on v0.17.1 as the current stable release.
Compatibility
- No MCP tool/schema changes.
- No workdir or mutation-authorization changes.
- OAuth 2.1 and static API Key behavior are unchanged.
- Native Windows and macOS lifecycle semantics are unchanged.
- Production Linux deployments should pin
ghcr.io/ntlx/serverfs_mcp:0.17.1.
Validation
- Release commit:
a54bcfae14e3202e2866624fbbcd08a6ad2dbb60. - Pi1 ARM64 root suite: 1587 passed / 316 skipped; focused Tunnel deployment tests: 20 passed.
- Agent Bridge suite: 364 passed / 12 skipped.
- Five relevant Compose deployment shapes and the 33-page English/Chinese production docs build passed locally.
- Windows native
cargo checkpassed with the Cargo-generated 0.17.1 lock entry. - Pre-tag exact-commit Container, Windows Native, Windows Agent, macOS Native and Pages workflows all passed.
- Pi1 could not reach Docker Hub for the local development image build, but the exact release commit's hosted Container workflow passed, providing the clean-network container gate.
- Tag-triggered Container and Windows wheel release workflows both passed; the stable multi-architecture image and all three Windows installation wheels were published successfully.
Resolved issues
- #15 — Tunnel readiness and control-plane diagnostics
- #16 — Read-only host observability recipe
- #17 — Restricted-network ARM64 deployment options
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.17.1-py3-none-any.whl | ServerFS env | b6eba03d8b0f890549cf36e5abedf0fb0a6b0395ae340f45c5096b0ce5e17676 |
| serverfs_windows_native-0.17.1-cp312-abi3-win_amd64.whl | ServerFS env | 21c80b7184408d157691cd67519e2b6a08a9b5b839497a64d18da9a43f14a367 |
| serverfs_agent_bridge-0.17.1-py3-none-any.whl | Agent Bridge env | f7d4ecbee91aaa69b637137d723b1584326cabbbe79a66d26e689009db465388 |
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.17.1/serverfs_mcp-0.17.1-py3-none-any.whl https://github.com/NTLx/ServerFS_MCP/releases/download/v0.17.1/serverfs_windows_native-0.17.1-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.17.1/serverfs_agent_bridge-0.17.1-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.17.1/serverfs_windows_native-0.17.1-cp312-abi3-win_amd64.whl" --sha256 21c80b7184408d157691cd67519e2b6a08a9b5b839497a64d18da9a43f14a367