Proton Drive MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROTON_DRIVE_PATH | No | Custom path to your Proton Drive location if not in the standard location |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_mountB | Check if Proton Drive is mounted and accessible |
| list_filesC | List files and folders in Proton Drive |
| read_fileC | Read a text file from Proton Drive |
| write_fileC | Write or create a file in Proton Drive |
| delete_fileB | Delete a file or folder from Proton Drive |
| create_folderB | Create a new folder in Proton Drive |
| get_file_infoC | Get information about a file or folder |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no ambiguity: check_mount verifies accessibility, create_folder creates folders, delete_file deletes items, get_file_info retrieves metadata, list_files lists contents, read_file reads text files, and write_file writes files. The actions (check, create, delete, get, list, read, write) and targets (mount, folder, file) are well-defined and non-overlapping.
All tools follow a consistent verb_noun pattern using snake_case, such as check_mount, create_folder, delete_file, get_file_info, list_files, read_file, and write_file. The naming is predictable and readable throughout the set, with no deviations in style or convention.
With 7 tools, the count is well-scoped for a Proton Drive file management server, covering essential operations without bloat. Each tool earns its place by addressing core needs like mounting, CRUD operations, and file listing, making the set efficient and focused.
The tool set provides strong coverage for basic file operations, including create, read, update (via write_file), delete, and list, along with mount checking and metadata retrieval. A minor gap exists in update operations for folders (e.g., rename or move), but agents can work around this using delete and create, and core workflows are well-supported.