rm

This MCP server, rm-mcp, connects your reMarkable library to AI tools by exposing a set of read-only capabilities. It allows Claude, Claude Desktop, VS Code Copilot, and similar assistants to read, search, and traverse your entire library, including handwritten notes via OCR. Key tools include remarkable_read for extracting and paging through document text, remarkable_browse for navigating folders, remarkable_search for content-wide searches, remarkable_recent for recently modified items, remarkable_status to verify connectivity, and remarkable_image to render page images (with optional OCR). All tools return structured JSON to enable reliable downstream processing and prompts for next steps. You can curate access with root-path filtering and background color options to tailor the experience for your workflows. To use the tools, configure your MCP client to point at the rm-mcp server (e.g., in Claude Code or Claude Desktop), and supply the necessary REMARKABLE_TOKEN for authentication. The server handles OCR through the client’s sampling capability, so no extra API keys are required.

Prerequisites: Node.js and npm installed on your machine, access to a reMarkable account with a reMarkable Connect subscription via uvx. Ensure you have the ability to install global npm packages and run commands from your terminal.

1. Install the uvx CLI (if you don’t already have it):

npm install -g uvx

2. Obtain a one-time token via the Quick Install flow (preferred) or use the manual setup steps described in the repository README. The one-command setup is:

uvx rm-mcp --setup

This will prompt you to authorize via your browser and print a ready-to-paste MCP config snippet for Claude Code or Claude Desktop.

3. If you need to run the MCP server manually, start it with:

uvx rm-mcp

This will start the server and expose the MCP endpoints for your clients to connect.

4. Integrate with your MCP client:

• Claude Code:

claude mcp add remarkable \
  -e REMARKABLE_TOKEN='<paste token from step 2>' \
  -e REMARKABLE_OCR_BACKEND=sampling \
  -- uvx rm-mcp@latest

• Claude Desktop: add to mcp config (path to uvx may vary on your system) with the snippet shown in the setup output or using the provided config structure.

5. If you prefer the manual configuration, place the following in your MCP client configuration (adjust paths as needed):

{
  "mcpServers": {
    "remarkable": {
      "command": "uvx",
      "args": ["rm-mcp"],
      "env": {
        "REMARKABLE_TOKEN": "<paste token from step 2>",
        "REMARKABLE_ROOT_PATH": "/",
        "REMARKABLE_OCR_BACKEND": "sampling",
        "REMARKABLE_BACKGROUND_COLOR": "#FBFBFB"
      }
    }
  }
}

Environment variables provide important configuration options. REMARKABLE_TOKEN is required for authentication and comes from the uvx setup flow. REMARKABLE_ROOT_PATH can restrict the server to a specific folder (default is /). REMARKABLE_OCR_BACKEND enables OCR on handwriting when supported by the client (default is sampling). REMARKABLE_BACKGROUND_COLOR affects image rendering; use a hex color like #RRGGBB or #RRGGBBAA. Other tuning options include REMARKABLE_CACHE_TTL for metadata caching, REMARKABLE_MAX_OUTPUT_CHARS to cap tool responses, and REMARKABLE_PAGE_SIZE for PDF/EPUB text extraction. If you encounter permission or network issues, ensure the token is valid, the server process can reach the reMarkable cloud, and your MCP client is configured to reach the rm-mcp server URL. For best results, keep the REMARKABLE_ROOT_PATH scoped to the work area you want to expose to tools.