BitAtlas
Zero-knowledge encrypted cloud storage for AI agents and the humans they work for.
What it can do
- Bitatlas Vault Status: Get vault health status, file count, and storage usage.
- Bitatlas List Files: List files in the vault. Optionally filter by folder, category, or search term.
- Bitatlas Search: Search vault files by a query string, optionally narrowed to a category.
What data it sees
Do you need an account
No: the server works without sign-in
Zero-knowledge encrypted cloud storage for AI agents and the humans they work for.
BitAtlas gives your agent a persistent, private vault. Every file is encrypted client-side with AES-256-GCM before it ever reaches the server — BitAtlas, and any host running this MCP server, can never read your data. EU-hosted, zero-knowledge by design.
What your agent can do
- Store & retrieve — upload, download, list, search, and organize encrypted files and folders ❯ [Image #7] and this
─────────────────────────────
- Generate an API key at bitatlas.com/vault/settings (starts with
ba_). - Provide your API key and your 256-bit master key (64 hex chars, derived from your password client-side — never sent to BitAtlas).
- Connect — your agent gets an encrypted vault it can read and write, while the data stays unreadable to everyone but you.
🔒 Client-side AES-256-GCM · 🇪🇺 EU-hosted · 🤝 Zero-knowledge share links
- Hand a file to a human — mint a zero-knowledge share link (
/s/#k=…) whose decryption key rides in the URL fragment and never touches the server - Manage shares — list and revoke share links
Tools (10)
bitatlas_vault_status · bitatlas_list_files · bitatlas_search · bitatlas_get_file · bitatlas_upload_file · bitatlas_delete_file · bitatlas_create_folder · bitatlas_share_file · bitatlas_list_shares · bitatlas_revoke_share
Setup
- Generate an API key at bitatlas.com/vault/settings (starts with
ba_). - Provide your API key and your 256-bit master key (64 hex chars, derived from your password client-side — never sent to BitAtlas).
- Connect — your agent gets an encrypted vault it can read and write, while the data stays unreadable to everyone but you.
🔒 Client-side AES-256-GCM · 🇪🇺 EU-hosted · 🤝 Zero-knowledge share links
Why this copy: it leads with the one-line value prop (SEO + scannability), names the differentiator (zero-knowledge, client-side encryption), lists the concrete tools agents will search for, and makes setup obvious.
Server tool list (10)
Raw names from tools/list. Only developers need these.
| bitatlas_vault_status | Get vault health status, file count, and storage usage. |
| bitatlas_list_files | List files in the vault. Optionally filter by folder, category, or search term. |
| bitatlas_search | Search vault files by a query string, optionally narrowed to a category. |
| bitatlas_get_file | Get file metadata and download + decrypt the file content. Returns decrypted content as UTF-8 text for text files, or base64 for binary files. Requires BITATLAS_MASTER_KEY. |
| bitatlas_upload_file | Read a local file, encrypt it client-side with AES-256-GCM, and upload it to the vault. Requires BITATLAS_MASTER_KEY. Files over 100 MB are not supported via MCP. |
| bitatlas_delete_file | Permanently delete a file from the vault. |
| bitatlas_create_folder | Create a new folder in the vault. |
| bitatlas_share_file | Generate a zero-knowledge share link for a vault file, to hand it to a human. The returned link is PUBLIC: ANYONE who has the link can open and read the file. The decryption key is in the URL fragment (#k=...) — BitAtlas never sees it and cannot read the file, but whoever you send the link to can. Confirm with the user before sharing anything sensitive. Requires BITATLAS_MASTER_KEY. |
| bitatlas_list_shares | List the share links you have created, with their expiry, download count, and status. |
| bitatlas_revoke_share | Revoke a share link so the server stops handing out the file. Note: anyone who already downloaded the file keeps it — revocation only stops future downloads. |