@borealstack/proton-drive-cli-mcp

Proton Drive CLI MCP

Manage Proton Drive from Claude, Codex, VS Code/Copilot, and other MCP clients through Proton's official proton-drive CLI without exposing Proton credentials. Authentication, encrypted Drive behavior, and session storage stay delegated to Proton's tooling instead of being reimplemented here.

Highlights

Area	What is ready
MCP clients	stdio server runnable with npx -y @borealstack/proton-drive-cli-mcp
Proton auth	Browser login through the official Proton Drive CLI
CLI install	Optional managed install from Proton's download index with SHA-512 verification
Distribution	npm package metadata, MCP Registry server.json, Codex plugin metadata, and Claude MCPB metadata
Safety	No Proton credentials in MCP config, no custom public-link passwords in command arguments, confirmation gates for destructive tools

Why This One

If you need	This project does	Why it matters
Proton's supported Drive behavior	Calls the official proton-drive CLI	Auth, encrypted Drive behavior, and session storage stay with Proton's tooling
MCP access from AI clients	Exposes typed tools for Claude, Codex, VS Code/Copilot, and other MCP hosts	Agents can call structured file, sharing, trash, and invitation workflows instead of shelling out blindly
No desktop sync-folder dependency	Works through the official CLI path and /my-files remote paths	The MCP server can manage cloud Drive paths without relying on a mounted local sync folder
Safer mutations	Requires confirm: true for permanent delete, empty trash, logout, sharing removal, and invitation accept/reject	High-impact actions stay explicit
Easy local install	Runs with npx -y @borealstack/proton-drive-cli-mcp and can managed-install the official CLI with SHA-512 verification	Users do not need to clone or build the repo to try it

Quick Start

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

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

This is a stdio MCP server, so running the command directly in a terminal is expected to show no prompt or banner. It waits for MCP JSON-RPC messages on stdin and writes responses on stdout.

To confirm package resolution from a shell, run the command outside this package checkout:

npx -y @borealstack/proton-drive-cli-mcp

When developing from this repository, use the built local entry point instead:

npm run build
node dist/index.js

Then call proton_drive_diagnose or proton_drive_setup. If the CLI is not authenticated, call proton_drive_auth_login, finish the browser sign-in, and check status again.

Install Paths

Client	Install option
Claude Code	claude mcp add --transport stdio proton-drive -- npx -y @borealstack/proton-drive-cli-mcp
Claude Desktop	Use the stdio JSON above, or install the .mcpb bundle after the first release: proton-drive-cli-mcp.mcpb
Codex	Plugin metadata is in plugins/proton-drive-cli-mcp
VS Code	code --add-mcp "{\"name\":\"proton-drive\",\"command\":\"npx\",\"args\":[\"-y\",\"@borealstack/proton-drive-cli-mcp\"]}"
npm	@borealstack/proton-drive-cli-mcp after publication

The MCPB and npm links become active after the first public release.

Requirements

• Node.js 22+ for the published package and built server.
• Bun 1.3+ for development and Bun test coverage.
• The official Proton Drive CLI installed, or network access to Proton's CLI download index.
• A Proton account login completed by the official CLI, or browser access for proton_drive_auth_login.

The server resolves the CLI in this order:

• PROTON_DRIVE_CLI_PATH
• The managed user-local install path
• proton-drive or proton-drive.exe in the current directory or common download paths
• proton-drive on PATH
• Auto-install from https://proton.me/download/drive/cli/index.html

The official CLI command name is proton-drive. Proton's downloaded binary can be run from its download directory as ./proton-drive on macOS/Linux or .\proton-drive.exe on Windows. The managed installer uses %LOCALAPPDATA%\Programs\proton-drive-cli\proton-drive.exe on Windows and ~/.local/bin/proton-drive on macOS/Linux. On Windows it adds the managed install directory to the user PATH when possible, so new terminals can run proton-drive version.

Set PROTON_DRIVE_CLI_AUTO_INSTALL=0 to disable managed install. Set PROTON_DRIVE_CLI_INSTALL_DIR to override the managed install directory. Set PROTON_DRIVE_CLI_MANAGE_PATH=0 to skip PATH management.

Tools

Core tools:

• Setup/Auth: proton_drive_diagnose, proton_drive_setup, proton_drive_auth_status, proton_drive_auth_login, proton_drive_auth_login_status, proton_drive_auth_login_cancel, proton_drive_auth_logout
• CLI: proton_drive_cli_install, proton_drive_cli_version, proton_drive_cli_help
• Files: proton_drive_list, proton_drive_list_async, proton_drive_info, proton_drive_create_folder, proton_drive_upload, proton_drive_upload_async, proton_drive_download, proton_drive_download_async, proton_drive_job_status, proton_drive_job_cancel, proton_drive_read_text, proton_drive_write_text
• Mutations: proton_drive_rename, proton_drive_copy, proton_drive_move, proton_drive_trash, proton_drive_restore, proton_drive_delete, proton_drive_empty_trash
• Sharing: proton_drive_sharing_status, proton_drive_sharing_invite, proton_drive_sharing_remove, proton_drive_sharing_set_url, proton_drive_sharing_remove_url
• Invitations: proton_drive_invitation_list, proton_drive_invitation_accept, proton_drive_invitation_reject

Permanent delete, empty trash, logout, sharing removal, and invitation accept/reject require confirm: true.

Full tool details are in docs/TOOLS.md.

Trust And Verification

• The npm publish workflow is prepared for GitHub OIDC trusted publishing and runs npm publish --provenance; npm package settings must authorize the workflow before a future manual release.
• Future GitHub releases build npm and MCPB assets, attach SHA-256 checksums, and publish Sigstore-backed artifact attestations for those assets.
• OpenSSF Scorecard runs from scorecard.yml and publishes SARIF results for public repository security signals.
• Dependabot and CodeQL are configured for dependency updates and SAST coverage, and GitHub Actions are pinned to commit SHAs with version comments.
• MCP Registry metadata in server.json includes publisher-provided categories, keywords, safety notes, and install details for downstream indexes.

Development

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

During local development, run the server directly with Bun:

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

Run bun run smoke:cli only when intentionally testing against a real logged-in Proton Drive account.

Safety And Legal

This is an independent project and is not affiliated with Proton AG. Proton and Proton Drive are Proton AG marks used only to identify interoperability with Proton Drive and the official Proton Drive CLI.

The server delegates sign-in and session storage to the official CLI, and it does not request or store Proton credentials. Custom public-link passwords are not accepted through MCP tool arguments because command-line arguments can be visible to local process inspection.

See LICENSE, NOTICE, DISCLAIMER.md, and SECURITY.md.

Support Discovery

If this helps you use Proton Drive from an MCP client, star the repository so other Proton users can find the maintained official-CLI wrapper: borealstack/proton-drive-cli-mcp.

References

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