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.733 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.41 npmMIT
- AlicenseAqualityDmaintenanceMCP server that gives Claude Desktop and other desktop MCP clients filesystem powers—read, write, edit, and manage files like AI coding assistants.1746 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
- AlicenseAqualityAmaintenanceAn 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.39AGPL 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.01MIT
- 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 38 tools
Several tool pairs overlap in purpose: drive_upload vs drive_write_file, drive_download vs drive_read_file, drive_rename vs drive_move, and the three share-removal tools. The descriptions do add clear boundary notes, but the sheer number of similar operations makes misselection likely.
The drive_ and photos_ prefixes with verb_noun naming are mostly consistent, e.g. drive_list_trash, drive_share_invite, photos_create_album. Minor deviations like drive_list, drive_info, and drive_invitation_accept vs drive_list_invitations break the pattern slightly.
38 tools is well above the 25+ threshold and feels heavy even for a combined Drive and Photos server. Several tools could be consolidated, such as drive_rename/drive_move, drive_upload/drive_write_file, and the share-removal variants.
The tool set covers the full Drive file lifecycle, trash workflow, sharing, invitations, auth, and Photos albums, so core workflows have no dead ends. Minor gaps remain: no direct remote text-file creation without the sync path, no role-editing operation, and no photo deletion from the timeline.