Claude Memory Lite · MIT source

Persistent project memory for Claude Code.

Claude Memory Lite is the compact member of the Gilligan Tech Inc. memory family: a local SQLite MCP server for repo rules, architecture notes, deploy facts, preferences, and decisions that should survive across coding sessions.

Open the Memory Lite repo Compare Full MCP memory

Install Evidence

A small local server, not a hosted account.

The repo is public, MIT licensed, and built for Claude Code/Claude Desktop MCP configuration with one local SQLite database.

GitHub destination github.com/Gilligan-Tech-Inc/claude-memory

{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": ["-y", "@gilligantechinc/claude-memory"]
    }
  }
}

# Optional: install globally for faster startup
npm install -g @gilligantechinc/claude-memory
# then use  "command": "claude-memory"  in the config above

Storage

One local database

Memory lives in SQLite under the developer account. No hosted login, no cloud database, no telemetry layer.

Keyword recall

SQLite FTS5/BM25 is enough for short project notes where exact words, repo tags, and recency matter.

Workflow

Bootstrap first

The agent loads repo context at session start, then works with current rules instead of stale assumptions.

Proof

Company infrastructure

This is the same operational memory discipline behind Gilligan Tech Inc.'s product and RAG delivery work.

Tool Surface

Built for durable Claude context.

Use Claude Memory when the information is short, authoritative, and should be recalled before work begins.

Tool	Purpose
`memory_bootstrap`	Load repo rules, architecture, deploy notes, and preferences at session start.
`memory_save`	Persist a durable note, rule, decision, or preference.
`memory_recall`	Find memory by keyword, filters, and recency weighting.
`memory_update`	Correct an existing memory when project truth changes.
`memory_archive`	Retire stale notes without deleting history.

01 / SAVECapture the rule

A project fact becomes a short, searchable memory note.

02 / RECALLLoad it first

Claude starts the next session with the right rules and deploy constraints.

03 / SHIPReduce rework

The agent spends less time rediscovering context and more time executing safely.