[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # reMarkable API and MCP server: Let your AI agent keep your reMarkable in order. > reMarkable has no public API, no developer docs and no MCP server for its cloud (checked 25 Oct 2026). Cotlet runs 9 reMarkable tools hosted, over MCP for agents and REST for scripts. Connect your reMarkable cloud files and document details to an agent or a script. Use MCP or REST to prepare a notebook index and folder reports. [MCP setup](https://cotlet.dev/integrations/remarkable-api-mcp-server.md#connect) [REST API guide](https://cotlet.dev/integrations/remarkable-api-mcp-server.md#rest-api) - Free 7-day trial, no card - Unofficial, not affiliated with reMarkable - Page: https://cotlet.dev/integrations/remarkable-api-mcp-server ## What can you automate in reMarkable? - Send PDFs and ebooks to the tablet - Sort new files into folders - Rename files to one pattern - Clear out finished files - Find a file by name or folder - Check Connect status and payments ## Does reMarkable have an MCP server or an API? - Zapier and n8n have no reMarkable app or node. Files go in by hand: the apps, the web app, a USB cable, Read on reMarkable or the Google Drive, Dropbox and OneDrive links on the tablet. - Developer mode on the Paper Pro opens a root shell on the tablet itself, after a factory reset and outside the warranty. It does not reach the cloud. - Community tools on GitHub talk to the reMarkable cloud with a device token. Their cloud mode needs a Connect subscription, and their writes stopped working for a day on 17 Aug 2026 when reMarkable changed the sync format. | What you need | reMarkable apps | GitHub MCP server | Cotlet | |---|---|---|---| | Send a PDF or EPUB to the tablet | By hand | Yes | Yes, from a link | | List, rename, move and trash from an agent | No | Yes, on your computer | Yes, hosted | | Connect status and payment history | By hand | No | Yes, read only | | Read handwritten pages | Convert on the tablet | Some, with OCR | No | | Fixed for you when reMarkable changes | Yes | No | Yes, tested every 12 h | Checked 25 Oct 2026. Sources: [reMarkable Support: About my.remarkable.com](https://support.remarkable.com/articles/Knowledge/About-my-remarkable-com), [reMarkable Support: Using reMarkable without a subscription](https://support.remarkable.com/articles/Knowledge/Using-reMarkable-without-a-subscription), [reMarkable Support: Importing and exporting files](https://support.remarkable.com/articles/Knowledge/importing-and-exporting-files), [reMarkable Support: Developer mode](https://support.remarkable.com/articles/Knowledge/Developer-mode), [ddvk/rmapi: writes fail since 17 Aug 2026](https://github.com/ddvk/rmapi/pull/77) ## How does Cotlet connect to reMarkable? 1. **Sign in to reMarkable.** Use your own account in its Cotlet Cloud Browser. 2. **Choose MCP or REST.** Connect your agent or create a Cotlet API key. 3. **Run your workflow.** Ask your agent or send an HTTP request. We never keep your reMarkable password, and nothing goes to the trash until you say so. ## Connect reMarkable to your agent or workflow Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide. 1. **Sign in to my.remarkable.com.** Create a Cotlet account, open reMarkable, sign in to your reMarkable account in its Cloud Browser and press Enable for agents. 2. **Give your agent the address.** Add https://cotlet.dev/mcp/v1 to the MCP servers or connectors of your agent. 3. **Let it in.** Chat apps open a Cotlet sign-in. Code editors, n8n and scripts take an API key from the console. reMarkable shares `https://cotlet.dev/mcp/v1` with every other app you enable. Turned reMarkable on after you connected? Refresh the connector to load its tools. Claude: ``` Settings > Connectors > Add custom connector URL: https://cotlet.dev/mcp/v1/connect Claude Code: claude mcp add --transport http cotlet-remarkable \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` ChatGPT: ``` Settings > Apps & Connectors > Create MCP server URL: https://cotlet.dev/mcp/v1/connect Authentication: OAuth ``` Cursor: ``` // ~/.cursor/mcp.json { "mcpServers": { "cotlet-remarkable": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet-remarkable] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` n8n: ``` MCP Client Tool (inside an AI Agent) Transport: HTTP Streamable URL: https://cotlet.dev/mcp/v1 Auth: Bearer, Tool: remarkable_read ``` Make, Zapier: ``` Make: MCP Client > Call a tool Zapier: MCP Client by Zapier > Run Tool Server URL: https://cotlet.dev/mcp/v1 Token: Tool: remarkable_write ``` ## How to use the reMarkable REST API ### Create your Cotlet API key Create a Cotlet API key with access to reMarkable and its read operations. Store it as `COTLET_API_KEY` in your environment or automation platform's credential store. Sign in to reMarkable in its Cotlet Cloud Browser and enable the app for agents. Use the my.remarkable.com account paired with your tablet. ### Make your first reMarkable API request cURL: ``` curl "https://cotlet.dev/api/v1/remarkable/files?folder=Reading" \ -H "Authorization: Bearer $COTLET_API_KEY" ``` ### Read one folder and follow child folders A successful REST call puts the tool output in `result`. This illustrative response excerpt omits call IDs, messages and credit details. Illustrative response excerpt: ``` { "status": "success", "app": "remarkable", "tool": "list_files", "result": { "folder": "Reading", "items": [ { "id": "f_8a1c20", "name": "Attention is all you need", "kind": "file", "file_type": "pdf", "size_mb": 2.1 } ] } } ``` Replace `Reading` with an existing folder name or ID, or omit `folder` to list the root. Read `result.items` for files and child folders. File listing reads one folder level without a cursor, page or offset. Follow returned folder IDs to build a deeper inventory. `get_file` returns metadata rather than notebook pages or handwriting. Payment history defaults to the most recent ten records and exposes no cursor. ### reMarkable workflows for agents and automations | Tool | Connect through | Example workflow | |---|---|---| | n8n | HTTP Request | Read folder contents and file metadata into a recursive document index without interpreting handwriting. | | Make | HTTP > Make a request | Combine subscription details and payment records into a private account-cost report. | | Python or Node.js | REST API | Read account details and folder contents to verify the paired account and prepare a private library inventory. | Send `Authorization: Bearer ` in request headers. You configure the schedule, destination and record comparisons. Cotlet reads reMarkable; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template. Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports. The [API and MCP reference](https://cotlet.dev/integrations/remarkable-api-mcp-server.md#tools) lists operations and inputs. The [REST API guide](https://cotlet.dev/docs/api.md) explains authentication, errors and approvals. ## reMarkable API endpoints and MCP tools ### My files: import, folders and trash Names, folders and file types as My files shows them, one folder level per call. Imports take PDF, EPUB, JPG and PNG up to 100 MB. No tool opens pages or reads handwriting. - **List files** (`list_files`, read): List the files and folders in My files, at the top level or inside one folder. - **Get file** (`get_file`, read): Read one file or folder from My files by id. - **Import file** (`import_file`, write): Import a PDF, EPUB, JPG or PNG into My files, so it syncs to your tablet. - **Rename file** (`rename_file`, write): Rename a file or folder in My files. - **Move file** (`move_file`, write): Move a file or folder to another folder in My files. - **Move file to trash** (`trash_file`, write, asks first): Move a file or folder to the trash, as Move to trash does in My files. ### Account and Connect billing Read only. The card and the plan stay in your hands at my.remarkable.com. - **Get account** (`get_account`, read): Read the name and email of the signed-in reMarkable account. - **Get subscription** (`get_subscription`, read): Read the Connect subscription status and billing interval. - **List payments** (`list_payments`, read): List your Connect payment history. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/remarkable-api-mcp-server#tools ## Who can see my reMarkable session, and how do I revoke it? - **What we store.** Your signed-in my.remarkable.com profile, AES-256-GCM, in Finland. No password. - **What your agent gets.** The 9 reMarkable tools. No cookie and no device token. - **What the session sees.** Your file names and folders, account name and email, Connect payments. - **What no tool touches.** Handwriting, the card, the plan, the password and paired tablets. - **If reMarkable signs you out.** You get an email with a sign-in link. Google or Facebook sign-in stays yours to click. - **How to cut access.** Disable for agents, reset the browser or change your reMarkable password. cotlet.dev rates A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)). We have no SOC 2 report or third-party pentest yet. ## Is it against reMarkable's terms? Account safety > You as a user shall not and shall not allow any third party to: ... copy, decompile, disassemble, reverse engineer ... interfere with or disrupt the integrity of the Software or data included therein; attempt to gain unauthorized access. > > [reMarkable End User License Agreement, section 2.3, effective 5 Nov 2025](https://support.remarkable.com/articles/Knowledge/reMarkable-End-User-License-Agreement) The EULA covers the tablet software and the mobile and desktop apps. Accounts and Connect sit under separate terms, and the Connect terms of 24 Sep 2026 say nothing about bots or outside clients. Cotlet does not touch the tablet software: it uses the web account in a browser, as you do. We found no public case of a reMarkable account closed for automation or for rmapi (checked 25 Oct 2026). How we keep your account looking like you: - Your own reMarkable account, signed in by you - One Cloud Browser with its own IP and cookies - No device token and no developer mode - Moves to the trash wait for your OK - If reMarkable objects, we pause the reMarkable tools for everyone within 24 h > Without Connect, the cloud keeps only files used and synced in the last 50 days. Import in batches you will read, not your whole archive at once. ## What happens when reMarkable changes? - **12 h** between tests of the reMarkable reads and imports - **$0** for a call to a reMarkable tool paused for a fix reMarkable changes its cloud without notice: on 17 Aug 2026 it began to reject the way community tools wrote their file index, and every write from them failed until a fix landed the next day. A fix to our tools is ours to make. [status.cotlet.dev](https://status.cotlet.dev) checks the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Finds the folder.** Lists My files so the import lands in the right place. 2. **Imports from your link.** PDF or EPUB up to 100 MB, named as you asked. 3. **Files the rest.** Moves and renames reach only your library. 4. **Asks before the trash.** Each trash call waits in your Cotlet console. | Action | Undo | |---|---| | Import a file | Yes, move it to the trash | | Rename a file or folder | Yes, rename it back | | Move a file or folder | Yes, move it back | | Move to the trash | Restore it on the tablet until the trash is emptied | 1 of 9 tools asks first: trash_file, because a trashed folder leaves your tablet at the next sync. Imports, renames and moves touch only your own library and go back with one more call, so they run at once. Switch the wait off for trash_file if a weekly cleanup should run alone. > No tool empties the trash or deletes a file for good. MCP call: ``` { "name": "import_file", "arguments": { "file": "https://example.com/files/q4-board-deck.pdf", "name": "Q4 board deck", "folder": "Reading" } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/remarkable/files \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"file":"https://example.com/files/q4-board-deck.pdf","name":"Q4 board deck","folder":"Reading"}' ``` Tool output: ``` { "id": "f_8a1c44", "name": "Q4 board deck", "kind": "file", "file_type": "pdf", "size_mb": 3.8, "folder": "Reading", "status": "imported" } ``` A script can call the same tools at `/api/v1/remarkable` with the same key and price, for example to send each new paper from a feed to Reading. A file over 100 MB or of another type fails, and a failed call is free. The tools table lists the REST path of each tool. ## How much does the reMarkable MCP server cost? **About $14 a month** for a reader importing 20 documents a month, 2,430 credits. Connect, if you have it, stays $3.99 a month at reMarkable. | Job | Calls | Credits | |---|---|---| | Import a PDF or EPUB into a folder | 2 × 20 | 400 | | Sort new top-level files, weekly | 6 × 4 | 240 | | Trash finished files, weekly | 4 × 4 | 160 | | Rename a folder's files to one pattern | 11 × 1 | 110 | | Connect status and last payments | 2 × 1 | 20 | | Cloud Browser, 30 days | | 1,500 | | Total | | 2,430 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser, the larger part here - One-time packs, valid 12 months, no subscription 20 imports a month is our assumption: no public figure for a reMarkable library exists, and Send to Remarkable sells tiers of 10 and 25 documents a month. Dollars at the $29 pack rate. ## reMarkable MCP server on GitHub or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | [SamMorrowDrums/remarkable-mcp](https://github.com/SamMorrowDrums/remarkable-mcp) | 252 stars, MIT, Python. Reads and searches documents, renders pages with OCR, uploads and manages folders over USB, SSH or the cloud. | Runs on your computer. Cloud mode needs Connect and a device token in `~/.rmapi`. Last commit 2 Oct 2026. | | [wavyrai/rm-mcp](https://github.com/wavyrai/rm-mcp) | 21 stars, MIT. Reads pages as images with OCR through your client; renames, moves, makes folders. | Needs Connect and a token from its setup. Last commit 24 Aug 2026. | | [ddvk/rmapi](https://github.com/ddvk/rmapi) | 341 stars, AGPL-3.0. Command line for the cloud: ls, put, get, mkdir, mv, rm. | Not MCP. Writes failed on 17 Aug 2026 until the next day's fix. | | [remarkdown](https://remarkdown.org/pricing) | Hosted MCP: pushes Markdown as an editable notebook, reads typed and handwritten pages back from one folder. | $9 a month or $81 a year after the first push. One connected folder. | | [Send to Remarkable](https://www.sendtoremarkable.com/) | Email a file to your own address and it lands on the tablet. | Sends only. Free for 10 documents a month, 3 MB each; $9 or $25 a year for more. | Want your agent to read handwriting? Use a GitHub server or remarkdown; Cotlet does not open pages. Want imports, folders and cleanup to run from a hosted agent with no token on your laptop? That is what Cotlet does. ## Who runs Cotlet Behind Cotlet is Take Group sp. z o.o., a software company in Poland, EU (VAT PL6342984273), in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the reMarkable tools go to contact@cotlet.dev. ## reMarkable API and MCP: questions ### Can I use the reMarkable API without an AI agent? Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST. ### How do I get access? Sign up free at https://cotlet.dev, open reMarkable under Integrations in the console and sign in to my.remarkable.com in its Cloud Browser. The trial begins with your first app and asks for no card. ### Do I need a Connect subscription? Not for the account itself. reMarkable lists Google Drive, Dropbox and OneDrive integrations, handwriting conversion and Read on reMarkable among the features of the tablet without a subscription, with limited cloud sync (files used and synced in the last 50 days). Cotlet works in the my.remarkable.com account you already have; how much reaches your tablet depends on your plan. ### Can my agent read my handwritten notes? No. These tools work on My files as the website shows it: names, folders, imports and the trash. They do not open pages or convert handwriting to text, which the tablet does itself. Reading note content is not built. ### What file types and sizes can it import? PDF, EPUB, JPG and PNG, up to 100 MB per file. reMarkable converts JPG and PNG to PDF on import. Word and PowerPoint files go through the Office add-ins or must be saved as PDF first. ### Does reMarkable have webhooks? No. reMarkable sends no events out, so nothing tells an agent that a file arrived or changed. Run the agent on a schedule instead, for example a weekly list_files pass over your top level. ### Do I need developer mode or a device token? No. Developer mode is a Paper Pro setting that wipes the tablet, and device tokens are what the GitHub tools register. Cotlet uses your web sign-in, so your list of paired devices stays as it is. ### Is the MCP server different from the REST API? Only in how you call it. MCP and REST share the 9 tools, their inputs and answers, one API key and one price. Agents take MCP; scripts and HTTP steps take REST. ### Is Cotlet affiliated with reMarkable? No. Cotlet is independent and not affiliated with reMarkable AS. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.