Skip to main content
Glama

Related Servers

Alternatives to Lucy Memory MCP

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables agents to search and read saved memory and to propose memory saves, updates, links, and archives that remain pending until a user approves them in the local workspace.
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    A local decision graph built from your repo's git history, PRs, ADRs and CLAUDE.md/AGENTS.md, plus Jira, Linear, Notion, Slack and others read-only. Coding agents query it for what was decided and why, and every edit is checked against it before it is written.
    19
    4,612 npm
    24
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables MCP-capable agents and chat apps to store, recall, pin, and manage hierarchical, provenance-aware memories with deterministic scoring and shared access across clients.
    298 npm
    3
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables agents and MCP clients to retain, recall, screen, quarantine, approve, supersede, and verify durable memories with session-level provenance. Every write passes a poisoning gate, so suspicious or secret-bearing entries are held for human review rather than silently trusted in later sessions.
    1
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables agents to store, recall, and manage persistent memory documents through MCP tools, with authenticated context tokens and hybrid lexical/vector search.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to store, search, and resolve shared memories with full provenance, conflict detection, and an audit trail across MCP-compatible clients.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides persistent, searchable memory for MCP-compatible agents, enabling recall by meaning, automatic decay, trust scoring, and cross-agent handoffs.
    5
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to store and semantically retrieve durable memories across sessions via MCP or REST, with tools for remembering, recalling, asking, updating, and forgetting memories.
    17 npm
    MIT

TDQS

A3.6/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct role: recall reads approved memories, propose submits a pending write, and proposal_status checks approval state. Descriptions explicitly separate active approved memory from pending proposals, minimizing misselection.

Naming Consistency4/5

All names use a consistent memory_ prefix in snake_case, with recall/propose as verbs. memory_proposal_status is noun-oriented rather than verb_noun, but still predictable and readable.

Tool Count4/5

Three tools fit a focused, approval-gated memory workflow without bloat. It is slightly thin, but each tool maps to a necessary stage: recall, propose, and status check.

Completeness3/5

The surface covers reading approved memories, proposing a write, and checking proposal status. It lacks explicit update, delete/forget, or supersede operations, which are notable gaps for a durable memory lifecycle.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues