@bitatlas/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITATLAS_API_KEY | No | Your BitAtlas API key | |
| BITATLAS_MASTER_KEY | No | Your derived BitAtlas master key used for client-side encryption | |
| BITATLAS_WALLET_PRIVATE_KEY | No | EVM wallet private key for x402 pay-per-request access (alternative to API key) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bitatlas_vault_statusB | Get vault health status, file count, and storage usage. |
| bitatlas_list_filesB | List files in the vault. Optionally filter by folder, category, or search term. |
| bitatlas_searchB | Search vault files by a query string, optionally narrowed to a category. |
| 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. |
| 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. |
| bitatlas_delete_fileC | Permanently delete a file from the vault. |
| bitatlas_create_folderC | Create a new folder in the vault. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
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.
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.
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.
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.