Server data from the Official MCP Registry
MCP server for Proton Drive via the official Proton Drive CLI.
MCP server for Proton Drive via the official Proton Drive CLI.
Valid MCP server (1 strong, 2 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.
8 files analyzed · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-borealstack-proton-drive-cli-mcp": {
"args": [
"-y",
"@borealstack/proton-drive-cli-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.

Local MCP server for Proton Drive. It wraps the official proton-drive CLI, so
authentication, encrypted Drive behavior, and session storage stay delegated to
Proton's tooling instead of being reimplemented here.
| 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 |
npx -y @borealstack/proton-drive-cli-mcp
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": {}
}
}
}
Then call proton_drive_auth_status. If the CLI is not authenticated, call
proton_drive_auth_login, finish the browser sign-in, and check status again.
| 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.
proton_drive_auth_login.The server resolves the CLI in this order:
PROTON_DRIVE_CLI_PATHproton-drive or proton-drive.exe in the current directory or common download pathsproton-drive on PATHhttps://proton.me/download/drive/cli/index.htmlSet PROTON_DRIVE_CLI_AUTO_INSTALL=0 to disable managed install. Set
PROTON_DRIVE_CLI_INSTALL_DIR to override the managed install directory.
Core tools:
proton_drive_auth_status, proton_drive_auth_login, proton_drive_auth_login_status, proton_drive_auth_login_cancel, proton_drive_auth_logoutproton_drive_cli_install, proton_drive_cli_version, proton_drive_cli_helpproton_drive_list, proton_drive_info, proton_drive_create_folder, proton_drive_upload, proton_drive_downloadproton_drive_rename, proton_drive_copy, proton_drive_move, proton_drive_trash, proton_drive_restore, proton_drive_delete, proton_drive_empty_trashproton_drive_sharing_status, proton_drive_sharing_invite, proton_drive_sharing_remove, proton_drive_sharing_set_url, proton_drive_sharing_remove_urlproton_drive_invitation_list, proton_drive_invitation_accept, proton_drive_invitation_rejectPermanent delete, empty trash, logout, sharing removal, and invitation
accept/reject require confirm: true.
Full tool details are in docs/TOOLS.md.
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.
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.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.