Mimir's Vault
Related Servers
Alternatives to Mimir's Vault
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that treats Obsidian vaults as knowledge graphs, enabling AI agents to traverse wikilinks, assemble token-budgeted context, and search with backlink awareness.3 npm1MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that reduces AI coding agent token usage by 80-99% through a queryable knowledge graph of code, change tracking, and persistent memory across sessions.93 npm1MIT
- AlicenseAqualityAmaintenanceLocal-first MCP server that gives any AI coding agent per-project memory, workflow intelligence, and always-on, lossless token & context optimization.3760 npm6MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that provides controlled read/write tools for managing local-first research memory in an Obsidian vault, enabling AI agents to maintain project context across sessions.4 npm1MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that exposes an Obsidian-style markdown vault as agent-readable memory. It provides tools for search, read, graph, and guarded capture without using embeddings.1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that provides a navigable map of an Obsidian vault for coding agents, with tools to outline notes, fetch sections, query frontmatter, and grep content, reducing token usage compared to reading whole notes.MIT
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: initialization, navigation, search, module creation, updating, and decision logging. There is no overlap in their responsibilities.
All tools follow a consistent verb_noun pattern in snake_case (e.g., get_root_node, create_module_node, log_decision). The naming convention is uniform and predictable.
With 7 tools, the set is well-scoped for managing a project memory graph. Each tool fulfills a specific need without unnecessary bloat or redundancy.
The toolset covers initialization, reading, creating, and updating nodes, plus decision logging. It lacks a delete or rename operation, which are minor gaps for a full lifecycle but not critical for the primary use case.