reMarkable MCP Server

reMarkable MCP Server

Access a reMarkable library from MCP clients such as Claude, VS Code Copilot, OpenWebUI, and other compatible tools.

Features

• Browse folders and recent documents.
• Search names, tags, and extracted text.
• Read typed text, PDF and EPUB text, highlights, and annotations.
• Render notebooks and annotated PDFs as PNG or SVG.
• Export one document as a complete PDF or sectioned Markdown resource.
• Run handwriting OCR through Google Vision or Tesseract.
• Upload files and manage folders in supported transports.
• Render Markdown as PDF and upload it to the tablet.
• Open an interactive canvas in clients that support MCP Apps.
• Serve MCP over stdio or local Streamable HTTP.
• Serve MCP 2026-07-28 and every earlier SDK-supported revision from one stable SDK 2.x MCPServer.

Quick Install

Prerequisite: install uv

The commands below use uvx, which is included with uv. Page images are rasterized with PyMuPDF; no system Cairo, browser, or graphics runtime needs to be installed on macOS, Linux, or Windows.

macOS and Linux

Use the official standalone installer:

curl -LsSf https://astral.sh/uv/install.sh | sh

Or install with Homebrew:

brew install uv

Windows

Use the official standalone installer from PowerShell:

powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

Or install with WinGet:

winget install --id=astral-sh.uv -e

Choose a connection

Start with the first mode that fits your setup.

USB Web Interface

Connect via USB and enable the web interface in your tablet's Storage Settings.

%22%2C%22password%22%3Atrue%7D%5D&config=%7B%22command%22%3A%22uvx%22%2C%22args%22%3A%5B%22remarkable-mcp%22%2C%22--usb%22%5D%2C%22env%22%3A%7B%22GOOGLE_VISION_API_KEY%22%3A%22%24%7Binput%3Agoogle_vision_api_key%7D%22%7D%7D) %22%2C%22password%22%3Atrue%7D%5D&config=%7B%22command%22%3A%22uvx%22%2C%22args%22%3A%5B%22remarkable-mcp%22%2C%22--usb%22%5D%2C%22env%22%3A%7B%22GOOGLE_VISION_API_KEY%22%3A%22%24%7Binput%3Agoogle_vision_api_key%7D%22%7D%7D&quality=insiders)

1. Connect your reMarkable via USB
2. On your tablet, open Settings > Storage and enable USB web interface
3. Install via the button above

Manual USB web configuration

Add to .vscode/mcp.json:

{

"servers": { "remarkable": { "command": "uvx", "args": ["remarkable-mcp", "--usb"], "env": { "GOOGLE_VISION_API_KEY": "your-api-key" } } } }

• Make sure your reMarkable is connected via USB and unlocked
• Verify USB web interface is enabled in Settings > Storage
• The tablet should be accessible at http://10.11.99.1

Local Directory Mode

Read the official reMarkable desktop app's sync folder from disk. This mode is offline and read-only. The desktop app controls synchronization.

Local directory configuration

Add to .vscode/mcp.json:

{

"servers": { "remarkable": { "command": "uvx", "args": ["remarkable-mcp", "--local-dir"] } } }

With no path, the desktop app's data folder is auto-detected:

• macOS (current app): ~/Library/Containers/com.remarkable.desktop/Data/Library/Application Support/remarkable/desktop
• macOS (legacy app): ~/Library/Application Support/remarkable/desktop
• Windows: %APPDATA%\remarkable\desktop
• Linux: ~/.local/share/remarkable/desktop

Or point at any xochitl-style directory (e.g. a tablet backup):

{

"servers": { "remarkable": { "command": "uvx", "args": ["remarkable-mcp", "--local-dir", "/path/to/xochitl-data"] } } }

• Content freshness depends on the desktop app. Keep it running and signed in.
• This mode is read-only. Direct writes could bypass synchronization and corrupt the app cache.
• If the directory can't be found and a cloud token is configured, the server falls back to cloud mode for read access (the server remains read-only because it was launched in local-directory mode)

Cloud Mode

Cloud mode works without a device connection and requires a reMarkable Connect subscription.

It fetches metadata in parallel and caches content-addressed blobs on disk. See Cloud performance and caching for configuration.

