A
licenseB
qualityF
maintenanceA server that consolidates 21+ Obsidian tools into 5 intelligent operations (vault, edit, view, workflow, system) with contextual workflow hints to help AI agents effectively interact with Obsidian.
5
26 npm
36
MIT
NOUZ MCP Server
by Semiotronika
Related Servers
Alternatives to NOUZ MCP Server
- FlicenseNot gradedqualityDmaintenanceProvides a coherent memory layer for LLM agents that models beliefs as nodes in a constraint network to detect and surface semantic contradictions. It uses local embeddings and a hybrid geometric-logical energy model to identify conflicting information that requires review.-
Related Servers
- AlicenseAqualityCmaintenanceMCP server for local knowledge management with Markdown and PDF indexing using SQLite FTS5.56 npm2MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that enables full-text search and link navigation over Markdown files as a knowledge graph.-
- AlicenseNot gradedqualityAmaintenanceMCP server that turns a Markdown folder (e.g. Obsidian vault) into a second brain, capturing readings and ideas, connecting them as concepts, and resurfacing related notes on demand.45 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for a personal knowledge base that captures and structures idea fragments, enabling MCP-capable agents to search, retrieve, and add notes with semantic links and clustering.3MIT
- AlicenseAqualityAmaintenanceMCP server for managing a local, domain-agnostic knowledge base using Markdown notes with frontmatter. Enables AI agents to capture, read, search, link, and maintain notes with atomic writes and privacy controls.13MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that provides semantic memory with search, related-content traversal, and write-back capabilities, all powered by local embeddings of your notes, documents, and chat histories.3MIT
TDQS
A4.2/5.0
Scored across 8 tools
Disambiguation4/5
Most tools have clear, distinct responsibilities: write_file is for creating/replacing notes, update_metadata is for frontmatter-only edits, and suggest_metadata provides classification advice. The only mild overlap is that write_file with content_lock=true can also update metadata-only, but the descriptions are explicit enough to guide correct selection.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern (index_all, read_file, write_file, update_metadata, list_files, get_children, get_parents, suggest_metadata). There is no mixing of conventions or unexpected naming styles.
Tool Count5/5
Eight tools is a well-scoped set for a Markdown vault knowledge-base server. Each tool covers a distinct operation without redundancy, and the count is neither too sparse nor overwhelming.
Completeness3/5
The core content lifecycle (read, create/replace, update metadata, index, list, traverse) is covered, but obvious operations are missing: there is no delete/remove toolchers, no search/query tool despite embeddings being mentioned, and no explicit move/rename workflow. These are notable gaps but not fatal for basic note management.
Maintenance
ActivityMaintained
ResponsivenessWithin a week