Delx Memory MCP server
Local-first persistent memory MCP: shared SQLite key/value store, searchable, TTL-aware, secret-safe
2 stars302 downloads/wk
Reviews
Write oneNobody has reviewed Delx Memory yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Delx Memory tools (8, 3 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
memory_exportDump the memory store as JSON, JSONL, or Markdown. Optional since/until window on updated_at. Use for backup/inspection. Requires explicit_user_intent: true.
memory_forgetwrite actionDelete a single key from memory. Idempotent: returns existed=false if the key was not present. Requires explicit_user_intent: true.
memory_forget_by_tagwrite actionDelete every entry carrying the given tag. Returns deleted_count. Requires explicit_user_intent: true.
memory_getExact key lookup. Returns the stored value plus timestamps, ttl, tags, metadata. Returns null if missing or expired.
memory_listList keys with optional prefix or tag filter. Returns keys + timestamps + tags only — call memory_get for values. Use this first on a new session to discover what is stored.
memory_searchFull-text search across keys, values AND tags. Uses an FTS5 index with bm25 relevance ranking (key-weighted), word-stemming, diacritic folding and prefix matching — so multi-word, partial and accent-insensitive queries all hit, ranked by relevance. Falls back to a LIKE substring scan if the SQLite build lacks FTS5. Returns top N matches with a snippet. Case-insensitive.
memory_setwrite actionCreate or update a key in memory. Rejects credential-shaped keys or values. Requires explicit_user_intent: true. Returns whether the row was created or updated.
memory_statsHigh-level stats about the local memory store. Safe to call first on every session to gauge whether the store is empty, small, or large.
Public scan report
scanner v0.1.10 · 2026-11-08 · same rubric, same numbers if you re-run it
- Code scan22 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 3 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Delx Memory compares
Against every graded E-commerce MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 93% of 2,172 E-commerce servers
- Tools
- 8
- the typical E-commerce server has 7
- Tools that change things
- 38%
- typical: 3%. Fewer write tools means less an agent can break
- GitHub stars
- 2
- more than 80% of 1,055 E-commerce servers
- Downloads a week
- 302
- more than 82% of 479 E-commerce servers with a package
What its tools let an agent do: 5 read · 3 change
Install Delx Memory in Claude Code, Cursor or VS Code
Runs npx -y delx-memory on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add delx-memory -- npx -y delx-memory
What the publisher says
From the Delx Memory repository's README, as published. We do not edit it. Read it on GitHub
delx-memory
Local-first persistent memory MCP server. One shared SQLite store any MCP-speaking agent (Claude Desktop, Cursor, Hermes, OpenClaw, Codex) can read and write — so context survives across sessions AND across tools.
Why
Every chat client has its own ephemeral context. Quit the tab → preferences gone. Switch from Claude Desktop to Cursor → starting from scratch. Pin a side project in Hermes → invisible to the next agent.
delx-memory is a tiny MCP server that exposes a single shared SQLite file as a key/value memory layer. Any client that speaks MCP can read and write the same memory file → real continuity, real cross-tool context.
- 15 tools — discovery + handoff + batch ops + FTS5 search + mutations gated by intent.
- SQLite at ~/.delx-memory/db.sqlite (0700 dir, 0600 file).
- Secret-blocking: refuses to store credential-shaped keys or values.
- TTL support (lazy expiry on read).
- Tags + prefix filters + FTS5 full-text search (bm25 ranking, stemming, diacritic folding; LIKE fallback if FTS5 is unavailable).
- Mutations require explicituserintent: true so over-eager agents can't silently rewrite your context.
- Zero telemetry. Zero phone-home. The file is yours.
Multi-agent namespaces
# Agent A
DELX_MEMORY_NAMESPACE=claude npx -y delx-memory
# Agent B (same machine, isolated keys)
DELX_MEMORY_NAMESPACE=cursor npx -y delx-memoryKeys are stored as namespace::key. Omit the env var for a single global store (default).
Footprint / lightweight mode
- Default transport is lite: tools-only MCP over stdio without loading the MCP SDK (biggest RSS win for always-on agents).
- Full SDK surface (prompts + resources): delx-memory --sdk or DELXMEMORYTRANSPORT=sdk.
- Optional HTTP: delx-memory --http (Express + SDK; still loopback by default).
- DELXMEMORYLEAN=1 applies to the SDK path only (skip prompts/resources).
- doctor --json reports rss_kb. Dominant remaining cost is Node + native better-sqlite3 (no embeddings).
Community measurements (custom transport vs SDK) pointed at the SDK tree as the main overhead — see issue #7.
Install + run
# Run once (npx will download + boot)
npx -y delx-memory doctor
# Or install globally
npm install -g delx-memory
delx-memory doctorThe doctor command checks Node version, DB writability, and file permissions, then prints next steps.
HTTP (v2 stateless)
Default is stdio. Optional Streamable HTTP — no session id, JSON responses, loopback only:
npx -y delx-memory --http
# GET http://127.0.0.1:3030/health
# POST http://127.0.0.1:3030/mcp (sessionless)Env: DELXMEMORYHOST, DELXMEMORYPORT, DELXMEMORYTRANSPORT=http.
Wire it into your MCP client
Claude Desktop
Add to ~/Library/Application Support/Claude/claudedesktopconfig.json (macOS):
{
"mcpServers": {
"delx-memory": {
"command": "npx",
"args": ["-y", "delx-memory"]
}
}
}Then restart Claude Desktop. See examples/claude-desktop.json.
Cursor
Add to ~/.cursor/mcp.json. See examples/cursor.json.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Delx Memory: common questions
- Is Delx Memory MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Delx Memory safety report
- How do I install Delx Memory?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Delx Memory need an API key?
- No secret keys are declared. It reads 5 settings from the environment.
- Is Delx Memory maintained?
- The last commit was 10 days ago (2026-11-05). The latest release is v0.2.3.
- What can I use instead of Delx Memory?
- Servers from other publishers that do the same job: Mneme Memory MCP server, Kagura Memory Cloud MCP server and Steam MCP Server. Compare all Delx Memory alternatives.
- How does Delx Memory compare with other E-commerce MCP servers?
- safety score 92/100 (higher than 93% of 2,172 E-commerce servers); tools 8 (the typical E-commerce server has 7); tools that change things 38% (typical: 3%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Delx Memory
Same job from other publishers: the closest match first, then the best rated.
- Mneme MemoryCross-session memory for AI coding agents via six tools; local-first SQLite store.not reviewedEstablishedA
- Kagura Memory CloudPersistent memory for AI assistants: store, search, and connect knowledge across conversations.not reviewedGrowingA
- Steam MCP ServerSteam store/game data (no key) plus player profiles, libraries and achievements (Steam Web API).not reviewedGrowingB
Apify MCP ServerExtract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡not reviewedEstablishedA- CLIO ChronologRecord and retrieve agent interactions in a ChronoLog log store.not reviewedEstablishedA