Skip to main content
Glama
Sign In
RecallNest

RecallNest

by AliceLJY
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to RecallNest

No user-submitted related servers found.

    Related Servers

    • scratchbook-mcp

      jinyaolin
      A
      license
      A
      quality
      D
      maintenance
      A codebase-memory MCP server for AI coding agents with hybrid semantic+BM25 code search, structural outlines, a work journal, and gaze-and-think deep reasoning over a local LanceDB database.
      9
      1
      Apache 2.0

    • llm-memory-tool

      menoxz
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables persistent, hybrid, local memory for LLM agents, with vector + BM25 search, knowledge graph, and policy-driven retention, providing token-budgeted context injection for AI assistants.
      MIT

    • MCP Memory

      TWFBusiness
      F
      license
      Not graded
      quality
      D
      maintenance
      Persistent memory server for AI assistants with semantic search and three-layer context (global, project, personality). Works with MCP-compatible AI tools like Claude Code, Cursor, Continue, Cline, and more.
      1
      -

    • codemem

      kunickiaj
      A
      license
      B
      quality
      A
      maintenance
      Persistent memory MCP server that captures coding session context and automatically injects relevant memories into prompts using hybrid search for OpenCode and Claude Code.
      14
      79
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 30 tools

    Disambiguation2/5

    Multiple tool families have overlapping boundaries: store_memory/store_case/store_workflow_pattern/store_skill/batch_store/promote_memory all persist memories, distill_memory vs brief_memory vs distill_session all synthesize content, list_pins vs list_assets overlap, and data_checkup/memory_lint/memory_stats are all diagnostics. Descriptions help, but an agent can easily misselect within these clusters.

    Naming Consistency3/5

    All names are snake_case, which aids readability, but the convention is mixed: some are verb-first (store_memory, list_assets, search_memory), others are noun-first (data_checkup, memory_stats, memory_drill_down, checkpoint_session, latest_checkpoint), and one is a whimsical standalone verb (dream).

    Tool Count2/5

    At 30 tools the surface is heavy for a memory server, and several clusters (five-plus store variants, multiple diagnostics, multiple list tools) earn their place only marginally over consolidated alternatives. The count exceeds the 25-tool threshold for a well-scoped set.

    Completeness4/5

    Coverage is broad: capture, store, search, retrieve, drill-down, delete, pin, export/import, consolidate, checkpoint/resume, reminders, skills, patterns, cases, stats, and linting. The main gap is no direct update/edit tool for existing memory content, and asset-level deletion is not exposed beyond forget_memory.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources