Skip to main content
Glama

Related Servers

Alternatives to Vulcanus

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes a living systems memory vault to autonomous agents, letting them search notes with BM25 ranking, read sections within token budgets, extract API/port/schema contracts, compute dependency blast radius, and run machine-verifiable invariant assertions before mutating code. It also supports surgical frontmatter edits, schema linting, wikilink integrity checks, and worklog recording, over stdio MCP.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides long-lived, cross-project technical memory for AI agents via markdown cards stored in git and indexed by SQLite, enabling search, retrieval, and human-reviewed knowledge management.
      ISC
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides structured, addressable access to a local markdown vault with heading-anchored fragments, BM25 search, and stable IDs for verifiable retrieval.
      14 npm
      2
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Vault-native, accountable memory for Claude Code and MCP clients. Markdown is the source of truth, no LLM on the Stop path.
      6
      1 npm
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      A local-first CLI and MCP server that helps you build and search a personal knowledge vault from Markdown notes, with semantic search and AI-powered features like stale note detection and session memory harvesting. It’s provider-agnostic, requires no GPU in its default mode, and exposes your vault as long-term memory to any MCP-compatible AI tool like Claude Code.
      47
      Apache 2.0

    TDQS

    A4.5/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: recall for capsule retrieval, search for text search, list_projects for project routing, append_decision/update_capsule/append_rule for distinct write operations, and vault_status/doctor for health checks at different granularities. Descriptions explicitly cross-reference when to use which tool, eliminating ambiguity.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (list_projects, append_decision, update_capsule, append_rule), but recall, search, and doctor are single verbs, and vault_status is a noun compound. The minor inconsistency is easy to read and does not hinder understanding.

    Tool Count5/5

    With 8 tools, the set is well-scoped for a project memory and vault management server. Each tool earns its place, covering reading, searching, updating, and validating without bloat or redundancy.

    Completeness4/5

    The core workflows—accessing capsules, searching, updating summaries, appending decisions/rules, and checking health—are covered. Slight gaps exist: no direct tool to read decisions or rules (though search can find them) and no explicit project creation, but these may be out of scope for the vault's purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues