Skip to main content
Glama
Zavelinski

recall

by Zavelinski
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to recall

No user-submitted related servers found.

    Related Servers

    • claude-memory

      NathanNorman
      A
      license
      Not graded
      quality
      C
      maintenance
      A persistent memory MCP server for Claude Code that enables long-term recall across sessions via hybrid search, code intelligence, and tools for reading/writing memory.
      30 npm
      5
      MIT

    • MCP Memory Server

      imyashkale
      A
      license
      Not graded
      quality
      D
      maintenance
      A simple memory storage server for Claude using the Model Context Protocol (MCP), enabling Claude to store and retrieve text memories across conversations.
      21 npm
      MIT

    • memory-mcp

      AyubMoh1
      A
      license
      Not graded
      quality
      D
      maintenance
      Persistent memory MCP server for Claude Code. Store, search, and retrieve memories across sessions using hybrid vector + keyword search powered by SQLite, FTS5, and sqlite-vec.
      21 npm
      1
      MIT

    • Memory-Man

      HelyeFab
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides persistent long-term memory for Claude Code, enabling storage, search, and retrieval of project knowledge across sessions.
      -
    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.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: recall_get retrieves a single entry by name, recall_list enumerates all entries, and recall_search performs lexical search. No functional overlap exists.

    Naming Consistency5/5

    All tools follow a consistent 'recall_verb' pattern with clear, imperative verbs (get, list, search). The naming is predictable and easy to understand.

    Tool Count4/5

    With only 3 tools, the surface is minimal but appropriate for a read-only memory retrieval server. It covers the essential retrieval operations without unnecessary bloat.

    Completeness4/5

    The server provides complete coverage for reading memories (get by name, list all, search). Missing write operations (create, update, delete) are likely intentional, making the set complete for its stated purpose.

    Resources