Anything that removes data or changes the account — trash, delete, empty trash, logout, removing a share — refuses to run unless the call carries `confirm: true`, which turns an ambiguous instruction into a second explicit step rather than a lost file. The other design choice worth knowing about is that folder listings and job output come back bounded, with counts and a truncated flag, so pointing an assistant at a large Drive does not dump the whole tree into context.
A stdio server that exposes Proton Drive as schema-checked tools instead of prompt-written command lines. Every operation runs through Proton's official `proton-drive` CLI, so authentication, session storage and the encrypted Drive behaviour are Proton's code, not a reimplementation. It is an independent wrapper, not a Proton product.
- `proton_drive_list`, `proton_drive_info` and `proton_drive_create_folder` browse and build the tree, with list output bounded and paged
- `proton_drive_upload` and `proton_drive_download` move files, with `proton_drive_upload_async` and `proton_drive_download_async` returning a job id instead of blocking
- `proton_drive_job_status` and `proton_drive_job_cancel` follow or stop a background job
- `proton_drive_read_text` and `proton_drive_write_text` read and write small UTF-8 files directly, rejecting binary or oversized content
- `proton_drive_rename`, `proton_drive_copy`, `proton_drive_move`, `proton_drive_trash`, `proton_drive_restore` and `proton_drive_delete` reorganise and remove
- `proton_drive_sharing_invite`, `proton_drive_sharing_status`, `proton_drive_sharing_set_url` and `proton_drive_sharing_remove` handle people and public links
- `proton_drive_diagnose` and `proton_drive_setup` report CLI discovery, version, PATH and auth state, and install what is missing
Node.js 22+ and the official Proton Drive CLI. Run it as `npx -y @borealstack/proton-drive-cli-mcp` (package `@borealstack/proton-drive-cli-mcp`, version 0.1.2) over stdio. If the CLI is missing the server downloads the current official build for your OS and CPU and verifies Proton's SHA-512 checksum before using it; set `PROTON_DRIVE_CLI_PATH` to point at your own copy, or `PROTON_DRIVE_CLI_AUTO_INSTALL=0` to switch that off. Sign-in happens in the browser through the CLI and the session lands in the OS secret store — this server never sees or stores Proton credentials.
One command — npx -y @borealstack/proton-drive-cli-mcp
