afs-server
The agentic-fs service: the concrete backends (stores, search, extraction), the
services, and the REST + MCP surface. Implements the afs-core contracts.
Status
Store layer (in progress):
afs_server.settings—AFS_*env config; every swappable layer is selected by a backend name and every AWS-shaped backend takes anendpoint_urloverride.afs_server.stores— the store registry:get_object_store(settings)selects a builtin or an installed plugin (afs.object_storesentry-point group).afs_server.stores.objects_s3.S3ObjectStore— the S3ObjectStore. Because it speaks plain S3, it is your store for any S3-compatible endpoint (MinIO, Cloudflare R2, Wasabi, Backblaze B2) viaAFS_S3_ENDPOINT_URL— no code change.afs_server.stores.catalog_dynamodb.DynamoDBCatalogStore— the DynamoDBCatalogStoreover the single-table schema (AFS_DYNAMODB_ENDPOINT_URLpoints at DynamoDB Local for dev).
Both stores are certified by the afs-core conformance kits via moto.
afs_server.services.FsService— the read path (list/stat/ rangedread) over the stores, with scope + namespace enforcement and 404-not-403 misses.afs_server.app— the FastAPI app:/v1/healthz,/readyz,/me, andfs/{ns}/{entries,stat,doc}; dev auth (static principal, never prod); everyAfsErrorrendered as RFC 9457problem+json.afs_server.mcp— the MCP surface mounted at/mcp(FastMCP):whoami,fs_list,fs_stat,fs_readover the sameFsService(in-process, no HTTP self-calls). The full middleware chain + remaining tools land with their slices.
The image (../../Dockerfile) runs this app on Lambda / Fargate / locally;
make dev from the repo root runs it against MinIO + DynamoDB Local. Coming
next: the MCP mount (shares FsService in-process).
Swapping a backend (plug-and-play)
See docs/swap-guides/. In short: S3-compatible
storage needs only an env var; anything else implements the ObjectStore
Protocol, registers an entry point, and certifies against
afs_core.testing.ObjectStoreConformance.
Develop
uv sync
uv run pytest packages/afs-server # conformance kits run against moto
Metadata
Release files for afs-server 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| afs_server-1.0.1.tar.gz | 153.4 kB | Without provenance | Details for afs_server-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| afs_server-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for afs_server-1.0.1-py3-none-any.whl |
Total release size: 237.4 kB
Release files / afs_server-1.0.1.tar.gz
| Download URL | afs_server-1.0.1.tar.gz |
|---|---|
| Size | 153.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3845655f889e14b70bd4275da6eb7a35cab0fdf668f733f2925b85c19f0c1ecb
|
|
BLAKE2b-256 checksum How to use checksums |
fce09a83b24e778f467b357b6d490307eb2fe3851cfa15bfc24dfbab2b6d0003
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / afs_server-1.0.1-py3-none-any.whl
| Download URL | afs_server-1.0.1-py3-none-any.whl |
|---|---|
| Size | 84.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
98f734c95061bf9a0557063e1335cc8eb7b7e97d58784e2a95c403b8f9d6eeba
|
|
BLAKE2b-256 checksum How to use checksums |
937e42ce117c497890425180babf412585b5c786a56116b2df0f54e435541ecc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for afs-server 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.