Skip to main content
Glama

Related Servers

Alternatives to remem

  • A
    license
    A
    quality
    B
    maintenance
    Persistent local memory for Claude Code that indexes every session's JSONL file verbatim into SQLite + ChromaDB. Exposes 17 MCP tools for semantic recall, deterministic file replay, and fuzzy "do you remember when..." queries across your entire session history — no API calls, nothing leaves the machine.
    17
    86 PyPI
    17
    MIT

Related Servers

  • A
    license
    A
    quality
    B
    maintenance
    One Rust binary that gives Claude Code, Codex and other MCP clients a shared long-term memory, stored as plain Markdown notes in an Obsidian vault. Hybrid keyword and embedding search, plus a knowledge graph you can open in Obsidian.
    25
    1
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Local-first memory shared by every AI coding tool. Captures Claude Code, Codex, Gemini CLI, Copilot, Cursor and opencode sessions into SQLite and serves recall, per-file context and a session resume block over MCP.
    9
    1,209 npm
    4
    MIT
  • F
    license
    Not graded
    quality
    C
    maintenance
    Local-first memory for AI coding agents. Indexes your Claude Code, Codex, Cursor, Cline and Gemini CLI history by repo/branch/worktree and hands a context capsule (decisions, touched files, next steps) to the next agent over MCP.
    -
  • A
    license
    Not graded
    quality
    A
    maintenance
    Gives Claude Code persistent cross-session memory with semantic search, automatic detection and classification of user corrections into behavioral patterns, and self-evolving frameworks that refine judgment over time. Everything runs locally through hooks and MCP tools, with no cloud, API keys, or telemetry.
    6 npm
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Persistent memory for Claude Code. Automatically indexes every conversation and provides production-grade hybrid search (BM25 + vectors + reranker) via MCP tools. 100% local, zero config, zero API keys, zero invoice.
    16
    50 npm
    8
    MIT

TDQS

A4.1/5.0

Scored across 15 tools

Disambiguation3/5

Most tools include explicit positioning guidance, but the set has several overlapping retrieval/context-assembly tools: search, search_raw, current_state, timeline, context_bundle, and recall_user_context could all plausibly match a lookup request. The long descriptions help disambiguate them, but an agent scanning names alone would likely confuse context_bundle with recall_user_context or timeline with timeline_report.

Naming Consistency3/5

The set mixes verb-led names like save_memory, update_workstream, and lookup_commit with noun-led names like workstreams, timeline, and context_bundle, plus the odd commits_for_session. There is no single predictable naming pattern, though the names are individually readable and avoid chaotic style mixing.

Tool Count4/5

Fifteen tools is at the upper edge of a compact surface, but the set covers memory management, raw sessions, git commit links, workstreams, and reporting without feeling padded. A few retrieval helpers could be consolidated, so it is slightly heavy rather than perfectly minimal.

Completeness4/5

The core memory lifecycle is covered: save_memory creates/updates, search and get_observations retrieve, and govern_memory handles deletion/staleness. The main gap is workstreams, which can be listed and updated but not created or deleted, though that is a workable omission for the primary memory-centric workflow.

Maintenance

ActivityActive
ResponsivenessUsually handled