This MCP server exposes the Rclone RC API through an AI-friendly interface. It auto-generates a suite of tools from the rclone-openapi spec via the rclone-sdk, providing a large set of endpoints (about 98 tools) grouped into toolsets such as core, config, operations, and sync. By running the server with the rclone-mcp package, you enable natural-language capable assistants to list directories, copy or move files, manage remotes, and perform cloud-storage operations through the RC API. The server can be accessed locally via the RC daemon URL you provide (default http://localhost:5572) and exposed to clients through standard MCP transports (stdio or HTTP).

Prerequisites:

• Node.js and npm (or an environment that can run npx)
• A running rclone remote control daemon (rcd) accessible via HTTP, configured with no-auth or with HTTP Basic Auth as desired

Install and run (stdio transport):

1. Ensure rclone rcd is running, e.g.: rclone rcd --rc-no-auth

   or with auth:

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

2. Run the MCP server using npx (no global install required): npx -y rclone-mcp

3. If you need HTTP transport instead, you can run the HTTP variant: npx rclone-mcp http --port 3000

Docker-based run (build-and-run):

1. Build the image (Dockerfile should be provided by the project): docker build -t rclone-mcp .
2. Run the container, passing the RCLONE_URL to the RC daemon: docker run -i --rm -e RCLONE_URL=http://host.docker.internal:5572 rclone-mcp

Environment and configuration:

• Set RCLONE_URL to point to your rclone rc daemon (default http://localhost:5572).
• Optional: RCLONE_USER and RCLONE_PASS if you’re protecting the RC API with Basic Auth.
• You can control exposed toolsets with RCLONE_TOOLSETS or via command-line flags such as --toolsets and --read-only.

Tips and caveats:

• The server exposes a large set of tools; use the default toolsets (core, config, operations, sync) for a broad capability set. Use --toolsets to restrict exposed tools if you want a focused interface.
• In read-only mode (RCLONE_READ_ONLY=1 or --read-only), mutating operations like copy/move/delete and certain config actions are hidden. This is useful for AI safety in untrusted environments.
• If you’re exposing the server over HTTP, consider securing with authentication, rate limiting, and TLS as appropriate for your deployment.
• When using Docker, ensure the container can access the host's rclone rc daemon; you may need to map the RC URL accordingly (e.g., http://host.docker.internal:5572).
• The RCLONE_TOOLSETS environment variable supports values like default, all, or a comma-separated list of toolsets to tailor the available commands.