Log inSubmit server
Proton Drive CLI MCP logo

Proton Drive CLI MCP

Connects AI agents to Proton Drive through typed MCP tools backed by Proton’s official CLI.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Proton Drive CLI MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "proton-drive-cli-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@borealstack/proton-drive-cli-mcp"
      ],
      "env": {
        "PROTON_DRIVE_CLI_PATH": "YOUR_VALUE_HERE",
        "PROTON_DRIVE_CLI_AUTO_INSTALL": "YOUR_VALUE_HERE",
        "PROTON_DRIVE_CLI_INSTALL_DIR": "YOUR_VALUE_HERE",
        "PROTON_DRIVE_CLI_MANAGE_PATH": "YOUR_VALUE_HERE",
        "PROTON_DRIVE_AUTH_STATUS_CACHE_MS": "YOUR_VALUE_HERE",
        "PROTON_DRIVE_VERSION_CACHE_MS": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

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

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 4d ago.

Overview

Proton Drive CLI MCP MCP server exposes Proton Drive operations as typed tools for MCP clients, using Proton’s official CLI for authentication and encrypted Drive behavior. It supports file listing, transfers, text-file edits, sharing, invitations, setup, authentication, and background jobs. Run it as a local stdio server through npx, with Node.js 22+ and browser access for Proton login. Reach for it when an agent needs structured Proton Drive access without handling Proton credentials directly.

Use cases

  • List files in a Proton Drive folder
  • Upload local files and monitor transfer jobs
  • Read and update small UTF-8 text files
  • Manage shared links and invitations
  • Move files to trash or restore them

Key features

  • Typed Proton Drive file and folder tools
  • Official Proton CLI authentication delegation
  • Synchronous and asynchronous transfers
  • Sharing and invitation management
  • Managed CLI installation with checksum verification
  • Confirmation gates for destructive actions

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

9/9 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · @borealstack/proton-drive-cli-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads608Package downloads in the last 30 days.
Last commit4mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Proton Drive CLI MCP works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Proton Drive CLI MCP

Proton Drive CLI MCP is an MCP server that connects AI clients to Proton Drive through Proton’s official CLI. Its main tools cover diagnosis, authentication, file listing, uploads, downloads, text-file edits, sharing, invitations, mutations, and background job tracking. It runs locally over MCP stdio and does not store Proton credentials.

Install it through an MCP client with `npx -y @borealstack/proton-drive-cli-mcp`. The published package requires Node.js 22 or newer. The server can manage installation of Proton’s official CLI when automatic installation is enabled, or you can provide an existing CLI path.

Start the browser login flow with `proton_drive_auth_login`, complete Proton sign-in in the browser, and check the result with `proton_drive_diagnose`. Authentication and session storage remain inside Proton’s official CLI, and the MCP server does not request or store Proton credentials.

Yes, it provides setup paths for Claude Desktop, Codex, and VS Code, and runs as a local stdio MCP server. Claude Desktop can use the JSON configuration or MCPB bundle, Codex has plugin metadata, and VS Code can add the server with its MCP command.

Yes, asynchronous upload and download tools can start long-running work, while `proton_drive_job_status` reports progress. Small UTF-8 files can use the text helpers, but full binary or large-file operations should use the upload and download tools.

Related MCP servers

All in File Systems All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewProton Drive CLI MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/proton-drive-cli-mcp?style=directory)](https://allmcps.com/mcp/proton-drive-cli-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/proton-drive-cli-mcp"><img src="https://allmcps.com/api/badge/proton-drive-cli-mcp?style=directory" alt="Proton Drive CLI MCP on AllMCPs" /></a>