MCP server for Proton Drive via the official Proton Drive CLI.
If you already use Proton Drive CLI MCP, the proton drive cli mcp mcp server is the piece that lets your assistant work with it directly. MCP server for Proton Drive via the official Proton Drive CLI.
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.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
SHA256SUMS — Sigstore JSON attestation bundleClient — SetupCodex — Use the plugin metadata in plugins/proton-drive-cli-mcpVariable — EffectPROTON_DRIVE_CLI_PATH — Use an explicit Proton Drive CLI binaryPROTON_DRIVE_CLI_INSTALL_DIR — Override the managed install directoryPROTON_DRIVE_AUTH_STATUS_CACHE_MS — Tune successful auth-status cachingPROTON_DRIVE_VERSION_CACHE_MS — Tune CLI version cachingArea — ToolsFiles — proton_drive_list, proton_drive_info, proton_drive_create_folder, proton_drive_upload, proton_drive_downloadMutations — proton_drive_rename, proton_drive_copy, proton_drive_move, proton_drive_trash, proton_drive_restore, proton_drive_delete, proton_drive_empty_trashSharing — proton_drive_sharing_status, proton_drive_sharing_invite, proton_drive_sharing_remove, proton_drive_sharing_set_url, proton_drive_sharing_remove_urlConfiguration is passed through the environment: PROTON_DRIVE_CLI_PATH, PROTON_DRIVE_CLI_MANAGE_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
PROTON_DRIVE_CLI_PATH 2. The managed user-local install path 3. proton-drive or proton-drive.exeThe server ships on npm as @borealstack/proton-drive-cli-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the file and storage access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Proton Drive CLI MCP's toolset — SHA256SUMS, Client, Codex and 11 more — is a fair guide to whether it matches your workflow. It is maintained by borealstack; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Proton Drive CLI MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| SHA256SUMS | Sigstore JSON attestation bundle |
| Client | Setup |
| Codex | Use the plugin metadata in [plugins/proton-drive-cli-mcp](plugins/proton-drive-cli-mcp). |
| Variable | Effect |
| PROTON_DRIVE_CLI_PATH | Use an explicit Proton Drive CLI binary. |
| PROTON_DRIVE_CLI_INSTALL_DIR | Override the managed install directory. |
| PROTON_DRIVE_AUTH_STATUS_CACHE_MS | Tune successful auth-status caching. |
| PROTON_DRIVE_VERSION_CACHE_MS | Tune CLI version caching. |
| Area | Tools |
| Files | proton_drive_list, proton_drive_info, proton_drive_create_folder, proton_drive_upload, proton_drive_download |
| 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 |
| Guardrail | Behavior |
{
"mcpServers": {
"proton-drive": {
"command": "npx",
"args": ["-y", "@borealstack/proton-drive-cli-mcp"],
"env": {}
}
}
}Configuration as documented by the project. Restart the client after saving.
PROTON_DRIVE_CLI_PATH 2. The managed user-local install path 3. proton-drive or proton-drive.exe| Variable | Description | Required |
|---|---|---|
| PROTON_DRIVE_CLI_PATH | Filesystem location the server is allowed to use. | Optional |
| PROTON_DRIVE_CLI_MANAGE_PATH | Filesystem location the server is allowed to use. | Optional |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.