Rclone MCP Server
Cloud storage management using Rclone RC API for AI-driven file operations.
Data last scanned today · Reviewed today
Overview
Rclone MCP Server interfaces with the Rclone remote control daemon to expose storage management capabilities to AI assistants. It generates tools from the official Rclone OpenAPI specification, supporting a wide range of actions including file synchronization, directory listing, and remote configuration management through the RC API. The server organizes 98 available endpoints into modular toolsets. Users can tailor the functionality exposed to their AI by selecting specific toolsets, such as core, sync, or operations, and can further constrain capabilities by enabling a read-only mode to prevent unintended file modifications.
Our verdict
This server carries a high risk level with a security score of 31/100. It is a community-maintained project lacking a clear software license and missing an editorial review of its implementation. While the ability to enforce a read-only configuration provides a significant security control, users should exercise caution as the project relies on a single contributor and has not been vetted for production environments. It is recommended primarily for local, non-sensitive development workflows.
- Supports a read-only configuration mode for safety
- Modular toolsets allow granular exposure of API endpoints
- Small supply-chain footprint with only five direct dependencies
- No license detected, creating ambiguous legal usage terms
- Project maintained by a single contributor
- Lacks an editorial security review
Setup
{
"mcpServers": {
"rclone-mcp": {
"args": [
"-y",
"rclone-mcp"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What is required to run the rclone-mcp server?
You must have a running rclone remote control daemon, which can be started using the command rclone rcd.
›How do I secure the rclone remote control daemon?
You can configure the daemon to require authentication by using the --rc-user and --rc-pass flags when starting rclone rcd.
›How can I prevent the MCP server from modifying my files?
You can enable read-only mode by setting the environment variable RCLONE_READ_ONLY=1 or by passing the --read-only flag, which disables all mutating tools.
›Can I limit the number of tools exposed to the AI?
Yes, you can specify individual toolsets using the --toolsets flag or the RCLONE_TOOLSETS environment variable to include only the specific functionality you need.
›Does the server support connections from remote or web-based MCP clients?
Yes, you can run the server with the HTTP transport command instead of stdio by executing npx rclone-mcp http.
Badge
Maintain this server? Add the live badge to your README.