RemNote MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key, used to authenticate with the hosted Cotlet.dev MCP server. Get your key at https://cotlet.dev/app. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
RemNote through Cotlet.dev. Call remnote_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| remnote_guideA | How to work in RemNote (find notes, draft flashcards and organize documents in your own RemNote account): its screens and the sign-in link. Call this first. |
| remnote_statusA | Check that your Cotlet.dev account and RemNote are ready: account, credits and RemNote connection. |
| remnote_openB | Open a RemNote page in your signed-in Cloud Browser (default https://www.remnote.com) to work with find notes, draft flashcards and organize documents in your own RemNote account. |
| remnote_readB | Read the current RemNote page: its text and numbered buttons, links and fields. |
| remnote_clickB | Click a numbered element on the current RemNote page. |
| remnote_typeC | Type text into a numbered field on the current RemNote page. |
| remnote_closeA | Close the RemNote browser session when the work is done, so credits stop running. |
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 7 tools
Each tool maps to a clearly distinct action or state: guide/status for setup, open/read/close for browser lifecycle, and click/type for page interaction. There is no meaningful overlap between reading the page and mutating it via click/type.
All tool names use the same remnote_ prefix and snake_case, making them easy to scan and group. The only minor inconsistency is that guide and status are noun-like states while the rest are action verbs, so it is not a strict verb_noun pattern throughout.
Seven tools are well-scoped for a browser-automation wrapper: setup, open, inspect, interact, and close. There are no redundant tools and the count is not so small that essential operations are missing.
The set covers the core lifecycle: guide/status, open, read, click/type, and close for working in RemNote through the Cloud Browser. Minor gaps include no explicit wait, reload, back, or screenshot tool, though agents can likely work around these using page elements.