@prom.codes/memory-mcp 0.7.1 → 0.7.2

package/README.md

@@ -7,45 +7,46 @@ procedures survive context-window resets. Records live in a local SQLite
 database (`~/.prometheus/memory.db`); project-scoped memories are mirrored
 as git-versioned markdown under `.prometheus/memories/` in your repo.
 
-## Quick start
-
-```jsonc
-// Claude Desktop / Cursor MCP config — dock under the server name `memory`
-// so the tools resolve to memory_read / memory_write / … (no double prefix).
-{
-  "mcpServers": {
-    "memory": {
-      "command": "npx",
-      "args": ["-y", "@prom.codes/memory-mcp@latest"],
-      "env": {
-        "PROMETHEUS_WORKSPACE_ROOT": "/absolute/path/to/your/repo",
-        "VOYAGE_API_KEY": "pa-…  // optional: enables semantic recall (search)"
-      }
-    }
-  }
-}
-```
+## Quick start (Claude Code)
 
-No API key is required to start: the server boots in keyword mode out of the
-box. Add a `VOYAGE_API_KEY` for semantic search (embeddings run Voyage-direct,
-fully local — only the memory text transits to Voyage), or a `prom_live_…`
-`PROMETHEUS_API_KEY` to route embeddings through the metered Prometheus proxy.
+```bash
+claude mcp add memory --env PROMETHEUS_API_KEY=prom_live_… -- npx -y @prom.codes/memory-mcp@latest
+```
 
-Then ask your agent to run `memory_setup` once per workspace — it installs
-the memory protocol into your runtime rule files (CLAUDE.md, .cursor/rules,
-.augment/rules or AGENTS.md) so the agent reads memory at session start and
-captures learnings at session end.
+Docks under the server name `memory`, so tools resolve to `memory_read` /
+`memory_write` / … `claude mcp add` defaults to local scope; add
+`--scope project` for a committable `.mcp.json`. Other hosts (Cursor, VS Code)
+use the same command/args in their own config.
+
+Then ask your agent to run `memory_setup` once per workspace — it installs the
+memory protocol into your runtime rule files (CLAUDE.md, .cursor/rules,
+AGENTS.md) so the agent reads memory at session start and captures learnings at
+session end.
+
+## Configuration
+
+- **Works with no key at all** — boots keyword-only (FTS5) and fully offline. A
+  `PROMETHEUS_API_KEY` (real `prom_live_<tag>_<secret>` from
+  [app.prom.codes/app/api-keys](https://app.prom.codes)) adds **semantic** recall
+  via the managed proxy — the same one key as Context and Saver.
+- **Workspace root is auto-detected** (Claude Code `CLAUDE_PROJECT_DIR` / MCP
+  `roots`) — no need to set `PROMETHEUS_WORKSPACE_ROOT`.
+- **Optional quality levers** (documented): `PROMETHEUS_MEMORY_RERANK_PROVIDER`
+  (cross-encoder rerank — reranked recall ties full-context at ~28× fewer tokens
+  on LoCoMo) and `PROMETHEUS_MEMORY_REWRITE_PROVIDER` (HyDE). Temporal-intent
+  ranking ("latest/earliest" queries) is **on by default**; disable with
+  `PROMETHEUS_MEMORY_TEMPORAL=off`.
 
 Tools (docked as `memory`): `memory_read`, `memory_write`, `memory_capture`,
 `memory_search`, `memory_list`, `memory_delete`, `memory_setup`. Secrets are
-rejected on every write. Your memories never leave your machine.
+rejected on every write. Your memories never leave your machine (only short
+query/record text transits when embeddings are enabled).
 
 ## Native modules
 
 Uses `better-sqlite3` (native). Prebuilt binaries are fetched automatically on
 common platforms (macOS x64/arm64, Linux x64/arm64, Windows x64) — no compiler
 needed. On an unsupported platform/Node ABI, install C/C++ build tools so the
-module can compile (Windows: `npm i -g windows-build-tools` or VS Build Tools).
-Requires Node ≥ 20.10.
+module can compile (Windows: VS Build Tools). Requires Node ≥ 20.10.
 
-Docs: https://prom.codes/docs
+Docs: https://prom.codes/docs/mcp/memory

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prom.codes/memory-mcp",
-  "version": "0.7.1",
+  "version": "0.7.2",
   "description": "prom.codes Memory — persistent, local-first agent memory as an MCP server.",
   "type": "module",
   "bin": {