Skip to main content
Glama

Related Servers

Alternatives to HiveMem

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides a local long-term memory layer for AI coding tools like Cursor and Claude Code, enabling cross-session, cross-tool sharing of project facts, user preferences, decisions, and workflows.
      11 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to persist project memory across sessions by compiling decisions, progress, and pitfalls into git-linked, evidence-backed entries. It lets clients add, query, inject, scan for stale, check assertions on, and compute ROI of those memories over stdio.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Persistent shared memory for AI coding agents. Stores facts as entity/key/value triples with hybrid semantic search, task checkpoints, and conflict resolution — shared across Claude Code, Codex CLI, and GitHub Copilot.
      16
      235 npm
      5
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables a team's AI coding agents to share a self-hosted memory of conventions, decisions, requirements and known errors, exposing session briefs, incremental codebase indexing, and hybrid keyword/semantic search over MCP or plain HTTP.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code, Codex and other MCP agents to share one bounded, persistent memory across sessions, so a session starts from what earlier sessions learned instead of re-reading the repository. Storage and retrieval run locally on SQLite full-text search with per-client tokens and scopes, and optional local model enrichment, without any paid model in the path.
      1
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to read and write persistent, local-first memory so project decisions, preferences, and cross-project guidelines survive across sessions and can be retrieved by semantic search. Optionally also exposes a task queue for autonomous execution that draws on the same stored context.
      -

    TDQS

    A4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct role in the memory lifecycle: search, index, read, write, update, archive, review, stats, and bootstrap. The descriptions explicitly clarify potentially confusing boundaries, especially search vs. index vs. bootstrap and archive vs. update.

    Naming Consistency5/5

    All tools follow a consistent memory_<action> naming convention with clear action verbs. There is no mixing of casing or verb styles.

    Tool Count5/5

    Nine tools are well-scoped for a memory server covering discovery, CRUD-like lifecycle, review, statistics, and project briefing. Each tool appears to earn its place without excessive surface area.

    Completeness4/5

    The surface covers the core memory lifecycle well, including write, read, update, archive, search, indexing, review, and stats. Minor gaps may exist around permanent deletion/purge or restoring prior versions, but archive and versioned reads mitigate these for normal workflows.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data