Skip to main content
Glama

Related Servers

Alternatives to Vezlu

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Persistent, shared memory for Claude across sessions and clients (Code, Desktop, Cowork) — deterministic diff reads, checkpoints, cross-client task handoff, and project-wide search. 100% local and deterministic, no API keys, no LLM summarization.
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides Claude with persistent local memory and a structured knowledge graph for tracking project states, task dependencies, and historical context. It enables users to store notes, manage task relationships, and perform time-travel queries to reconstruct past information without relying on cloud services.
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code to record a verifiable history of code changes with before/after and rationale, and to propose changes that users can accept or discard, all reviewable on a local web timeline.
      -
    • A
      license
      A
      quality
      A
      maintenance
      Enables Claude to save, retrieve, update, search, and organize personal ideas and reusable analytical frameworks in a private SQLite-backed knowledge base. Supports local desktop use or always-on access across a user's own devices over a private network.
      8
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables local-first document versioning with content-addressable storage, word-level AST diffs, and AI-compliance auditing for LLM agents.
      6
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent, searchable memory for Claude Code using local SQLite, semantic embeddings, and full-text search, enabling Claude to recall and retrieve context across sessions and projects without external services.
      18 npm
      4
      MIT

    TDQS

    B3.3/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool maps to a distinct resource and action: project listing/creation, branch listing/forking, artifact reading/writing, revision history, head comparison, and merging. No two tools overlap in purpose, and guards like expected_head further clarify use.

    Naming Consistency3/5

    Names are all lowercase and readable, but they mix resource nouns (projects, branches, history) with bare verbs (create, read, branch, write, compare, merge). The pattern is understandable but not a consistent verb_noun convention.

    Tool Count5/5

    Nine tools is well-scoped for a lightweight versioned artifact store. Every tool covers a needed facet—projects, branches, revisions, reads/writes, diffs, and merges—without redundancy.

    Completeness4/5

    Core workflows for creating projects, branching, reading/writing artifacts, inspecting history, comparing heads, and merging are covered. Minor lifecycle gaps remain, such as deleting or renaming projects and branches, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues