NoteDiscovery MCP Server
Related Servers
Alternatives to NoteDiscovery MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA free, open-source Markdown editor with a bundled MCP server (stdio, read-only): point Claude, Cursor, or any MCP client at your notes vault for local semantic search, read, and list. ~15MB, 5 platforms, MIT, local-first.1,603MIT
- AlicenseNot gradedqualityBmaintenanceLocal-first markdown vault with a built-in MCP server (streamable HTTP). 16 tools and 2 resources for Claude Code / Desktop / Cursor: read/write/search plus context_for_query, find_orphans, weekly_digest, compare_notes, semantic_outline. Per-folder agent permissions, LanceDB vectors, local Xenova ONNX embedder swappable to Ollama. Single Bun binary. AGPL.36AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceMCP server for AI agents to read, write, and organize notes in a local-first, human-in-the-loop note-taking app.3 npm2MIT
- AlicenseNot gradedqualityCmaintenanceLocal markdown notes for any MCP client: ranked + semantic search, tags, todos, a wiki-link knowledge graph, daily notes, templates, and slash-command workflows. Pure-JS, local, no API keys.11 npm1MIT
- AlicenseNot gradedqualityBmaintenanceA self-hosted MCP server that gives AI coding agents shared live docs, memory and session context from plain Markdown files on disk, with search, note editing, hand-over tasks and linting. It also provides a web UI with a graph of how notes connect, password-protected tokens, and offline sync.MIT
- AlicenseNot gradedqualityBmaintenanceA local-first CLI and MCP server that helps you build and search a personal knowledge vault from Markdown notes, with semantic search and AI-powered features like stale note detection and session memory harvesting. It’s provider-agnostic, requires no GPU in its default mode, and exposes your vault as long-term memory to any MCP-compatible AI tool like Claude Code.47Apache 2.0
TDQS
Scored across 22 tools
Most tools target a distinct resource+action (get_note vs list_notes vs search_notes vs get_recent_notes are clearly separable), and descriptions actively disambiguate the write paths. The main overlap is that create_note also updates existing notes, putting it in tension with edit_note and append_to_note, and the docs reference a non-existent update_note tool, which muddies selection slightly.
Nearly everything follows a clean verb_noun snake_case pattern (get_note, list_tags, create_folder, move_note, delete_folder, search_notes). The only deviations are health_check (noun-based) and the inconsistent verb choices for note writing (create/edit/append), which are minor and still readable.
At 22 tools this sits at the heavy end of the scale for a note vault server, spanning notes, folders, tags, graph, templates, and admin. Each tool is plausibly useful, but the surface could be trimmed (e.g. folding recent/config/health into generic listings) without losing capability.
Note lifecycle is well covered (read, create, edit, append, move, delete) along with folders, tags, graph/backlinks, search, and templates. Gaps remain: no tag add/remove or rename operations, no template create/update/delete, and no outgoing-link inspection beyond the full graph, plus a dangling reference to an update_note tool.