remarkable-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| remarkable_list_documentsA | List documents in the reMarkable local cache. Optional case-insensitive substring filter on document names. Returns document IDs, names, page counts, and last modified timestamps. |
| remarkable_get_document_infoA | Get detailed metadata for a single reMarkable document. Returns document ID, name, page count, page IDs, and content format (v1/v2). Lightweight — reads JSON only, no rendering. |
| remarkable_render_pagesA | Render selected pages of a reMarkable document to a single PDF. Priority: page_indices > last_n > first_n > all pages. For a 200-page doc with last_n=5, only the last 5 pages are rendered. Returns the PDF path, document name, pages rendered/failed, and indices. |
| remarkable_render_documentA | Render all pages of a reMarkable document to a single PDF. Convenience wrapper — equivalent to render_pages with no selection args. Returns the PDF path, document name, pages rendered/failed, and indices. |
| remarkable_check_statusA | Check reMarkable system status and tool availability. Returns whether the cache exists, document count, and rmc/cairo availability. Use this to diagnose issues before rendering. |
| remarkable_cleanup_rendersA | Remove temporary rendered PDFs from the render directory. Returns the number of files removed and bytes freed. Call this after you're done reading rendered PDFs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Most tools have clearly distinct purposes, but remarkable_render_document is explicitly a wrapper for remarkable_render_pages with no selection arguments, creating a slight overlap. The descriptions mitigate this by clarifying the relationship, so it's mostly unambiguous.
All tools follow a consistent verb_noun pattern with the remarkable_ prefix, such as list_documents, render_pages, and check_status. This makes the tool names predictable and easy to navigate.
With 6 tools, the server is well-scoped for its purpose of managing and rendering reMarkable documents. Each tool serves a distinct function (listing, metadata, rendering, status, cleanup) without unnecessary bloat.
The tool set covers the core lifecycle for reading and rendering documents: listing, retrieving metadata, rendering all or select pages, checking status, and cleaning up. It lacks write operations like upload or delete, but those fall outside the apparent scope of a rendering-focused server.