Bitatlas

What bitatlas-group/bitatlas does

bitatlas-group/bitatlas connects AI agents to a personal cloud vault through the Model Context Protocol. Its documented MCP interface contains seven tools for encrypted file-vault management, including uploading, downloading, searching, and organizing files. The repository describes the vault as suitable for sensitive material such as identity documents, property deeds, medical records, and other digital assets.

The project is designed around zero-knowledge storage. Files are encrypted before they are uploaded, and the server is not given plaintext content or encryption keys. This makes the server relevant for workflows where an agent needs controlled access to documents without placing unencrypted files in the storage service.

How it works

Encryption occurs in the browser or through the SDK encryption layer before a file reaches cloud storage. The stated encryption scheme is AES-256-GCM. Agents interact with the vault through the MCP server, while the user or authorized agent retains access to the encrypted data through the configured client-side setup.

The project also documents an x402 payment option for anonymous access. Under that model, agents can pay with USDC on Base without an account, API key, or KYC, and stored files include 30 days of storage with pay-to-renew. The supplied MCP configuration uses API credentials instead, so the applicable access method depends on how the service is being used.

Setup and configuration

The README provides an npm-based MCP configuration using the @bitatlas/mcp-server package:

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

Set BITATLAS_API_KEY and BITATLAS_MASTER_KEY in the MCP client configuration. The first identifies the API credential used by the example setup; the second supplies the derived master key used with the vault's encryption model. Keep both values outside source control and replace the example values with credentials from your BitAtlas setup.

The repository identifies Claude Desktop and OpenClaw as agent examples. Of the clients covered by this directory, Claude Desktop is explicitly named in the project material.

Tools and capabilities

The documented MCP surface contains seven tools for working with an encrypted file vault. The provided material supports these capability areas:

• Upload files to the vault.
• Download files from the vault.
• Search stored files.
• Read and manage vault content.
• Organize files within the vault.

Exact tool names, argument schemas, filtering options, and folder operations are not specified in the supplied README excerpt, so integrations should inspect the server's published tool definitions before building against them.

bitatlas-group/bitatlas is a fit for document assistants, private records workflows, and agent tasks that need file operations with client-side encryption. It is less suitable when an application requires plaintext server-side indexing or when the agent cannot securely provide the required key material.

Using this bitatlas-group/bitatlas MCP server

Always refer to the official documentation for the most accurate and up-to-date information on how to configure and run this server.