About this integration
Access your reMarkable tablet - read documents, browse files, extract text and OCR handwritten notes
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- user-authorization
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.7.0
- Package
- rm-mcp
- Last compatibility test
- Not independently tested
Connect your agent
rm-mcpPublisher documentation and package metadata were reviewed from pinned captures. The package and reMarkable Cloud connection were not executed or independently security-audited. Although one tools section calls the tools read-only, the same README also documents rename, move, and folder-creation behavior; operators should enable REMARKABLE_READ_ONLY when mutation is not intended.
Capabilities: Browse and search a reMarkable document library, Extract typed text from notebooks, PDF, and EPUB documents, Render notebook pages as PNG or SVG resources, Perform client-sampling OCR on handwritten notes, Rename or move documents and create folders
Connected profiles
Additional details
io.github.wavyrai/rm-mcp
Source ↗ · Checked 2026-09-170.7.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17REMARKABLE_TOKEN
Source ↗ · Checked 2026-09-17rm-mcp
Source ↗ · Checked 2026-09-200.7.0
Source ↗ · Checked 2026-09-20The publisher documents background PDF/EPUB indexing enabled by default and a client-managed MCP command configuration; this is documentation evidence only, not a runtime test.
Source ↗ · Checked 2026-09-20A reMarkable Connect subscription and one-time user code are required to obtain REMARKABLE_TOKEN. The publisher does not identify the underlying authentication protocol, so the native authentication class remains unknown rather than being labeled OAuth or API key.
Source ↗ · Checked 2026-09-20The documented local MCP connection launches rm-mcp with uvx and passes REMARKABLE_TOKEN in the client-managed environment; the existing stdio connection and null endpoint are preserved by the eligibility-update path.
Source ↗ · Checked 2026-09-20Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-20