home / mcp / proton drive mcp server

Proton Drive MCP Server

MCP server for Proton Drive - enables AI assistants to access your Proton Drive files

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "anyrxo-proton-drive-mcp": {
      "command": "node",
      "args": [
        "path/to/proton-drive-mcp/dist/index.js"
      ],
      "env": {
        "PROTON_DRIVE_PATH": "\\/custom\\/path\\/to\\/ProtonDrive"
      }
    }
  }
}

You can run a lightweight MCP server on your machine to let AI assistants interact with Proton Drive files. This enables you to list, read, write, create folders, and delete items directly through your MCP client, all locally and securely.

How to use

Once you have the MCP server running, you connect it to Claude Desktop, Cursor, or any MCP-compatible client. You will be able to ask your AI assistant to perform common file operations on Proton Drive, such as listing files, reading file contents, creating or updating files, creating folders, and deleting items. The server operates locally, so your data stays on your device without sending information to external servers.

How to install

Prerequisites you need before installing:

Node.js 16 or higher
Proton Drive desktop app installed and synced
Claude Desktop, Cursor, or any MCP-compatible client

Choose one installation path:

Install from npm (recommended)
Install from source

Install from npm (recommended)

npm install -g proton-drive-mcp

Install from source

git clone https://github.com/anyrxo/proton-drive-mcp.git
cd proton-drive-mcp
npm install
npm run build

Configuration and usage notes

Proton Drive path auto-detection is supported, but you can also specify it manually for your environment.

Path examples by platform:

macOS: ~/Library/CloudStorage/ProtonDrive-[email]-folder

Windows: C:\Users\[username]\Proton Drive

Linux: ~/ProtonDrive

Explicit MCP command examples for Claude Desktop and Cursor

Claude Desktop and Cursor can run the MCP server as a local process. Use the following configurations in your client to start the MCP server.

{
  "mcpServers": {
    "proton-drive": {
      "command": "node",
      "args": ["path/to/proton-drive-mcp/dist/index.js"]
    }
  }
}

Cursor configuration follows the same pattern, placed in your client settings.

Custom Proton Drive path

If you keep Proton Drive in a non-standard location, provide the path via an environment variable in your MCP config.

{
  "mcpServers": {
    "proton-drive": {
      "command": "node",
      "args": ["path/to/proton-drive-mcp/dist/index.js"],
      "env": {
        "PROTON_DRIVE_PATH": "/custom/path/to/ProtonDrive"
      }
    }
  }
}

Testing the MCP server

Verify the MCP server is working by running tests or performing a few simple tasks from your MCP client, such as listing files or reading a file.

Security and privacy

All operations are performed locally on your filesystem. No data is sent to external servers. Path validation helps prevent directory traversal issues.

Development and troubleshooting

Development commands include installing dependencies, building, starting in development mode, and running tests.

npm install
npm run dev
npm run build
npm test

Available tools

check_mount

Verify Proton Drive is accessible from the MCP server.

list_files

List contents of a directory on Proton Drive.

read_file

Read and return the contents of a file.

write_file

Create or overwrite a file with provided content.

delete_file

Remove files or folders.

create_folder

Create a new directory at a specified path.