
Rclone
io.github.rclone-ui由 GitHub 账号 rclone-ui 发布v2.1.0更新于 Nov 11, 2026
MCP server for the Rclone RC API, with selectable toolsets.
概览
面向 Rclone RC API 的 MCP 服务器,让助手管理云存储远端、列出目录并复制或同步文件。
- 可以做什么
- 管理远端与配置:列出、创建、修改或删除 rclone 远端及其设置
- 浏览与传输文件:列出目录、复制、移动、删除、清空目录、上传小文件以及抓取 URL
- 执行并监控同步:启动复制或同步任务(可后台运行),查看任务状态与任务列表
- 控制 rclone 进程:执行命令、调整带宽限制,并在启用相应工具集时启动 VFS、挂载与 serve 端点
- 通过可选工具集和只读模式限制暴露范围,隐藏会改动数据或返回凭据的工具
- 适用场景
- 适合让助手借助已有的 rclone 环境处理跨云存储的文件,例如列出远端内容、在远端之间复制或同步、查看传输任务,而无需离开对话。
- 运行要求
- 通过 npm 包 rclone-mcp 以 stdio 在本地运行;需要 Node 22.19 或更高版本,以及 PATH 中可用的 rclone 1.76.0 或更高版本。未设置 RCLONE_URL 时服务器会用你的 rclone.conf 自行启动 rclone;若要连接已在运行的 rclone,需设置 RCLONE_URL 以及 RCLONE_USER 和 RCLONE_PASS,配置加密时还需 RCLONE_CONFIG_PASS。可选设置包括 RCLONE_TOOLSETS、RCLONE_READ_ONLY 和 RCLONE_MCP_MAX_OUTPUT。
安装
在 SourceWeft 中
- 打开 控制台中的 Rclone,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
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
来源:README.md,提交 6672882
工具
0版本历史
3- v2.1.0最新Nov 11, 2026
- v2.0.0Nov 1, 2026
- v1.0.0Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分