Self-hosted S3-compatible object storage server with an MCP interface for AI agents.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Lightweight object storage that speaks S3 (boto3/AWS SDK compatible), plain HTTP, and MCP. SQLite for metadata, flat files on disk.
Most self-hosted S3-compatible storage is designed for large-scale deployments. Distributed erasure coding, IAM policies, WORM compliance, full web consoles — useful if you're running a cloud, overkill if you just want a place to put files that various services and AI agents can read and write.
AWS Sig V4 breaks behind reverse proxy path prefixes. Most implementations verify signatures using the full original upstream path. Put them behind nginx at /storage/, nginx strips the prefix, the server sees /bucket/key instead of /storage/bucket/key, the signature check fails. HybridS3 has a path_prefix config option — set it to /storage and all routes move under that prefix. No path stripping, no special proxy headers. boto3's signed path matches what the server sees.
Three interfaces, one service. boto3 works out of the box. Plain HTTP with curl works. AI agents connect via MCP and get structured tool definitions. No separate services for different clients.
Buckets are configuration, not state. There is no API to create or delete buckets. They live in the YAML config file. You always know exactly what exists, it's version-controlled, and there are no surprise buckets accumulating garbage.
TTL expiry is built in. Set ttl: 24h on a bucket and objects expire automatically after their last write. No lifecycle policies, no cron jobs, no separate process.
Readable and modifiable. Small enough to understand in an afternoon.
The container expects:
/config/config.yaml/data8080Runs as UID 1000.
docker run:
docker-compose:
Each bucket has two keys defined in config:
| Config field | Role | Keep secret? |
|---|---|---|
key | The private key. Used to authenticate Bearer requests and to sign S3 signatures. Never transmitted — only used locally to compute or verify HMACs. | Yes |
public_key | The public identifier. Used as aws_access_key_id in S3 auth and appears in presigned URL Credential= fields. Grants nothing on its own. | No — safe to share |
The split is what makes presigned URLs work safely. A presigned URL must embed an identifier in the Credential= field so the server knows which key to verify against — that identifier is the public_key. Since it is non-secret, having it in the URL is fine. The private key signs the URL on the server and never appears in it.
The master_key is a cross-bucket credential that works on every bucket for every operation, without needing individual bucket keys. Two situations call for it:
list_bucketsThe master_public_key is the non-secret identifier that pairs with master_key in S3 auth (used as aws_access_key_id).
Do not embed the master key in client-facing code. Use per-bucket keys for that — they limit access to exactly one bucket.
| Setting | GET / HEAD / LIST | PUT | DELETE / presign |
|---|---|---|---|
public: true | no authentication required | bucket key, master key, or valid presigned PUT | bucket key or master key |
public: false | bucket key, master key, or valid presigned GET | bucket key, master key, or valid presigned PUT | bucket key or master key |
HTTP requests authenticate using a Bearer token in the Authorization header. Pass the bucket's private key, or the master key for cross-bucket operations.
GET /) — master key lists all buckets; bucket key lists only its own bucket.POST /presign/...) — requires the bucket key or master key.No reviews yet — be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/hybrids3)<a href="https://allmcps.com/mcp/hybrids3"><img src="https://allmcps.com/api/badge/hybrids3?style=directory" alt="HybridS3 on AllMCPs" /></a>