Bitatlas

io.github.bitatlas-groupPublished by GitHub account bitatlas-groupv1.1.0Updated Oct 24, 2026

Zero-knowledge encrypted storage for humans and AI agents. Client-side AES-256-GCM, EU-hosted.

VerifiedSTDIODesktop onlyFiles & StorageSecurity & Monitoring

Overview

AI-generated overview

An MCP server that gives an assistant an encrypted BitAtlas cloud vault for storing, searching, retrieving and sharing files, with client-side encryption.

What you can do
Check vault status, file count and storage usage, and list or search file metadata by folder, category or name. Download and decrypt file contents locally, or encrypt a local file and upload it. Create folders and delete files. Create public share links, list existing shares with expiry and download counts, and revoke them.
When to use it
Use it when an assistant needs persistent, encrypted file storage across sessions, or when it should hand a generated artifact to a person through a link without exposing plaintext to the storage provider.
Requirements
Local Node.js process run via npx. Needs a BitAtlas API key (BITATLAS_API_KEY) or, alternatively, an EVM wallet private key (BITATLAS_WALLET_PRIVATE_KEY) for per-request USDC payments. A 64-character hex master key (BITATLAS_MASTER_KEY) is required for upload and download. Network access to the BitAtlas API.
Before you install
Requires a master key (BITATLAS_MASTER_KEY) that decrypts all vault contents; anyone holding it can read the files. The optional wallet mode uses a private key (BITATLAS_WALLET_PRIVATE_KEY) and spends USDC per request. Upload, delete, folder and share tools change data; share links are readable by anyone who has them until revoked.

Installation

In SourceWeft

  1. Open Bitatlas in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

BitAtlas MCP Server 🤖

Zero-Knowledge Cloud Drive persistence for AI agents.

This Model Context Protocol (MCP) server allows AI agents to securely interact with the BitAtlas vault. All files are encrypted client-side, meaning the server never sees the plaintext data.

Features

  • Search & List Vault: Agents can browse encrypted file metadata.
  • Secure Retrieval: Agents can fetch encrypted blobs and decryption metadata.
  • Zero-Knowledge: The agent performs decryption locally using the user's provided master key.
  • Hand a file to a human: bitatlas_share_file mints a public link the host cannot read — the decryption key rides in the URL fragment, never reaching BitAtlas. The canonical "agent produces an artifact → human opens a link" handoff, without giving up zero knowledge.

Tools

ToolPurpose
bitatlas_vault_statusVault health, file count, storage usage
bitatlas_list_filesList file metadata (filter by folder/category/search)
bitatlas_searchSearch files by name
bitatlas_get_fileDownload + decrypt a file's content
bitatlas_upload_fileEncrypt a local file client-side and upload it
bitatlas_delete_fileDelete a file
bitatlas_create_folderCreate a folder
bitatlas_share_fileCreate a public, zero-knowledge share link (/s/<id>#k=…) to hand a file to a human. ⚠️ Anyone with the link can read the file.
bitatlas_list_sharesList your share links with expiry, download count, and status
bitatlas_revoke_shareRevoke a share link (stops future downloads)

Installation

For AI Agents (Claude Desktop, OpenClaw, etc.)

Add this to your MCP settings:

json
{  "mcpServers": {    "bitatlas": {      "command": "npx",      "args": ["-y", "@bitatlas/mcp-server"],      "env": {        "BITATLAS_API_KEY": "your-api-key",        "BITATLAS_MASTER_KEY": "your-derived-master-key"      }    }  }}

x402 Wallet Mode (No Account Required)

Instead of an API key, agents can pay per request using a crypto wallet with USDC on Base:

json
{  "mcpServers": {    "bitatlas": {      "command": "npx",      "args": ["-y", "@bitatlas/mcp-server"],      "env": {        "BITATLAS_WALLET_PRIVATE_KEY": "0xabc...",        "BITATLAS_MASTER_KEY": "your-64-hex-char-master-key"      }    }  }}

No signup. No API key. The agent pays per request in USDC and gets full vault access. Files include 30 days of storage and can be renewed.

Priority: If both BITATLAS_API_KEY and BITATLAS_WALLET_PRIVATE_KEY are set, the API key is preferred (free within quota).

Environment Variables

VariableRequiredDescription
BITATLAS_API_KEYOne of API key or walletPersonal access token from bitatlas.com
BITATLAS_WALLET_PRIVATE_KEYOne of API key or walletEVM private key for x402 payments
BITATLAS_MASTER_KEYFor encrypt/decrypt64-char hex string (256-bit master key)
BITATLAS_API_URLNoDefaults to https://api.bitatlas.com
BITATLAS_WEB_URLNoWeb origin used to build share links. Defaults to https://www.bitatlas.com

Development

bash
npm installnpm run start

License

MIT

Source: mcp-server/README.md at commit bc46360

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts