
Rclone
io.github.rclone-uiPublished by GitHub account rclone-uiv2.1.0Updated Nov 11, 2026
MCP server for the Rclone RC API, with selectable toolsets.
Overview
MCP server for the Rclone RC API that lets an assistant manage cloud storage remotes, list directories, and copy or sync files.
- What you can do
- Manage remotes and configuration: list, create, update or remove rclone remotes and their settings
- Browse and transfer files: list directories, copy, move, delete, purge, upload small files and fetch URLs
- Run and monitor syncs: start copy or sync operations, optionally in the background, and check job status and lists
- Control the rclone process: run commands, adjust bandwidth limits, and start VFS, mount and serve endpoints when those toolsets are enabled
- Limit exposure with selectable toolsets and a read-only mode that hides anything that changes data or returns credentials
- When to use it
- Useful when an assistant should work with files across cloud storage providers through an existing rclone setup, for example listing remote contents, copying or syncing between remotes, or checking transfer jobs, without leaving the chat.
- Requirements
- Runs locally over stdio via the npm package rclone-mcp; Node 22.19 or later and rclone 1.76.0 or later on the PATH. Without RCLONE_URL the server starts its own rclone using your rclone.conf; set RCLONE_URL plus RCLONE_USER and RCLONE_PASS to use an already running rclone, and RCLONE_CONFIG_PASS if the config is encrypted. Optional settings include RCLONE_TOOLSETS, RCLONE_READ_ONLY and RCLONE_MCP_MAX_OUTPUT.
Installation
In SourceWeft
- Open Rclone in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
rclone-mcp
MCP (Model Context Protocol) server for the Rclone RC API. Gives AI assistants the ability to manage cloud storage remotes, copy/sync files, list directories, and more — all through natural language.
Tools are generated from the rclone-openapi spec and call rclone through the rclone-sdk client. There are 98 tools, organized into selectable toolsets, and each release targets one rclone version.
Prerequisites
rclone 1.76.0 or later, on the PATH. rclone-mcp starts it for you, with your normal rclone.conf, and stops it when the client disconnects. It listens on 127.0.0.1 with a random port and login.
If your MCP client can't find rclone, set PATH in the server's env, such as "PATH": "/opt/homebrew/bin:/usr/bin:/bin". If your rclone.conf is encrypted, set RCLONE_CONFIG_PASS there too.
To use an rclone that's already running, set RCLONE_URL. Do this if transfers need to outlast the client, because stopping rclone stops its background jobs, mounts and serves.
Each release targets one rclone version, and rclone-mcp refuses anything older.
Installation
Cursor / Claude Desktop (stdio)
Add to your .cursor/mcp.json or claude_desktop_config.json:
With an rclone that's already running
Docker
The image doesn't include rclone, so RCLONE_URL is required here.
Streamable HTTP transport
For web-based MCP clients, or to share one server:
This listens on 127.0.0.1 and only answers to local hostnames and origins. Every tool can reach your remotes, so listening anywhere else needs a token, which clients send as Authorization: Bearer <token>:
Use a TLS proxy in front of it on any network you don't trust, because the token and your data travel unencrypted otherwise. A proxy on the same machine can forward to the default host, as long as a token is set.
Browser pages can only use the server from origins you list in --allowed-origins. Clients that aren't browsers don't need this.
Configuration
Environment Variables
CLI Arguments
Toolsets
Tools are grouped by API path prefix. Enable only what you need to keep the tool list focused.
Special values:
default— the five default toolsets (core, config, operations, sync, jobs)all— every toolset, includingdangerous
The dangerous toolset
These tools only appear if you ask for them, whichever path they're on. They return credentials, control the rclone process, or can do damage that's hard to undo:
Examples
Read-Only Mode
When --read-only or RCLONE_READ_ONLY=1 is set, a tool is only registered if it changes nothing and returns no credentials, whichever toolsets you pick. So config_dump, options_get and serve_list are left out as well as sync_copy and operations_delete. operations_getfile is left out too, because it reads any file that rclone can reach, and rclone.conf is one of them.
One limit remains: job_status returns the output of any job that rclone still remembers. If another client ran config/dump in the background in the last minute, its output would be visible.
Tool Annotations
Every tool declares readOnlyHint and destructiveHint, so clients can ask for confirmation before anything that could delete or overwrite data. Copies count as destructive, because they can overwrite files at the destination.
Long-Running Calls
Calls that can take a while, such as sync_copy, accept run_in_background: true. They return a job ID right away, and job_status reports progress.
Without it, the call waits until rclone finishes. If the client times out or cancels first, rclone cancels the transfer, so use run_in_background for anything long. A server you run yourself also stops answering a single call after an hour, unless you change --rc-server-write-timeout.
job_list returns the newest 100 job IDs from each list, with runningTotal and finishedTotal giving the full counts. Pass limit for a different number, and status for only running or only finished jobs. Rclone counts every call as a job, including job_status and job_list themselves, so the newest IDs aren't always work you started.
Limits
- Its own rclone stops with it: without
RCLONE_URL, each rclone-mcp process starts its own rclone, and background jobs, mounts and serves stop with that process. With stdio, that means each client gets its own, and they don't see each other's jobs. Sessions on one HTTP server share one rclone. If rclone-mcp is killed withSIGKILL, its rclone keeps running until you stop it. - Sessions: the HTTP transport keeps up to 100 sessions, closing the longest-idle one to make room. Its client gets a 404 and starts a new session, as the MCP spec describes.
- Output: a call returns at most 100,000 characters, with a note when it's cut. Ask for less, or raise
RCLONE_MCP_MAX_OUTPUT. - Unknown fields: a field that a route doesn't document is an error, because rclone would ignore it without saying so. Routes that accept extra options, such as
serve_start, allow them. - Uploads:
operations_uploadfiletakes file contents as text or base64 in the call, so it suits small files. Useoperations_copyurlorsync_copyfor anything large.
Upgrading from 1.x
- Without
RCLONE_URL, rclone-mcp now starts its own rclone instead of connecting tohttp://localhost:5572. To keep using a server on that address, setRCLONE_URLto it. - rclone older than 1.76.0 is refused.
- Fields now go in as real objects, so
optandparametersare objects rather than JSON strings. _asyncis gone. Userun_in_backgroundon the tools that offer it.jobsis on by default, and thedangeroustools aren't.--read-onlyno longer exposesconfig_dump,config_get,options_get,options_info,serve_list,core_bwlimit,operations_publiclinkorcache_fetch.- The HTTP transport listens on
127.0.0.1by default. - Node 22.19 or later is required.
License
Source: README.md at commit 6672882
Tools
0Version history
3- v2.1.0LatestNov 11, 2026
- v2.0.0Nov 1, 2026
- v1.0.0Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts