A Filesystem Root grants the Advanced API/MCP Server named, standing access to one specific local folder, so a script or AI agent can work with files on your Mac without you re-authorizing every request. Go to Settings > Advanced > Filesystem Roots.
Requires a Klass-RM Uploader Pro license - including just listing your configured roots or their contents. This is unlike listing your reMarkable documents, which is free: there is no existing free surface in the app that already shows your local filesystem, so there is no reason to leave this one ungated. reMarkable Connect is never required - this is local-disk access, unrelated to your reMarkable account. Mac only.
Adding a root
Pick a folder with the standard folder picker, and choose its access level:
- Read-only (the default) - enforced at the OS level. A read-only grant literally cannot be written through, not just checked in the app.
- Read-write - allows write operations too.
What an agent can do with a root
Once a root is configured, an agent or script can address files inside it by the root's ID and a path relative to it, using nine operations available on both the REST API (/api/v1/filesystem/*) and the MCP server (Filesystem_* tools):
- List a directory
- Read a file
- Write a file
- Get file info
- Find files updated since a given time
- Create a directory
- Move a file
- Delete a file
A write, create-directory, move, or delete additionally requires the target root to be read-write - attempting one against a read-only root is refused with a clear error.
This is also what backs the Advanced API's path-based upload source - instead of always sending a file as base64-encoded bytes, an upload request can name a file inside a Filesystem Root by root ID and path. See the Advanced API and MCP Server page.
Filesystem Roots and Watched Folders
A folder can be both a Filesystem Root and a Watched Folder at the same time - the two features are independent and do not conflict. The app currently only warns you if a new root's path overlaps another configured root, not if it overlaps an active watched folder.
Exporting a cloud document straight into a Filesystem Root is not available yet. If you're looking for a destination picker to send an export directly into a root, it does not exist yet - use the normal Export flow on the Exporting Files from reMarkable page and point it at a regular folder instead.