Skip to main content
Glama
googlarz

Proton Drive MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

drive_upload

Upload local files or folders to Proton Drive with end-to-end encryption. Handles recursive folder uploads, preserves structure, and reports uploaded, skipped, and failed counts.

Instructions

Upload a local file or folder to Proton Drive with end-to-end encryption. Requires authentication. For folders, uploads recursively and preserves directory structure. Returns {uploaded, skipped, failed} counts — fails the call if failed > 0 (common causes: quota exceeded, destination path not found, permission denied). Conflict strategies are set separately for files and folders (CLI v0.8.0+) — both default to 'skip'. Do not use to move files already on Drive (use drive_move) or to write text content directly (use drive_write_file if PROTON_DRIVE_SYNC_PATH is set). Ensure destination folder exists first with drive_list; create it with drive_mkdir if needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localPathYesAbsolute local filesystem path of the file or folder to upload (must start with '/').
remotePathYesAbsolute remote Drive destination folder path (must start with '/'). E.g. /my-files/Reports
fileConflictStrategyNo'skip' leaves an existing remote file unchanged (default). 'create-new-revision' uploads as a new version of the existing file, keeping history. 'rename' adds a unique suffix to the uploaded file's name. 'replace' trashes the remote file and uploads the local copy in its place — confirm with user first.
folderConflictStrategyNo'skip' leaves an existing remote folder unchanged (default). 'merge' merges the uploaded folder's contents into the existing one. 'rename' adds a unique suffix to the uploaded folder's name. 'replace' trashes the remote folder and uploads the local copy in its place — confirm with user first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.32
    • removedInput schema / properties / conflictStrategy
      Removed value: -{
-  "description": "'skip' leaves existing remote files unchanged (default). 'replace' permanently overwrites the remote file — confirm with user first. 'keep-both' uploads with a unique name to avoid conflicts. 'merge' merges folder contents instead of failing (folders only).",
-  "enum": [
-    "skip",
-    "replace",
-    "keep-both",
-    "merge"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / fileConflictStrategy
      Added value: +{
+  "description": "'skip' leaves an existing remote file unchanged (default). 'create-new-revision' uploads as a new version of the existing file, keeping history. 'rename' adds a unique suffix to the uploaded file's name. 'replace' trashes the remote file and uploads the local copy in its place — confirm with user first.",
+  "enum": [
+    "skip",
+    "create-new-revision",
+    "rename",
+    "replace"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / folderConflictStrategy
      Added value: +{
+  "description": "'skip' leaves an existing remote folder unchanged (default). 'merge' merges the uploaded folder's contents into the existing one. 'rename' adds a unique suffix to the uploaded folder's name. 'replace' trashes the remote folder and uploads the local copy in its place — confirm with user first.",
+  "enum": [
+    "skip",
+    "merge",
+    "rename",
+    "replace"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changedv1.0.28
    • changedInput schema / properties / conflictStrategy / description
      Previous value: -"'skip' leaves existing remote files unchanged (default). 'overwrite' permanently replaces the remote file — confirm with user first. 'rename' uploads with a unique name to avoid conflicts."New value: +"'skip' leaves existing remote files unchanged (default). 'replace' permanently overwrites the remote file — confirm with user first. 'keep-both' uploads with a unique name to avoid conflicts. 'merge' merges folder contents instead of failing (folders only)."
    • changedInput schema / properties / conflictStrategy / enum
      Previous value: -[
-  "skip",
-  "overwrite",
-  "rename"
-]New value: +[
+  "skip",
+  "replace",
+  "keep-both",
+  "merge"
+]
  3. Changed3 schema fields changedv0.1.2
    • changedInput schema / properties / conflictStrategy / description
      Previous value: -"What to do if the file already exists. Default: skip."New value: +"'skip' leaves existing remote files unchanged (default). 'overwrite' permanently replaces the remote file — confirm with user first. 'rename' uploads with a unique name to avoid conflicts."
    • changedInput schema / properties / localPath / description
      Previous value: -"Absolute local path to upload."New value: +"Absolute local filesystem path of the file or folder to upload (must start with '/')."
    • changedInput schema / properties / remotePath / description
      Previous value: -"Remote Drive destination path. E.g. /my-files/Reports"New value: +"Absolute remote Drive destination folder path (must start with '/'). E.g. /my-files/Reports"
  4. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only include openWorldHint, so the description carries the full behavioral burden and succeeds. It discloses recursive folder upload, directory structure preservation, return counts, failure semantics (fails if failed > 0), common failure causes, default conflict strategies, and authentication requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence earns its place: core action, key behavior, return contract, failure modes, defaults, exclusions, and prerequisite steps. The description is dense but efficiently structured and front-loaded with the essential purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with no output schema, the description fully explains return values, error conditions, conflict handling, prerequisites, and alternatives. An agent has enough information to call it correctly and handle failures.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds value above the schema by explaining that conflict strategies are configured separately, defaults to 'skip', and the overall effect on upload results. It does not need to restate the schema's parameter details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Upload') and resource ('local file or folder to Proton Drive') and even specifies end-to-end encryption. It clearly distinguishes from sibling tools like drive_move and drive_write_file by naming exactly what this tool does and what it does not do.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance and names alternatives: 'Do not use to move files already on Drive (use drive_move)' and 'use drive_write_file'. It also gives a prerequisite workflow: check destination exists with drive_list, and create with drive_mkdir if needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools