Repository navigation
ServerFS v0.16.0
Overview
ServerFS v0.16.0 adds standards-compliant, opt-in OAuth 2.1 authentication for remote MCP access while preserving the existing filesystem authorization model and native Windows/macOS stdio behavior.
OAuth remains disabled by default. Existing v0.15-style deployments continue to work unchanged until the OAuth overlay and settings are explicitly enabled.
Highlights
- OAuth 2.1 Resource Server protection for Linux Streamable HTTP, including RFC 9728 discovery/challenge behavior and strict resource validation.
- Isolated
serverfs-authauthorization broker with opaque, resource-bound ServerFS access/refresh tokens, rotation, revocation, and private introspection. - Identity federation adapters for GitHub, DingTalk, Feishu/Lark, and WeChat Open Platform.
- Exact provider-qualified admission principals; OAuth identity admission remains separate from the existing per-workdir authorization model.
- Pre-registered clients, standards-current Client ID Metadata Documents (CIMD), and optional DCR compatibility mode.
- Dedicated
compose.oauth.ymlisolation: upstream provider credentials and Internet egress stay out of the MCP core. - English and Chinese OAuth operator documentation covering provider callbacks, proxy behavior, backup/restore, revocation, credential rotation, and troubleshooting.
- Cross-platform portability hardening and expanded Windows collection/CI coverage; OAuth does not change native Windows/macOS stdio defaults.
Compatibility and known limitations
- Real GitHub, Feishu/Lark, DingTalk, and WeChat browser login requires operator-created provider applications and credentials. These external prerequisites are documented and are not bundled with ServerFS.
- OAuth over the OpenAI Secure MCP Tunnel remains subject to upstream
tunnel-clientissue #78, which can rewrite the canonical OAuth resource. ServerFS does not weaken resource/audience validation, accept wildcard audiences, or hard-code undocumented OpenAI gateway hosts as a workaround. - The OAuth-disabled OpenAI Tunnel path remains supported and regression-tested; direct/generic OAuth is covered by production-boundary end-to-end tests.
Validation
1565 passed, 316 skippedin the final root test suite.157 passedin the focused OAuth/security matrix.- Final clean-host Container, Windows Native, Windows Agent, macOS Native, and Pages CI all passed on release commit
6fc7df2d2a90474159ec899278fe9ebfdd53390b. - Base, generic HTTP, OAuth, OAuth+Agent, and OAuth+file-ingress Compose shapes validated.
- Windows release wheels passed tag-version/METADATA checks and clean-install acceptance.
- Linux
0.16.0,0.16, andlatestmulti-architecture images passed manifest verification forlinux/amd64andlinux/arm64.
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.16.0-py3-none-any.whl | ServerFS env | 6effa976a99bc1844216b1472707c5608a9ef8b984c350c24b26fcd096db3fe6 |
| serverfs_windows_native-0.16.0-cp312-abi3-win_amd64.whl | ServerFS env | 4f6315bb9e0bfa1201e88b2c35faaab9c99d49586e26c59361d0e71dd0a3a035 |
| serverfs_agent_bridge-0.16.0-py3-none-any.whl | Agent Bridge env | 7a9d2c8e9cb6ebeff0f4b32e9b5bcdc960f4c28281ddc0a4270e3af1ad375045 |
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.16.0/serverfs_mcp-0.16.0-py3-none-any.whl https://github.com/NTLx/ServerFS_MCP/releases/download/v0.16.0/serverfs_windows_native-0.16.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.16.0/serverfs_agent_bridge-0.16.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.16.0/serverfs_windows_native-0.16.0-cp312-abi3-win_amd64.whl" --sha256 4f6315bb9e0bfa1201e88b2c35faaab9c99d49586e26c59361d0e71dd0a3a035