# Proton Drive CLI MCP [Health: Active]

**Category:** 📂 File Systems  
**Repository:** https://github.com/borealstack/proton-drive-cli-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 608  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/proton-drive-cli-mcp

## Description
MCP server for Proton Drive via the official Proton Drive CLI.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "proton-drive-cli-mcp": {
    "command": "npx",
    "args": ["-y","@borealstack/proton-drive-cli-mcp"],
    "env": {
      "PROTON_DRIVE_CLI_PATH": "",
      "PROTON_DRIVE_CLI_AUTO_INSTALL": "",
      "PROTON_DRIVE_CLI_INSTALL_DIR": "",
      "PROTON_DRIVE_CLI_MANAGE_PATH": "",
      "PROTON_DRIVE_AUTH_STATUS_CACHE_MS": "",
      "PROTON_DRIVE_VERSION_CACHE_MS": ""
    }
  }
}
```

**Requires environment variables:** `PROTON_DRIVE_CLI_PATH`, `PROTON_DRIVE_CLI_AUTO_INSTALL`, `PROTON_DRIVE_CLI_INSTALL_DIR`, `PROTON_DRIVE_CLI_MANAGE_PATH`, `PROTON_DRIVE_AUTH_STATUS_CACHE_MS`, `PROTON_DRIVE_VERSION_CACHE_MS` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Proton Drive CLI MCP does

The Proton Drive CLI MCP MCP server gives compatible AI clients structured access to Proton Drive. It wraps Proton’s official `proton-drive` command-line tool rather than implementing authentication or encrypted Drive APIs itself. This lets an agent inspect paths, manage files and folders, transfer content, handle sharing, and work with invitations through MCP tool schemas.

Available operations include listing and inspecting Drive items, creating folders, uploading and downloading files, renaming, copying, moving, trashing, restoring, and deleting content. Agents can also read and write small UTF-8 text files. Sharing tools cover status checks, invitations, public-link settings, and removal actions. Invitation tools can list, accept, or reject incoming invitations.

## How it works

The server communicates over MCP stdio. An MCP client starts the package, and the server exchanges JSON-RPC messages through standard input and output. The Proton CLI is resolved from `PROTON_DRIVE_CLI_PATH`, a managed user-local installation, common local paths, or the system `PATH`. If enabled and required, the server can install the official CLI from Proton’s download index with SHA-512 verification.

Authentication remains inside Proton’s CLI. The server does not request or store Proton credentials. On first use, call diagnosis to check CLI availability, version information, managed-install state, and access to `/my-files`. If needed, setup can install the CLI, and the browser-based Proton login flow can then be started through the authentication tools.

Long-running transfers and listings have asynchronous variants. A typical upload workflow starts `proton_drive_upload_async` and then checks progress with `proton_drive_job_status`. List responses and background output are bounded or summarized to limit response size; full binary files should use upload and download tools rather than text helpers.

## Setup and configuration

Install the Proton Drive CLI MCP MCP server through an MCP client using `npx -y @borealstack/proton-drive-cli-mcp`. The published package requires Node.js 22 or newer. The official Proton CLI is required, either already available or installable through the server’s managed-install path. Browser access is required for Proton’s official sign-in flow.

Configuration can select a CLI binary with `PROTON_DRIVE_CLI_PATH`. Set `PROTON_DRIVE_CLI_AUTO_INSTALL=0` to disable automatic installation, or use `PROTON_DRIVE_CLI_INSTALL_DIR` to change the managed installation directory. `PROTON_DRIVE_CLI_MANAGE_PATH=0` skips managed PATH updates. Authentication and version cache durations can be adjusted with `PROTON_DRIVE_AUTH_STATUS_CACHE_MS` and `PROTON_DRIVE_VERSION_CACHE_MS`.

## Tools and capabilities

The Proton Drive CLI MCP MCP server groups tools into several areas:

- Diagnosis, setup, CLI installation, version, and help
- Authentication status, browser login, login-status polling, cancellation, and logout
- Synchronous and asynchronous file operations
- Job status and cancellation
- Text-file read and write helpers
- File and folder mutations
- Sharing and invitation management

Destructive actions and account-changing operations require `confirm: true`. Permanent deletion and emptying the trash should be distinguished from moving an item to the trash. Custom public-link passwords are not accepted as MCP arguments because local process inspection could expose CLI arguments.

## Limitations and notes

The project is an independent wrapper and is not affiliated with Proton AG. It depends on the behavior and availability of Proton’s official CLI. The MCP server does not replace the CLI’s authentication system or encrypted Drive handling. Small text helpers are intended for small UTF-8 files; larger or binary content should use the file transfer tools. Direct terminal execution produces no interactive banner or prompt because the process waits for MCP JSON-RPC input.

_Full upstream README: https://allmcps.com/mcp/proton-drive-cli-mcp/readme_