Skip to main content
Glama
owrede

vault-memory

by owrede
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to vault-memory

No user-submitted related servers found.

    Related Servers

    • Brainstem

      DarkCodePE
      A
      license
      Not graded
      quality
      C
      maintenance
      Local-first knowledge backend for AI agents that connects MCP hosts to an Obsidian-compatible vault with indexed retrieval, token-budgeted memory recall, and secure ingestion.
      1
      MIT

    • exomem

      Artexis10
      A
      license
      Not graded
      quality
      A
      maintenance
      Durable memory with sources, proof, history, and review for MCP-capable agents. It turns a Markdown/Obsidian vault into a local knowledge substrate, enabling agents to store, search, and retrieve governed knowledge.
      10
      AGPL 3.0

    • ragvault

      maxrotemberg04-spec
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for local-first RAG over Obsidian vaults, enabling AI agents to search and ask questions about notes with grounded citations.
      MIT

    • Obsidian AI Brain

      Nolane-x
      A
      license
      Not graded
      quality
      C
      maintenance
      A local-first RAG, MCP, REST, and CLI bridge for Obsidian vaults that enables AI agents to retrieve cited knowledge from notes without uploading the vault.
      1
      MIT

    • ja-local-kb

      jefferyadventure519-byte
      F
      license
      Not graded
      quality
      A
      maintenance
      A local knowledge base MCP server that enables retrieval and evidence-based Q&A over Obsidian Markdown notes, with high-recall embedding search, chunked indexing, hybrid retrieval, and three STDIO MCP tools for agent-driven recollection and quality-gated recall.
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 37 tools

    Disambiguation3/5

    Multiple retrieval tools overlap heavily: search, search_text, search_semantic, search_hybrid, search_sections, and recall all return related documents with different ranking/scoping semantics. Document-structure tools like get_outline, get_document_bundle, and search_sections also blur together, though the detailed descriptions mostly save the set from being unusable.

    Naming Consistency3/5

    Most tools follow a recognizable verb_noun pattern like get_outline, write_note, and query_frontmatter, but bare/generic names such as search, fetch, recall, expand, cluster, and supersede break the pattern. Noun-style names like audit_log, index_runs, and vault_stats add further inconsistency, making the surface less predictable than it should be for 37 tools.

    Tool Count2/5

    37 tools is well into the 'too many' range for a single MCP server, especially with five deprecated tools still exposed and several near-duplicate search variants. The broad feature areas of notes, memory, briefs, embeddings, links, and contracts would be easier to navigate with consolidation and removal of deprecated entries.

    Completeness4/5

    The tool surface is extensive and covers note CRUD, search, frontmatter, links, citations, briefs, memory sinks, embeddings, and contracts, so agents rarely hit dead ends. Minor gaps exist, such as no note rename/move tool, no list-all-notes tool, and no embedding-model registration tool, but these are workable.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources