vault-engine
Related Servers
Alternatives to vault-engine
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read, search, write, and link notes in an Obsidian vault via MCP tools and resources.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to remotely access and interact with Obsidian vaults via MCP, supporting note operations, tag management, graph queries, and command execution.6GPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to list, read, search, create, update, rename, and delete markdown notes in a local Obsidian vault via an HTTP MCP endpoint.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLM clients to read, search, and write to a local Obsidian vault over MCP, with full-text search, vault analytics, health scoring, and policy-enforced file operations.1MIT
- AlicenseAqualityBmaintenanceExposes a typed, provenance-aware knowledge graph over an Obsidian vault to coding agents over MCP, so they can trace what grounds a claim, compute which other notes a change makes wrong, surface contradictions and admitted gaps, and assemble a task-specific token-budgeted subset of the vault. Indexing, retrieval, and impact analysis run with zero third-party runtime dependencies beyond the Python standard library.10MIT
- AlicenseAqualityBmaintenanceTurns a plain-Markdown Obsidian vault into a second brain that any MCP-speaking coding agent can search, read, extend, and maintain, using swappable SQLite, Qdrant, or markdown memory backends with automatic re-indexing and wiki-link graph navigation. Exposes read, write, and index tools plus an operator CLI for health, linting, and graph export.12MIT
TDQS
Scored across 6 tools
Each tool has a distinct primary purpose (graph metrics, search, lint, backlinks, scaffolding), but broken-link checking appears in four tools (inspect_graph counts them, find_broken_links lists them, get_backlinks and lint_note also report them), creating some selection ambiguity. The description headers ([BROKEN LINK DETECTOR], [VAULT LINTER], etc.) help an agent choose, but an agent may still pick the wrong tool when it just wants broken links.
All names share a consistent vault_ prefix and use snake_case with verb_noun structure (inspect_graph, find_broken_links, lint_note, get_backlinks, scaffold_note). The only minor deviation is vault_search, which lacks a noun component.
Six tools is a well-scoped set for a vault analysis/linting server, and each tool earns its place. It is on the lean side given that the surface is read/analyze-only with no mutation tools.
The analysis surface (search, graph metrics, lint, backlinks, broken links, scaffolding) is reasonably covered, but there is no tool to read a full note's content, write/create a note from the scaffold, update frontmatter, rename/move a note, or fix broken links. These gaps mean an agent can diagnose issues but cannot remediate them, and vault_lint_note needs content that no tool can fetch.