Skip to main content
Glama
LewenW

memory-bridge

by LewenW

Related Servers

Alternatives to memory-bridge

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Cross-project memory for Claude Code, enabling local semantic recall and secure, git-versioned markdown storage of reusable knowledge across repositories.
      MIT
    • A
      license
      Not graded
      quality
      B
      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
      A
      quality
      D
      maintenance
      Persistent memory + intelligent context for Claude Code. Save and reuse solutions, decisions, and patterns across projects.
      43
      7
      MIT

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct operation: health analysis, listing shared memories, namespace management, promotion to shared, searching, and syncing to projects. No two tools have overlapping purposes.

    Naming Consistency5/5

    All tools use consistent snake_case verb_noun pattern (get_, list_, manage_, promote_, search_, sync_), making them predictable and easy to distinguish.

    Tool Count5/5

    Six tools cover the core memory management tasks without unnecessary duplication. The count feels well-scoped for a memory bridge server.

    Completeness4/5

    The set covers health checks, listing, namespace management, promotion, search, and syncing. Missing direct memory deletion or retrieval by ID, but the core workflow of saving and sharing memories is complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues