Rclone

io.github.rclone-ui由 GitHub 帳號 rclone-ui 發布v2.1.0更新於 Nov 11, 2026

MCP server for the Rclone RC API, with selectable toolsets.

概覽

AI 產生的概覽

面向 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。
安裝前請注意
工具可以複製、移動、刪除和清空資料,複製也算破壞性操作,因為可能覆寫目的端檔案;可用 RCLONE_READ_ONLY 或縮小 RCLONE_TOOLSETS 來限制。dangerous 工具集會回傳憑證(包括 rclone 本身的密碼),並能執行任意 rclone 指令或停止 rclone。RCLONE_PASS 與 RCLONE_CONFIG_PASS 屬於機密。未設定 RCLONE_URL 時,背景工作、掛載和 serve 會隨伺服器程序結束而停止。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Rclone,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

rclone-mcp

[Discord]

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.

bash
rclone rcd --rc-user=admin --rc-pass=secret

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:

json
{  "mcpServers": {    "rclone": {      "command": "npx",      "args": ["-y", "rclone-mcp"]    }  }}

With an rclone that's already running

json
{  "mcpServers": {    "rclone": {      "command": "npx",      "args": ["-y", "rclone-mcp"],      "env": {        "RCLONE_URL": "http://localhost:5572",        "RCLONE_USER": "admin",        "RCLONE_PASS": "secret"      }    }  }}

Docker

bash
docker build -t rclone-mcp .
docker run -i --rm \  -e RCLONE_URL=http://host.docker.internal:5572 \  rclone-mcp

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:

bash
npx rclone-mcp http --port 3000

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>:

bash
RCLONE_MCP_TOKEN=<a long random string> npx rclone-mcp http --host 0.0.0.0

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

VariableDescriptionDefault
RCLONE_URLA running rclone to use. Without it, rclone-mcp starts its own—
RCLONE_USERHTTP Basic Auth username for RCLONE_URL—
RCLONE_PASSHTTP Basic Auth password for RCLONE_URL—
RCLONE_TOOLSETSComma-separated toolset listdefault
RCLONE_READ_ONLYSet to 1 to expose only tools that change nothing and return no credentials—
RCLONE_MCP_MAX_OUTPUTThe most characters of output a tool call returns100000
PORTPort the HTTP transport listens on3000
RCLONE_MCP_HOSTAddress the HTTP transport listens on127.0.0.1
RCLONE_MCP_TOKENBearer token for the HTTP transport. Required unless it listens on localhost—
RCLONE_MCP_ALLOWED_ORIGINSComma-separated browser origins that can use the HTTP transport—
RCLONE_MCP_SESSION_TIMEOUTSeconds an HTTP session can sit idle before it closes1800

CLI Arguments

rclone-mcp [command]
Commands:  rclone-mcp stdio  Run with stdio transport (default)  rclone-mcp http   Run with Streamable HTTP transport
Options:  --url              A running rclone to use. Without one, rclone-mcp starts its own  --toolsets         Comma-separated list of toolsets  --read-only        Only expose tools that change nothing and return no credentials  --max-output       The most characters of output a tool call returns
HTTP options:  --port             Port to listen on (default: 3000)  --host             Address to listen on (default: 127.0.0.1)  --token            Bearer token that clients must send. Prefer RCLONE_MCP_TOKEN  --allowed-origins  Comma-separated browser origins that can use the server  --session-timeout  Seconds a session can sit idle before it closes (default: 1800)

Toolsets

Tools are grouped by API path prefix. Enable only what you need to keep the tool list focused.

ToolsetPathsDefault
core/core/*, /rc/*Yes
config/config/*Yes
operations/operations/*Yes
sync/sync/*Yes
jobs/job/*Yes
vfs/vfs/*No
mount/mount/*No
serve/serve/*No
cache/cache/*No
debug/debug/*No
backend/backend/*No
options/options/*No
fscache/fscache/*No
dangerousSee belowNo

Special values:

  • default — the five default toolsets (core, config, operations, sync, jobs)
  • all — every toolset, including dangerous

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:

ToolWhy
config_dump, config_get, options_get, options_info, serve_listReturn credentials, including rclone's own password
config_delete, config_password, config_setpath, config_unlock, config_unset, options_setChange or remove configuration
core_commandRuns any rclone command
core_quitStops rclone
job_batchCan call any route, including everything on this list
operations_purgeDeletes a directory and everything in it

Examples

bash
# Default toolsets (55 tools)npx rclone-mcp
# Everything (98 tools)RCLONE_TOOLSETS=all npx rclone-mcp
# Just file operations and confignpx rclone-mcp --toolsets operations,config
# Default + mountnpx rclone-mcp --toolsets default,mount
# Read-only mode (no copy, delete, sync, etc.)npx rclone-mcp --read-only

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 with SIGKILL, 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_uploadfile takes file contents as text or base64 in the call, so it suits small files. Use operations_copyurl or sync_copy for anything large.

Upgrading from 1.x

  • Without RCLONE_URL, rclone-mcp now starts its own rclone instead of connecting to http://localhost:5572. To keep using a server on that address, set RCLONE_URL to it.
  • rclone older than 1.76.0 is refused.
  • Fields now go in as real objects, so opt and parameters are objects rather than JSON strings.
  • _async is gone. Use run_in_background on the tools that offer it.
  • jobs is on by default, and the dangerous tools aren't.
  • --read-only no longer exposes config_dump, config_get, options_get, options_info, serve_list, core_bwlimit, operations_publiclink or cache_fetch.
  • The HTTP transport listens on 127.0.0.1 by default.
  • Node 22.19 or later is required.

License

MIT

Made with ☁️ for the rclone community

來源:README.md,提交 6672882

工具

0
SourceWeft 曾在隔離沙箱中以無憑證方式啟動該軟體包一次,以列出其工具,但未能完成:伺服器未能啟動。

版本歷史

3
  1. v2.1.0最新Nov 11, 2026
  2. v2.0.0Nov 1, 2026
  3. v1.0.0Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分