Proton Drive MCP
Related Servers
Alternatives to Proton Drive MCP
- AlicenseAqualityDmaintenanceA Model Context Protocol server that enables AI assistants to interact with Proton Drive files, supporting operations like listing, reading, creating, and deleting files and folders.71,663 npm17MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceManage 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.53 npmMIT
- AlicenseAqualityAmaintenanceMCP server that gives Claude Desktop and other desktop MCP clients filesystem powers—read, write, edit, and manage files like AI coding assistants.17382 npm9MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the Proton privacy suite — Mail, Pass, Drive, Calendar, and VPN. 36 tools for Claude and other MCP-compatible AI agents.20MIT
- AlicenseBqualityAmaintenanceAn MCP server for managing Proton Mail, Pass, Drive, and Calendar through local IMAP/SMTP, pass-cli, and Proton Drive CLI, enabling AI agents to operate the mailbox, manage passwords, sync files, and classify emails.3946 npmAGPL 3.0
- AlicenseNot gradedqualityCmaintenanceMCP server for iCloud Drive on macOS, enabling Claude to browse, read, search, tag, write, and trash files with safe defaults and automatic handling of iCloud placeholder files.13 npm1MIT
- AlicenseBqualityCmaintenanceMCP server that gives Claude full read-write access to Google Drive, Docs, Sheets, and Slides using your own Google OAuth credentials and hosted server.25MIT
TDQS
Scored across 47 tools
Most tools are clearly differentiated by resource, scope, and permanence, and descriptions explicitly call out alternatives (e.g. drive_trash vs drive_delete, single vs bulk). A few overlaps remain, such as drive_rename being a narrow subset of drive_move and drive_read_file vs drive_read_content, but they are well documented.
The vast majority of tools use a consistent drive_* or photos_* prefix with snake_case verb_noun names (e.g. drive_list, photos_create_album). Minor deviations like drive_auth_status, drive_sharing_audit, and drive_version are state-oriented rather than verb_noun, and share vs sharing varies slightly.
47 tools is very heavy for an MCP server and far exceeds the typical well-scoped range. While the domain is broad (files, sharing, photos, trash, sync, analytics), many niche or bulk/audit tools could be consolidated or split into separate servers.
Coverage is strong: file/folder CRUD, trash/restore, sharing lifecycle, invitations, public links, photo albums/timeline, bulk operations, sync planning, and analytics are all present. Minor gaps include no direct sharing role update (worked around by revoke+invite) and no dedicated photo deletion/trash operation.