Delx Memory
Give coding agents a local-first SQLite memory layer with search, TTL, and secret-safe storage shared across MCP sessions.
Overview
Delx Memory is a MCP server for the Build phase that provides a local-first SQLite key/value memory store for agents with search, TTL, and secret-safe operations.
What is this MCP server?
- Local-first shared SQLite key/value store (default ~/.delx-memory/db.sqlite, override via DELX_MEMORY_PATH)
- Searchable entries with TTL awareness for expiring context
- Secret-safe handling suited to agent memory without blasting credentials into prompts
- Stdio default transport; optional HTTP via DELX_MEMORY_TRANSPORT with host, port, and CORS env vars
- npm package delx-memory v0.2.1
- Published version 0.2.1 on npm identifier delx-memory
- Default DB path ~/.delx-memory/db.sqlite unless DELX_MEMORY_PATH is set
- Optional HTTP transport default host 127.0.0.1 port 3030 per env documentation
What problem does it solve?
Coding agents forget project context every session unless you manually re-paste state or risk leaking secrets into unstructured notes.
Who is it for?
Solo builders who want one persistent memory file on disk for Claude Code or Cursor across days of shipping the same product.
Skip if: Multi-tenant production user data that needs hosted Postgres, auth, and backups—use your app backend instead.
What do I get? / Deliverables
After registration, agents can store, search, and expire shared memory locally via MCP while keeping sensitive values out of casual prompt dumps.
- Persistent searchable agent memory on disk
- MCP tools for read/write/search with TTL-aware entries
Recommended MCP Servers
Journey fit
Persistent agent memory is introduced while building the agent stack but pays off again when you operate and iterate on the same product context. A searchable TTL-aware KV store is classic agent-tooling—how the agent remembers decisions, prefs, and project facts between runs.
How it compares
Local SQLite agent memory MCP, not the Delx Protocol continuity/witness bridge.
Common Questions / FAQ
Who is Delx Memory for?
Indie developers and agent builders who need durable, searchable, TTL-aware memory on their own machine without standing up a cloud memory API.
When should I use Delx Memory?
Use it while building and operating agent workflows whenever the same facts must survive session restarts, with optional expiry for time-bound context.
How do I add Delx Memory to my agent?
Install npm package delx-memory, optionally set DELX_MEMORY_PATH, add the stdio server to your MCP config, and optionally switch to HTTP with DELX_MEMORY_TRANSPORT=http and port env vars.