Skip to main content
Glama
agent-memory-sqlite
by Urthella

agent-memory-sqlite

ci

Persistent, searchable memory for coding agents, exposed as an MCP server. Your agent saves the decisions and conventions it learns, and recalls them in the next session instead of rediscovering them.

  • One SQLite file, shared safely by every agent session (WAL mode)

  • Zero native dependencies: Node's built-in node:sqlite with FTS5, nothing to compile on Windows, macOS or Linux

  • Ranked recall: BM25 relevance, boosted by recency, scoped per project

  • Works with any MCP client: Claude Code, Cursor, Claude Desktop, Windsurf

Quick start

Requires Node 24+.

Claude Code

claude mcp add memory -- npx -y github:Urthella/agent-memory-sqlite

Cursor / Claude Desktop (mcp.json / claude_desktop_config.json)

{
  "mcpServers": {
    "memory": { "command": "npx", "args": ["-y", "github:Urthella/agent-memory-sqlite"] }
  }
}

Then just work: tell the agent "remember that we deploy on Vercel", and ask "what do we know about deploys?" in a later session.

Related MCP server: rekal

Tools

Tool

What it does

remember

Save a fact, decision or convention, with optional tags. Saving the same text again refreshes it instead of duplicating.

recall

Keyword search, best match first. Prefix matching, so lock finds locks.

recent

The latest saved or refreshed memories.

forget

Delete a memory by its #id.

Every tool takes an optional project. It defaults to the name of the directory the agent runs in; "*" searches all projects.

How it works

flowchart LR
  A[Coding agent] -- MCP over stdio --> S[server.ts]
  S --> M[(memories table)]
  M -- insert/update/delete triggers --> F[(FTS5 index)]
  S -- MATCH + bm25 --> F
  • Storage: a plain memories table plus an external-content FTS5 index kept in sync by triggers, so text is stored once and every write path updates search.

  • Dedup: a SHA-256 of the text is unique per project; saving it again only bumps updated_at.

  • Safe queries: free text is reduced to quoted prefix terms ("redis"* OR "lua"*), so punctuation and FTS operators in a question can't break the query.

  • Ranking: the top BM25 hits are reranked by relevance × (1 + recency), where recency halves every 30 days.

  • Accents: the tokenizer folds diacritics, so agac finds ağaç.

Configuration

Variable

Default

AGENT_MEMORY_DB

~/.agent-memory/memory.db

AGENT_MEMORY_PROJECT

name of the current directory

Develop

npm ci        # also builds dist/
npm test      # node --test, runs the .ts sources directly

nix develop (or direnv) gives you the same Node 24 toolchain. CI runs on Linux, macOS and Windows.

License

MIT

Available Tools

4 tools
forgetA
Destructive

Delete a memory by its id (the #number shown by recall and recent).

Inputs: id (required).

recallC
Read-only

Search saved memories by keywords. Best matches first (BM25), with recent memories ranked higher.

Inputs: query (required), limit, project.

recentB
Read-only

List the most recently saved or refreshed memories.

Inputs: limit, project.

rememberB

Save a durable fact, decision or convention for future sessions. Saving the same text again refreshes it instead of duplicating.

Inputs: content (required), tags, project.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool maps to a clear memory operation: save, search, list-recent, and delete. The only mild overlap is between recall and recent, since both retrieve memories, but their descriptions distinguish keyword search from recency listing.

    Naming Consistency4/5

    Names are short, lowercase, and mostly verb-based (remember, recall, forget). 'recent' is an adjective rather than a verb, which is a minor deviation from the otherwise consistent pattern.

    Tool Count5/5

    Four tools is well-scoped for a lightweight memory server: save, search, list, and delete cover the core lifecycle without bloat. Each tool earns its place.

    Completeness4/5

    The surface covers create, search, list, and delete, with deduplication on re-save. A direct update-by-id operation is missing, but remember's refresh behavior and forget cover most practical workflows.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI coding assistants with persistent project memory to retain architectural decisions, code patterns, and domain knowledge across sessions. It stores data locally in a SQLite database, allowing agents to remember, recall, and manage project-specific context using full-text search.
      3 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      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.
      52
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides AI agents with a persistent long-term memory over a single SQLite file, letting them write, screen, consolidate, and recall notes across sessions without any generative LLM in the loop. Recall judges relevance, follows links between notes, and signals when memory is insufficient, so agents get one to three useful facts per question instead of a generic top-k list.
      11
      84 PyPI
      4
      MIT