RemNote MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REMNOTE_WS_PORT | No | The WebSocket port used to communicate with the RemNote MCP Bridge plugin. (Default: 3002) | 3002 |
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 |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| remnote_create_noteC | Create a new note in RemNote with optional content, parent, and tags |
| remnote_searchC | Search the RemNote knowledge base for notes matching a query |
| remnote_read_noteC | Read a specific note from RemNote by its Rem ID |
| remnote_update_noteC | Update an existing note in RemNote (change title, append content, or modify tags) |
| remnote_append_journalC | Append content to today's daily document in RemNote |
| remnote_statusA | Check the connection status and statistics of the RemNote MCP bridge |
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
Each tool has a clearly distinct purpose: append_journal targets daily documents, create/read/update_note handle note lifecycle operations, search finds notes, and status checks connectivity. There is no overlap in functionality, making tool selection unambiguous for an agent.
All tools follow a consistent 'remnote_verb_noun' pattern with snake_case throughout (e.g., remnote_append_journal, remnote_create_note). The naming is predictable and adheres to a uniform convention without any deviations.
With 6 tools, the server is well-scoped for managing a knowledge base like RemNote. It covers core operations (create, read, update, search) plus specialized functions (append_journal, status), avoiding bloat while ensuring each tool earns its place.
The toolset provides strong CRUD coverage for notes and search, with additional utilities for journaling and status checks. A minor gap exists in note deletion functionality, but agents can work around this by updating notes or using other methods, and the core workflows are well-supported.