proton-drive-cli-mcp

Proton Drive CLI MCP

Manage Proton Drive from Claude, Codex, VS Code/Copilot, and any MCP client through Proton's official CLI.

Authentication and encrypted Drive behavior stay with Proton's tooling.

|

|

|

|

|

Why This Exists

AI agents can already run shell commands, but Drive operations should not depend

on prompt-crafted command lines. This server exposes Proton Drive as typed MCP

tools while delegating the sensitive parts to Proton's official `proton-drive`

CLI.

> [!NOTE]

> This project is an independent interoperability wrapper. It is not affiliated

> with Proton AG.

Install

Add the server to an MCP client as a local stdio server:

{
  "mcpServers": {
    "proton-drive": {
      "command": "npx",
      "args": ["-y", "@borealstack/proton-drive-cli-mcp"],
      "env": {}
    }
  }
}

The command is a stdio server. If you run it directly in a terminal, no prompt

or banner is expected; it waits for MCP JSON-RPC messages on stdin.

Client Shortcuts

First Run

Start with diagnosis. The server will report whether the official CLI is found,

whether the managed install path exists, which version is available, and whether

the CLI can access `/my-files`.

Call proton_drive_diagnose

If the CLI is missing, run setup:

Call proton_drive_setup with installIfMissing=true

If authentication is missing, start the browser login flow:

Call proton_drive_auth_login
Finish Proton sign-in in the browser
Call proton_drive_diagnose again

> [!TIP]

> The server does not request or store Proton credentials. Login, session

> storage, and encrypted Drive behavior remain delegated to Proton's official

> CLI.

Requirements

• Node.js 22+ for the published package.
• Bun 1.3+ for repository development and Bun test coverage.
• The official Proton Drive CLI, or network access to Proton's CLI download

index for managed install.

• Browser access for the official Proton login flow.

The CLI is resolved in this order:

1. `PROTON_DRIVE_CLI_PATH`

2. The managed user-local install path

3. `proton-drive` or `proton-drive.exe` in the current directory or common download paths

4. `proton-drive` on `PATH`

5. Managed install from Proton's CLI download index

Useful environment switches:

What Agents Can Do

Full schemas and examples are in docs/TOOLS.md.

Common Agent Workflows

List the top 20 items in /my-files/Reports.

Uses `proton_drive_list` with bounded output and pagination metadata.

Upload these local files to /my-files/Reports, then poll until done.

Uses `proton_drive_upload_async` followed by `proton_drive_job_status`.

Read /my-files/Notes/todo.txt, update the text, and write it back.

Uses `proton_drive_read_text` and `proton_drive_write_text` for small UTF-8

files. Full binary or large-file work should use `proton_drive_download` and

`proton_drive_upload`.

Safety Model

This project is designed so the MCP layer can orchestrate Drive work without

becoming a credential broker.

> [!IMPORTANT]

> `proton_drive_delete` and `proton_drive_empty_trash` are permanent operations.

> Prefer `proton_drive_trash` first unless the user explicitly asks to delete.

Release Channels

Release assets include:

• npm package tarball
• MCPB bundle
• `SHA256SUMS`
• Sigstore JSON attestation bundle

Develop Locally

bun install
bun run typecheck
bun test
bun run build
npm test

Run the development server through Bun:

{
  "mcpServers": {
    "proton-drive-dev": {
      "command": "bun",
      "args": ["run", "/src/index.ts"],
      "env": {}
    }
  }
}

Run real-account smoke checks only when you intentionally want to touch a

logged-in Proton Drive account. Keep generated smoke artifacts local and out of

git.

Project Map

References

• Proton: Using Proton Drive CLI
• Proton blog: Introducing Proton Drive CLI
• Official Proton Drive CLI README
• Model Context Protocol TypeScript SDK

Help Discovery

If this project helps you connect Proton Drive to an MCP client, star the

repository so other users can find the maintained official-CLI wrapper:

borealstack/proton-drive-cli-mcp.