remarkable-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sambt94/remarkable-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server