Cloud mode setup

1. Get a One-Time Code

Go to my.remarkable.com/device/desktop/connect and generate a code.

2. Convert to Token

uvx remarkable-mcp --register YOUR_CODE

Registration saves the token to ~/.rmapi. When your MCP client runs the server as the same user on the same machine, remarkable-mcp reads that file automatically, so you do not need to put a token in the client configuration. Set REMARKABLE_TOKEN only when ~/.rmapi is unavailable, such as when the server runs under another user or on another machine.

3. Configure your MCP client

Minimal client-neutral server definition

Add this server definition using the MCP configuration UI or wrapper required by your client:

{

"command": "uvx", "args": ["remarkable-mcp"] }

No env entry is needed when the server can read the token from ~/.rmapi.

VS Code

VS Code's .vscode/mcp.json uses a top-level servers object. The saved ~/.rmapi credential means no token input is required:

{

"servers": { "remarkable": { "command": "uvx", "args": ["remarkable-mcp"] } } }

Claude Desktop and other clients

Claude Desktop and many other MCP clients use a top-level mcpServers object and literal values in env; they do not use VS Code's inputs array. With the token available in ~/.rmapi, the minimal configuration is:

{

"mcpServers": { "remarkable": { "command": "uvx", "args": ["remarkable-mcp"] } } }

If the token file is unavailable, add "env": {"REMARKABLE_TOKEN": "your-token"} to the remarkable server entry. Consult your client's documentation if it uses a different outer key or secret-storage mechanism.

SSH Mode

SSH provides direct filesystem access and native notebook authoring. It requires developer mode, which factory-resets the tablet when enabled. Use this mode only when USB web, local directory, or cloud mode does not provide the operation you need.

{

"servers": { "remarkable": { "command": "uvx", "args": ["remarkable-mcp", "--ssh"] } } }

See the SSH setup guide for authentication and device setup.

Connection Modes

All modes support reading, rendering, and single-document export. Cloud and SSH support full library management. USB web supports upload but does not accept a destination folder. Local directory mode is read-only.

¹ Folder ops = create folder / move / rename / delete. Upload and folder ops are enabled by default; pass --read-only to expose a read-only server. Deletes move items to the trash and prompt for confirmation when your client supports elicitation, and are refused without it unless REMARKABLE_SKIP_CONFIRM=1 is set.

² The desktop app itself signs in to the reMarkable cloud to sync; local directory mode just reads whatever the app has already synced to disk.

Automatic cloud fallback

If a selected device transport is unavailable and a cloud credential is configured, the server falls back to cloud mode. A server launched with --local-dir remains read-only after fallback. remarkable_status reports the effective transport and sets fell_back_to_cloud.

Pass --no-cloud-fallback (or set REMARKABLE_DISABLE_CLOUD_FALLBACK=1) to disable this and fail instead when the device is unreachable.

The transport is resolved once per server process. Restart the MCP server after connecting a device or starting the desktop app if the process already fell back to cloud.

Detailed setup:

• USB web setup
• SSH setup
• Cloud performance and caching

OpenWebUI (Streamable HTTP)

OpenWebUI's native MCP connection uses Streamable HTTP. Start remarkable-mcp on the same machine:

uvx remarkable-mcp --http

Then add http://127.0.0.1:8000/mcp as the MCP server URL in OpenWebUI. The HTTP transport combines with --usb, --ssh, and --read-only; for example:

uvx remarkable-mcp --usb --http

The bind address and port can also be set with --host / --port or REMARKABLE_MCP_HOST / REMARKABLE_MCP_PORT.

The server uses MCP Python SDK 2.x's dual-era endpoint. Modern 2026-07-28 requests are sessionless; older clients continue to use the initialize handshake and legacy MCP sessions on the same /mcp route. The reMarkable token and selected tablet transport remain process-local CLI/env configuration and are never inferred from MCP HTTP authorization headers.

[!WARNING]

Streamable HTTP has no built-in authentication. It binds to 127.0.0.1 by

default. Keep that default unless you control the network boundary. Wildcard

binds such as 0.0.0.0 and :: are rejected because they cannot provide a

strict Host allowlist. A concrete non-loopback address is allowed but exposes