noetrail-mcp
Related Servers
Alternatives to noetrail-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides AI agents with typed tools to bootstrap sessions, ingest files, search, read, write, link, handoff, self-check, and audit markdown notes in a self-hosted Obsidian-compatible vault.3MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to search, read, and traverse Markdown note vaults (Obsidian-compatible) with full-text search, backlinks, knowledge graphs, and a persistent memory system for cross-session context.1613 npm4MIT
- AlicenseAqualityBmaintenanceProvides an AI agent with a searchable markdown notes vault, offering tools to create, read, list, search, update, and delete notes stored as plain .md files.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read and write to a personal knowledge vault of markdown notes, projects, and tasks, with tooling for search, capture, daily logs, and project management across different AI tools.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to search and retrieve notes from a local Markdown vault using hybrid keyword/semantic search, and to save typed memories with append and guarded replacement operations.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to semantically search and retrieve content from a local Markdown vault. Provides tools for fetching specific notes and finding related ones via embeddings and wikilinks.MIT
TDQS
Scored across 28 tools
Most tools target clearly distinct resources and actions (capture vs update vs trash, set_relation vs set_unresolved_relation, get_attachment vs add_attachment vs list_pending_attachments). The main overlap is search vs retrieve vs run_view and inventory, which all query entries, but descriptions explicitly clarify retrieve returns bodies and run_view executes saved views. Boundaries are generally clear enough to select correctly.
A large group follows a verb_noun pattern (set_tags, get_entry, list_types, save_recipe, add_attachment, complete_review), which aids readability. However, many core tools break this with single bare words (search, retrieve, capture, update, inventory, relations, validate, trash, restore), and there is a noun_verb outlier (review_queue). Mixed conventions but still decipherable.
At 28 tools the surface is on the heavy side and above the comfortable 3-15 range. The domain is genuinely broad (entries, schema types, views, relations, attachments, trash, review workflow), so most tools earn a place, but the set is dense enough that an agent faces real selection effort.
Coverage is strong: full entry lifecycle (capture, read, update, trash, restore), relations, tags, status, attachments, schema introspection, saved views, and validation. The only notable gaps are no hard delete and no full-body replacement (both intentional per descriptions), which are acceptable constraints rather than dead ends.