Skip to main content
Glama
vault-engine

vault-engine

by Bagas10k

Related Servers

Alternatives to vault-engine

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to remotely access and interact with Obsidian vaults via MCP, supporting note operations, tag management, graph queries, and command execution.
      6
      GPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to list, read, search, create, update, rename, and delete markdown notes in a local Obsidian vault via an HTTP MCP endpoint.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Exposes 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.
      10
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Turns 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.
      12
      MIT

    TDQS

    B3.2/5.0

    Scored across 6 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.