RemNote MCP Server
Related Servers
Alternatives to RemNote MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables users to create, link, explore, and synthesize atomic notes through Claude and other MCP-compatible clients, with bidirectional links, tags, search, and a Markdown/SQLite-backed knowledge graph.-
- FlicenseNot gradedqualityAmaintenanceEnables users to create, link, explore, and synthesize atomic notes through Claude and other MCP-compatible clients, with markdown storage, tags, search, and semantic link types.-
- FlicenseNot gradedqualityAmaintenanceEnables users to create, link, explore, and synthesize atomic notes through Claude and other MCP-compatible clients, with semantic links, tags, search, and a Markdown-backed SQLite index.-
- FlicenseNot gradedqualityAmaintenanceEnables users to create, link, tag, search, explore, and synthesize atomic notes through Claude and other MCP-compatible clients. Notes are kept as human-readable Markdown files (with an automatically rebuilt SQLite index) and connected through typed bidirectional links that form an explorable knowledge graph.-
- FlicenseNot gradedqualityAmaintenanceEnables users to create, link, tag, search, explore, and synthesize atomic notes through Claude and other MCP-compatible clients, using Markdown files as the source of truth and an SQLite index for fast knowledge graph traversal.-
- FlicenseNot gradedqualityAmaintenanceEnables users to create, link, explore, and synthesize atomic notes through Claude and other MCP-compatible clients, using bidirectional links, tags, search, and a Markdown/SQLite knowledge graph.-
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.