Skip to main content
Glama
leandromlmoreira

Recall

by leandromlmoreira
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Recall

No user-submitted related servers found.

    Related Servers

    • kepta

      DamianTodorovic
      A
      license
      Not graded
      quality
      B
      maintenance
      Local memory for AI agents in one SQLite file on your own machine. Facts carry a validity window and a confidence score, so an outdated one is superseded and downweighted rather than deleted, and retrieval fuses BM25, vector similarity and a knowledge graph.
      2
      AGPL 3.0

    • code-recall

      AbianS
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives AI coding agents persistent memory by storing observations, decisions, and learnings in a local SQLite database with vector search, full-text search, and a rules engine.
      4
      MIT

    • rekal

      janbjorge
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides long-term memory for LLMs via local SQLite storage with hybrid search (BM25, vectors, recency decay), enabling AI coding agents to persist and recall memories across sessions without cloud or API keys.
      53
      MIT

    • al-buddy-memory-mcp

      flytomoon
      A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI agents governed, provenance-tagged memory where facts are invalidated rather than deleted and every recall result carries validity dates, confidence, and replacement links. Stores memory in a local SQLite file with tools for remembering, recalling, invalidating, and pinning facts, plus policy enforcement and an audit trail.
      1,295 npm
      3
      Apache 2.0

    • agent-logbook

      Rajwantmishra
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to maintain long-term memory by logging and retrieving facts and decisions in a SQLite database, with relevance ranking and full history tracking.
      7
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool maps to a distinct memory operation: store (remember), retrieve (recall), delete (forget), connect (link), log (timeline), and reinforce. No two tools overlap in purpose, and descriptions clearly delineate boundaries.

    Naming Consistency4/5

    Five of six tools are single-word imperative verbs (remember, recall, forget, link, reinforce), but timeline is a noun, breaking the verb pattern. Still readable and mostly consistent, with only this minor deviation.

    Tool Count5/5

    Six tools are well-scoped for a long-term memory server, covering core actions without bloat. Each tool earns its place and the set feels neither thin nor heavy.

    Completeness4/5

    Core lifecycle is covered: create, read, delete, link, reinforce, and event log. No direct update operation, but replacing a fact via remember + supersedes link handles it; minor gap but workable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources