reMarkable MCP
ReviewAudited by ClawScan on May 1, 2026.
Overview
The skill is coherently aimed at reading and searching reMarkable tablet content, but it relies on an external MCP package and optional credentials that users should verify before use.
Install this only if you want your agent to access reMarkable documents. Verify the external remarkable-mcp package, prefer USB mode for local access, and avoid enabling cloud tokens or Google Vision OCR unless you understand the data and credential exposure.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The external MCP server will run locally and mediate access to the user's reMarkable content.
The documented setup runs an external MCP package that is not included in the provided artifacts; this is central to the skill's purpose, but users should verify the package source.
"command": "uvx", "args": ["remarkable-mcp", "--usb"]
Verify the remarkable-mcp package provenance and version before adding it to openclaw.json.
If cloud mode is used, the configured MCP server may access documents available through the user's reMarkable account.
Cloud mode uses a reMarkable token, which is expected for cloud access but grants account-level access that should be protected.
"REMARKABLE_TOKEN": "your-token"
Prefer USB mode when possible, keep tokens out of shared files, and revoke or rotate the token if it is no longer needed.
Handwritten notes or rendered page content could be sent to an external OCR provider when OCR features are used.
The optional OCR path involves an external provider; private handwritten pages may need to be processed by Google Vision for OCR.
For handwriting OCR, add a Google Vision API key
Only enable the Google Vision key if you are comfortable with that provider processing the relevant note content.