Skip to main content
Glama

Related Servers

Alternatives to OpenClaw Memory

  • A
    license
    A
    quality
    B
    maintenance
    Gives your AI persistent memory across conversations. Stores facts automatically, finds them by meaning using hybrid search with query expansion, and organizes everything into topics without manual tagging.
    18
    1
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides a persistent, local-first memory for coding agents over MCP, enabling automatic recall and recording of past work, failures, and decisions to reduce repetition and token usage.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables capturing and storing AI coding decisions as markdown, and provides MCP tools for assistants to query and record those decisions so they respect past architectural choices.
    MIT
  • F
    license
    Not graded
    quality
    B
    maintenance
    Enables AI coding agents to persistently store and retrieve conversation history with hybrid semantic and keyword search, cross-encoder reranking, session filtering, and archiving through MCP tools.
    -
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables local archiving and searchable recall of AI coding sessions from Claude Code, Codex, Pi, and OpenCode via MCP, allowing agents to access past conversations as context.
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Process memory for AI agents and humans that remembers the evolution of a project. Provides MCP tools to create timeline events, search history, explain files, and visualize the evolution graph.
    4
    1
    MIT

TDQS

A4/5.0

Scored across 3 tools

Disambiguation5/5

The three tools have clearly distinct purposes with no overlap: memory_log_conversation records a complete conversation turn, memory_log_conversation_append extends that recording when needed, and memory_search retrieves past conversations. Each tool serves a unique function in the conversation logging workflow.

Naming Consistency4/5

The naming follows a consistent memory_verb_noun pattern with minor deviations: memory_log_conversation and memory_search fit perfectly, while memory_log_conversation_append is slightly longer but maintains the same prefix structure. All use snake_case consistently.

Tool Count5/5

Three tools is ideal for this server's purpose of conversation memory management. It covers the core workflow of logging, appending when responses are long, and searching history without being overly complex or insufficient for the domain.

Completeness4/5

The toolset provides solid coverage for basic conversation memory operations: logging, extending logs, and searching. A minor gap exists in lacking update/delete capabilities for recorded conversations, but agents can work effectively with the provided CRD (create, read, delete via omission) functionality.

Maintenance

ActivityInactive
ResponsivenessNo issues