Skip to main content
Glama
@bitatlas/mcp-server

@bitatlas/mcp-server

BitAtlas

Zero Knowledge Cloud Drive for Humans and Agents

BitAtlas is a next-generation cloud storage platform designed with privacy and AI agents in mind. It provides a secure, zero-knowledge environment where your most sensitive documents are encrypted client-side and accessible only to you and the agents you authorize.

🚀 Vision

BitAtlas aims to be the secure "atlas" for your digital life, providing a foundation for both human productivity and AI agent assistance without compromising on privacy.

Related MCP server: Doc Manager

✨ Key Features

  • 🛡️ E2E Encryption (AES-256-GCM): All files are encrypted in the browser (or at the SDK level) before being uploaded. The server never sees your plaintext data or your encryption keys.

  • 🤖 Agent-Native (MCP Server): Built from the ground up to support AI agents via the Model Context Protocol (MCP). Let your agents safely search, read, and manage your vault.

  • 🔐 Personal Vault: A dedicated space for your most critical documents—identity papers, property deeds, medical records, and digital assets.

  • 🇪🇺 European Data Sovereignty: All infrastructure is hosted on European soil, subject to the world's strongest privacy regulations (GDPR).

  • 💸 Pay-per-Request (x402): Anonymous access via the x402 payment standard. Agents pay with USDC stablecoins on Base — no account, no API key, no KYC. Files include 30 days of storage with pay-to-renew. Learn more →

🏗️ Project Structure

  • mcp-server/: The Model Context Protocol server for integrating with AI agents like Claude Desktop, OpenClaw, and more.

  • sdk/encryption/: The core encryption logic used for client-side security.

🌐 Ecosystem

  • LegacyShield (legacyshield.eu): The first production application built on BitAtlas. A digital legacy platform and encrypted document vault for humans and their descendants.

🛠️ Getting Started

MCP Server

To use BitAtlas with your AI agent, configure the MCP server:

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

📜 License

MIT License. See LICENSE for details.


Built with ❤️ by BitAtlas Group

Available Tools

7 tools
bitatlas_create_folderC

Create a new folder in the vault.

Inputs: name (required), parent_id.

bitatlas_delete_fileC

Permanently delete a file from the vault.

Inputs: file_id (required).

bitatlas_get_fileA

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.

Inputs: file_id (required).

bitatlas_list_filesB

List files in the vault. Optionally filter by folder, category, or search term.

Inputs: folderId, category, search.

bitatlas_upload_fileA

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.

Inputs: file_path (required), name, category, folder_id.

bitatlas_vault_statusB

Get vault health status, file count, and storage usage.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity: create_folder, delete_file, get_file, list_files, search, upload_file, and vault_status all target specific, non-overlapping operations in the file vault domain. The descriptions reinforce these distinctions, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent 'bitatlas_verb_noun' pattern with snake_case throughout (e.g., bitatlas_create_folder, bitatlas_delete_file). This predictability makes the tool set easy to navigate and understand at a glance.

    Tool Count5/5

    With 7 tools, the count is well-scoped for a file vault management server. Each tool earns its place by covering essential operations like CRUD for files/folders, listing, searching, and status checks, without being overly sparse or bloated.

    Completeness5/5

    The tool set provides complete CRUD/lifecycle coverage for the vault domain: create (upload_file, create_folder), read (get_file, list_files, search), update (implied via re-upload), delete (delete_file), and administrative status (vault_status). There are no obvious gaps that would hinder agent workflows.

    Maintenance

    ActivityActive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Zero-knowledge document vault backed by Azure Blob Storage with built-in MCP server. Client-side AES-256-GCM encryption, five tools (list, get, search, create, update), and OAuth-gated access for Claude.
      9
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Sovereign E2E cloud storage for AI agents. MCP-native, zero-knowledge, RGPD-compliant, built in France.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Non-custodial memory MCP server with client-side encryption, enabling secure remember, recall, forget, and share operations with post-quantum security.
      9
      355 npm
      1
      Apache 2.0