Your archive,
from the command line.
One token, four ways in: MCP for AI assistants, a CLI with no dependency, a REST API, and an S3 endpoint that works with aws-cli and rclone. The scope stays limited to the folder you choose.
- access.waysCLI · REST · S3 · MCP
- access.tokenscoped revocable
- access.signatureV4
- access.dataFrance 100%
The one line client
Self-hosted, with no npm and no dependency. The token is read from an environment variable.
Install in one command
From any script
An authenticated POST, with the token in a header. Multipart or raw body.
The S3 tools you already use
Signature V4: aws-cli, rclone, s3cmd and the SDKs work as they are. Each folder is a bucket.
You set the scope
Limited to one folder
The token only sees the folder you open to it. The rest of the archive stays invisible.
Fine grained permissions
Search, read, upload: switch on only what the tool actually needs.
Revocable, logged
Every call is traced; a token is revoked in one click.
What developers ask us
And on a Mac, without living in the terminal?
The same client backs a quick action in the Finder: right click a document and it goes into the folder of your choice, with no browser. The install is done once.
Which token for which access?
The same token, created in your account, serves MCP, the CLI and the REST API (Bearer header). For S3 it also provides an access key and secret key pair (signature V4).
What file sizes?
On the free account, up to 100 MB per file, whichever way you use. On a paid tier, up to 8 GB per file, and a multi-part S3 upload, which rclone starts by itself for large files.
Does it work with rclone?
Yes: set up an S3 remote (provider Other), endpoint s3.pdf-archive.com, access key and secret from your token, in path style.
Where are my files?
Hosted in France, under the GDPR. Nothing is transferred outside the European Union.