Skip to main content
Glama

Related Servers

Alternatives to Rememb

Related Servers

  • F
    license
    Not graded
    quality
    A
    maintenance
    Gives AI coding agents direct, local-first read/write access to persistent memory — project decisions, preferences, error patterns, research, and cross-project guidelines — retrieved by semantic search backed by SQLite with no API keys or network calls. A companion server also exposes optional autonomous task-queue execution.
    -
  • A
    license
    A
    quality
    C
    maintenance
    Persistent semantic memory for AI agents. SQLite-backed, local-first, zero config. Semantic search via Ollama embeddings with keyword fallback. Tools: remember, recall, history, forget, stats.
    17
    37 npm
    1
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Lightweight persistent memory for AI agents using a single SQLite file with hybrid search (keywords + semantics). Zero to 12MB install, no cloud or server required.
    7
    MIT
  • F
    license
    Not graded
    quality
    A
    maintenance
    Provides a local-first, cross-session memory layer that lets AI coding agents store and semantically search per-project decisions, preferences, error patterns, and research alongside global guidelines. Also supports an optional task queue for autonomous execution, all backed by on-disk SQLite with no API keys or external calls.
    -
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to store and recall durable facts, decisions, and lessons over MCP using hybrid semantic and keyword search, typed memories, graph relations, sessions, and time-travel queries. Runs locally with no server process or API key, persisting everything to files that both agents and a CLI can share.
    20 npm
    MIT

TDQS

A3.8/5.0

Scored across 18 tools

Disambiguation4/5

Core entry operations are clearly separated: write/create, edit/update, delete/soft-delete, restore, clear, get, search, recent, and versions/diff each target distinct intents. The main overlap is between rememb_read and rememb_read_page, which both return full entry content and differ only by pagination/filtering; search/recent/get are distinguishable by description.

Naming Consistency4/5

All tools consistently use the rememb_ prefix and mostly follow a verb or verb_noun pattern such as list_stores, get, search, write, edit, delete, restore, and read_page. A few names are noun/adjective-based (versions, recent, stats) rather than strict verbs, but the overall convention remains readable and predictable.

Tool Count3/5

At 18 tools the surface is borderline heavy for a memory store, with several overlapping read/list variants (read, read_page, recent, search, get) plus auxiliary skill and store-management tools. Each tool has a plausible purpose, but some read variants could likely be consolidated to reduce selection burden.

Completeness5/5

The memory lifecycle is well covered: create, read, search, update, soft-delete, restore, permanent clear, revisions, diffing, tagging, statistics, store listing, consolidation, and skill discovery/loading. No obvious CRUD or lifecycle gaps remain for the stated domain.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues