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.
接入你的智能体
發布者自己的指令。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
npx -y [email protected]Claude Code 沒有本機指令的安裝連結。複製下方指令並在終端機中執行。
DELX_MEMORY_PATH=<value> DELX_MEMORY_TRANSPORT=<value> DELX_MEMORY_HOST=<value> DELX_MEMORY_PORT=<value> DELX_MEMORY_ALLOWED_ORIGIN=<value> claude mcp add io.github.davidmosiah-delx-memory -- npx -y delx-memory@0.2.3在終端機中執行。
{ "mcpServers": { "io.github.davidmosiah-delx-memory": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "DELX_MEMORY_PATH": "<value>", "DELX_MEMORY_TRANSPORT": "<value>", "DELX_MEMORY_HOST": "<value>", "DELX_MEMORY_PORT": "<value>", "DELX_MEMORY_ALLOWED_ORIGIN": "<value>" } } }}claude_desktop_config.json
遠端 URL 還是本機指令? 兩種安裝方式的差異
來自發布者
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.
Local-first persistent memory MCP: shared SQLite key/value store, searchable, TTL-aware, secret-safe
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.
~/.delx-memory/db.sqlite (0700 dir, 0600 file).explicit_user_intent: true so over-eager agents can't silently rewrite your context.# Agent A
DELX_MEMORY_NAMESPACE=claude npx -y delx-memory
# Agent B (same machine, isolated keys)
DELX_MEMORY_NAMESPACE=cursor npx -y delx-memory
Keys are stored as namespace::key. Omit the env var for a single global store (default).
lite: tools-only MCP over stdio without loading the MCP SDK (biggest RSS win for always-on agents).delx-memory --sdk or DELX_MEMORY_TRANSPORT=sdk.delx-memory --http (Express + SDK; still loopback by default).DELX_MEMORY_LEAN=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.
# Run once (npx will download + boot)
npx -y delx-memory doctor
# Or install globally
npm install -g delx-memory
delx-memory doctor
The doctor command checks Node version, DB writability, and file permissions, then prints next steps.
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: DELX_MEMORY_HOST, DELX_MEMORY_PORT, DELX_MEMORY_TRANSPORT=http.
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):
{
"mcpServers": {
"delx-memory": {
"command": "npx",
"args": ["-y", "delx-memory"]
}
}
}
Then restart Claude Desktop. See examples/claude-desktop.json.
Add to ~/.cursor/mcp.json. See examples/cursor.json.
See examples/hermes.md.
See examples/openclaw.md.
See examples/codex.toml.
Not a vector DB. Not a second brain SaaS. Local continuity for agents that already have a model.
explicit_user_intent: true)Every mutation refuses to run unless the caller passes explicit_user_intent: true. The intent: an agent that decides on its own to update memory must show its work. The user can see the flag in the tool call and reject it if they didn't ask.
delx-memory is NOT a secrets manager. Use macOS Keychain / gnome-keyring / Windows Credential Manager for those.
What we refuse to store:
oauth, token, secret, password, cookie, refresh, api_key, api-key, apikey, bearer, credential, session_id (case-insensitive).eyJ…)Bearer <token> headerssk_live_… / sk_test_…xoxb-… / xoxp-… / etc.github_pat_… / ghp_… / gho_… / ghs_… / ghr_…sk-… (with realistic length)AKIA…Authorization: <scheme> <token> stringsrefresh_token (even with an empty value) is rejected.What stays local:
~/.delx-memory/db.sqlite.0700; file with mode 0600. (Best effort on Windows / WSL / non-POSIX filesystems.)What we do NOT promise:
sudo-using housemate) can read the file. Use full-disk encryption (FileVault, BitLocker, LUKS) if that matters.VACUUM automatically, so freed pages may sit on disk. For sensitive ephemera, treat the DB file like any other unencrypted dotfile.~/.delx-memory/db.sqlite like any other dotfile if you care about losing it.agent> memory_stats({})
→ { total_keys: 0, db_path: "/Users/me/.delx-memory/db.sqlite", … }
user> Remember that I prefer concise responses in pt-BR.
agent> memory_set({
key: "user_preferences",
value: { language: "pt-BR", verbosity: "concise" },
tags: ["profile", "preferences"],
explicit_user_intent: true
})
→ { action: "created", key: "user_preferences", … }
# … new chat, possibly different tool …
agent> memory_list({ tag: "preferences" })
→ [{ key: "user_preferences", updated_at: … }]
agent> memory_get({ key: "user_preferences" })
→ { found: true, value: { language: "pt-BR", verbosity: "concise" } }
delx-memory Start MCP stdio server
delx-memory --http Start local HTTP MCP server (127.0.0.1:3030)
delx-memory setup Print MCP client config snippets
delx-memory setup --json Print as JSON
delx-memory doctor Health check + next steps
delx-memory doctor --json Health check as JSON
delx-memory version Print version
git clone https://github.com/davidmosiah/delx-memory
cd delx-memory
npm install
npm test # typecheck + build + smoke + secret-detector + ttl + tag-delete + metadata
See AGENTS.md for repo conventions, SECURITY.md for the security model and reporting policy, and CONTRIBUTING.md for PR rules.
MIT © 2026 David Batista. Code of Conduct.
Same package, two doors. MCP registers tools on stdio/HTTP. The skill can drive the same tools through the CLI when the client has no MCP:
npx -y delx-memory call memory_connection_status --json '{}'
Copy skill/SKILL.md into your agent skills dir.
Local-first persistent memory MCP: shared SQLite key/value store, searchable, TTL-aware, secret-safe
{ "mcpServers": { "io.github.davidmosiah-delx-memory": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "DELX_MEMORY_PATH": "<value>", "DELX_MEMORY_TRANSPORT": "<value>", "DELX_MEMORY_HOST": "<value>", "DELX_MEMORY_PORT": "<value>", "DELX_MEMORY_ALLOWED_ORIGIN": "<value>" } } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
發布者列出了以下環境變數:DELX_MEMORY_PATH, DELX_MEMORY_TRANSPORT, DELX_MEMORY_HOST, DELX_MEMORY_PORT, DELX_MEMORY_ALLOWED_ORIGIN。
Delx Memory 透過 stdio 在本機執行。
上次檢查時間:2026-11-09。 Local-first persistent memory MCP: shared SQLite key/value store, searchable, TTL-aware, secret-safe