Skip to main content
Glama
Kaede Recall MCP

Kaede Recall MCP

Related Servers

Alternatives to Kaede Recall MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      A persistent, project-scoped memory layer for AI coding agents, providing 39 tools for capturing, searching, deduplicating, relating, and maintaining memory records across long-running coding sessions.
      0
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI coding agents with a persistent memory layer to save, recall, update, and track memories across sessions and repositories using hybrid semantic search.
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables coding agents to store, recall, and manage persistent memory across sessions through MCP tools, with reviewable handoffs and SQLite-backed local storage.
      1
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to read and write persistent, local-first memory across sessions and projects, with semantic search, global guidelines, and optional autonomous task execution.
      -

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool maps to a distinct lifecycle action on a single resource: memory-write stores, memory-recall searches, memory-update edits in place, memory-delete removes. The write/update boundary is the only potential source of confusion, but the descriptions clearly separate storing a new memory from editing an existing one.

    Naming Consistency5/5

    All four names follow a strict memory-<verb> kebab-case pattern with action-oriented verbs (write, recall, update, delete). Fully predictable and readable.

    Tool Count5/5

    Four tools cover the full memory lifecycle (create, read/search, update, delete) with no filler. The surface is tightly scoped to the server's single purpose.

    Completeness4/5

    Core CRUD lifecycle is fully covered, including a dry-run preview on delete. Minor gaps: no explicit get-by-id or list/browse operation, and no tools for inspecting tags, entities, or links outside of recall results.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues