Proton Drive MCP

Overview Schema Source Related Servers Discussions Admin

Download from Drive

drive_download

Downloads a file or folder from Proton Drive to a local destination folder; creates missing paths, downloads folders recursively, and handles file or folder conflicts.

Instructions

Download a file or folder from Proton Drive to the local filesystem. localPath is a destination FOLDER, not the file's final path — created if missing; the item is placed inside it under its remote name (/my-files/report.pdf with localPath '/tmp/out' gives /tmp/out/report.pdf). Folders download recursively. File and folder conflict strategies are separate, both default to 'skip'. Returns {downloaded, skipped, failed} counts (not the local path) and fails the call if any file failed. Requires confirmed=true when fileConflictStrategy or folderConflictStrategy is 'remove' (it deletes the existing LOCAL file or folder).

Input Schema

TableJSON Schema

Name	Required	Description
`confirmed`	No	Must be true; only after the user approved this exact action.
`localPath`	Yes	Absolute local DESTINATION FOLDER, not the file's final path. Created if missing; the item is placed inside it under its remote name.
`remotePath`	Yes	Absolute remote path to download, e.g. /my-files/report.pdf.
`fileConflictStrategy`	No	'skip' keeps the existing local file (default). 'rename' downloads under a unique name. 'remove' deletes the local file first — confirm with user.
`folderConflictStrategy`	No	'skip' keeps the existing local folder (default). 'merge' merges contents into it. 'rename' downloads under a unique name. 'remove' deletes the local folder first — confirm with user.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.2.0Sep 30, 2026

changedInput schema / properties / confirmed / description

Previous value: -"Must be true. Only set after the user explicitly approved this exact action."New value: +"Must be true; only after the user approved this exact action."

changedInput schema / properties / fileConflictStrategy / description

Previous value: -"'skip' leaves an existing local file unchanged (default). 'rename' downloads under a unique name. 'remove' deletes the local file and downloads the remote copy in its place — confirm with user first."New value: +"'skip' keeps the existing local file (default). 'rename' downloads under a unique name. 'remove' deletes the local file first — confirm with user."

changedInput schema / properties / folderConflictStrategy / description

Previous value: -"'skip' leaves an existing local folder unchanged (default). 'merge' merges the downloaded folder's contents into the existing one. 'rename' downloads under a unique name. 'remove' deletes the local folder and downloads the remote copy in its place — confirm with user first."New value: +"'skip' keeps the existing local folder (default). 'merge' merges contents into it. 'rename' downloads under a unique name. 'remove' deletes the local folder first — confirm with user."

changedInput schema / properties / localPath / description

Previous value: -"Absolute local DESTINATION FOLDER (must start with '/'), not the file's final path. Created automatically if it doesn't exist. The downloaded item is placed inside it, keeping its original remote name."New value: +"Absolute local DESTINATION FOLDER, not the file's final path. Created if missing; the item is placed inside it under its remote name."

changedInput schema / properties / remotePath / description

Previous value: -"Absolute remote Drive path to download (must start with '/'). E.g. /my-files/report.pdf"New value: +"Absolute remote path to download, e.g. /my-files/report.pdf."

Changed1 schema field changedv1.0.38Sep 24, 2026

addedInput schema / properties / confirmed

Added value: +{
+  "description": "Must be true. Only set after the user explicitly approved this exact action.",
+  "type": "boolean"
+}

Changed4 schema fields changedv1.0.32Aug 26, 2026

removedInput schema / properties / conflictStrategy

Removed value: -{
-  "description": "'skip' leaves an existing local file unchanged (default). 'replace' overwrites it — confirm with user first. 'keep-both' downloads under a unique name.",
-  "enum": [
-    "skip",
-    "replace",
-    "keep-both"
-  ],
-  "type": "string"
-}

addedInput schema / properties / fileConflictStrategy

Added value: +{
+  "description": "'skip' leaves an existing local file unchanged (default). 'rename' downloads under a unique name. 'remove' deletes the local file and downloads the remote copy in its place — confirm with user first.",
+  "enum": [
+    "skip",
+    "rename",
+    "remove"
+  ],
+  "type": "string"
+}

addedInput schema / properties / folderConflictStrategy

Added value: +{
+  "description": "'skip' leaves an existing local folder unchanged (default). 'merge' merges the downloaded folder's contents into the existing one. 'rename' downloads under a unique name. 'remove' deletes the local folder and downloads the remote copy in its place — confirm with user first.",
+  "enum": [
+    "skip",
+    "merge",
+    "rename",
+    "remove"
+  ],
+  "type": "string"
+}

changedInput schema / properties / localPath / description

Previous value: -"Absolute local destination path (must start with '/'). Parent directory must already exist."New value: +"Absolute local DESTINATION FOLDER (must start with '/'), not the file's final path. Created automatically if it doesn't exist. The downloaded item is placed inside it, keeping its original remote name."

Changed1 schema field changedv1.0.28Aug 12, 2026

addedInput schema / properties / conflictStrategy

Added value: +{
+  "description": "'skip' leaves an existing local file unchanged (default). 'replace' overwrites it — confirm with user first. 'keep-both' downloads under a unique name.",
+  "enum": [
+    "skip",
+    "replace",
+    "keep-both"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedv0.1.2Jun 10, 2026

changedInput schema / properties / localPath / description

Previous value: -"Absolute local destination path."New value: +"Absolute local destination path (must start with '/'). Parent directory must already exist."

changedInput schema / properties / remotePath / description

Previous value: -"Remote Drive path to download. E.g. /my-files/report.pdf"New value: +"Absolute remote Drive path to download (must start with '/'). E.g. /my-files/report.pdf"

First observedv0.1.0Jun 10, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Discloses behavior the annotations do not: folder downloads recurse, the return shape is {downloaded, skipped, failed} rather than a path, the call fails if any file fails, and the destructive 'remove' path deletes the LOCAL item and is gated by confirmed=true. This is exactly the kind of mutation/confirmation nuance the agent needs, and it does not contradict the destructiveHint=false default since deletion is opt-in and user-approved.

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?

Front-loads the core purpose, then layers the tricky localPath semantics, recursion, defaults, return shape, and confirmation gate. No filler; every sentence carries an operational fact.

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?

With no output schema, the description compensates by describing the return counts and failure behavior, and it covers recursion, conflict defaults, and confirmation requirements. An agent has everything needed to call this correctly.

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 goes further by clarifying that localPath is a destination FOLDER with a concrete worked example ('/my-files/report.pdf' with '/tmp/out' yields '/tmp/out/report.pdf') and by restating the confirmed gating condition. That added meaning, especially the example, exceeds the schema text.

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 and resource ('Download a file or folder from Proton Drive to the local filesystem'), and the scope (file vs folder, recursive) distinguishes it from siblings like photos_download, drive_read_file, and drive_sync_plan. An agent can identify it without opening the schema.

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

Usage Guidelines4/5

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

Gives clear operational context: when confirmed=true is mandated ('remove' strategies that delete the local item), and that file/folder conflict strategies are separate and default to 'skip'. It stops short of explicitly naming when to prefer this over drive_read_content or drive_sync_plan, so routing between siblings remains inferential.

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

Deploy Server

Download from Drive

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools