Skip to main content
Glama
lukaisailovic

remarkable-mcp

remarkable_execute

Run custom JavaScript against the reMarkable API to list, browse, search, read, download, upload, move, rename, remove, create notebooks, add/remove pages, write ink or text, draw Mermaid diagrams, manage tags, and refresh the tablet UI.

Instructions

Run JavaScript against the reMarkable API (SSH tablet or rmfakecloud).

declare const rme: { list(args): Promise; // List notebooks, PDFs, EPUBs, and folders. Trash is hidden unless includeTrash is true. browse(args): Promise; // Browse one folder path (default /). Opening a notebook returns that item. search(args): Promise; // Search by notebook name or path, optionally filtered by tag. info(args): Promise; // Notebook/folder/PDF info. Notebooks include pages[].title from the first typed line. read(args): Promise; // Read a notebook page (native paragraphs + checkbox state). Omit page to read every page. PDFs/EPUBs return extracted text. download(args): Promise; // Download the raw PDF or EPUB as base64. exportPage(args): Promise; // Render ink on a notebook page to PNG or SVG (base64). Does not render typed text. upload(args): Promise; // Upload a PDF or EPUB (base64) into a folder. mkdir(args): Promise; // Create a folder. move(args): Promise; // Move a notebook or folder into another folder (folder: "/" for root). rename(args): Promise; // Rename a notebook or folder. remove(args): Promise; // Move a notebook or folder to trash. createNotebook(args): Promise; // Create a blank notebook with one page. addPage(args): Promise; // Append (or insert after N) a blank notebook page. Returns the new 1-based page number. removePage(args): Promise; // Delete a 1-based notebook page. writeInk(args): Promise; // Append pen/highlighter strokes to a page. Points are [x,y] in 0–1 from the top-left. writeMermaid(args): Promise; // Draw a Mermaid diagram as ink (flowchart, sequence, state, class, ER, xychart). Renders to SVG then strokes. pie/gantt/etc. error. writeText(args): Promise; // Append native Type Folio text to a notebook page (default: last page). style: title (big), heading, body (small), bullet, checkbox. checked:true ticks a checkbox. blocks: mixed styles in one call. replace:true overwrites typed text (ink stays). newPage:true adds a blank page first. Repeated calls stack as new paragraphs. tag(args): Promise; // Add or remove a notebook tag (or a page tag when page is set). tags(args): Promise; // List every tag used on the tablet. refresh(args): Promise; // Restart xochitl so the tablet UI reloads the library. };

Write an async arrow function. No TypeScript syntax. Example: async () => { const docs = await rme.list({}); return docs; }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesJavaScript async arrow function to execute
Install Server

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It does so thoroughly: e.g., 'Trash is hidden unless includeTrash is true', 'exportPage ... Does not render typed text', 'writeMermaid ... pie/gantt/etc. error', and 'Repeated calls stack as new paragraphs' for writeText. It also notes refresh restarts xochitl, a side effect. This is rich, honest transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long, but it is well-structured like a TypeScript declaration with one-line comments per method. The primary purpose is front-loaded, and the method list is logically grouped. Every line adds necessary information for a complex execution environment; the length is justified and not redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's high complexity (arbitrary code execution over a rich API) and the lack of an output schema, the description is remarkably complete. It covers all available operations, their parameters, return types (as Promise<unknown>), notable behaviors, and limitations. The example anchors the usage, making the context fully self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While the input schema only describes the 'code' parameter minimally, the description adds immense semantic value by defining the entire rme API that the code can call, including parameter notes (e.g., 'folder: "/" for root', 'style: title (big), heading...'). It also provides a full example, effectively turning the description into a mini-API reference that exceeds the schema's brief description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a clear, specific purpose: 'Run JavaScript against the reMarkable API'. It then enumerates a comprehensive set of methods (list, browse, search, etc.) each with a brief semantic, making the tool's function unmistakable and distinct from any sibling concept, though no siblings exist.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit instructions on how to invoke the tool: 'Write an async arrow function. No TypeScript syntax.' and includes a concrete example. While it doesn't compare to alternative tools (none exist), it clearly outlines the expected format and gives a starting point for the code, which is sufficient guidance for use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Other Tools

Latest Blog Posts

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/lukaisailovic/remarkable-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server