claude-memory-store 0.1.0 → 0.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +18 -19
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -81,7 +81,7 @@ The full memory dump is only loaded when you explicitly ask for it (`?` at the s
81
81
 
82
82
  ### Prerequisites
83
83
  - Node.js 18+
84
- - MongoDB Atlas account ([free tier works](https://cloud.mongodb.com/register) — no credit card required)
84
+ - MongoDB Atlas M10+ cluster ([create account](https://cloud.mongodb.com/register))required for vector search
85
85
 
86
86
  ### Install
87
87
 
@@ -93,7 +93,7 @@ That single command:
93
93
  1. Prompts for your Atlas connection string (auto-detects from `CLAUDE_MEMORY_ATLAS_URI` env var or `.env` file)
94
94
  2. Tests the connection
95
95
  3. Creates the `claude_memory` database and indexes
96
- 4. Sets up Atlas vector search index (M10+ only, skipped gracefully on free tier)
96
+ 4. Sets up Atlas vector search index (requires M10+)
97
97
  5. Installs Claude Code hooks (startup, pre-tool-use, post-tool-use, stop)
98
98
  6. Registers the MCP server (recall, remember, threads, stats tools)
99
99
  7. Installs the skill file (`/recall`, `/remember`, `/threads`, `/stats`)
@@ -135,7 +135,7 @@ claude-memory clear --all # Clear all project memory
135
135
 
136
136
  | Tool | Description |
137
137
  |------|-------------|
138
- | `recall(topic, limit?)` | Search memory via semantic + keyword search |
138
+ | `recall(topic, limit?)` | Search memory via semantic vector search |
139
139
  | `remember(text, category?)` | Store with auto-classification (avoid/pattern/architecture/preference) |
140
140
  | `memory_threads()` | List open threads with status and age |
141
141
  | `memory_stats()` | Full memory statistics |
@@ -270,27 +270,26 @@ You can also set `CLAUDE_MEMORY_ATLAS_URI` as an environment variable or in a `.
270
270
 
271
271
  ---
272
272
 
273
- ## Atlas Tier Comparison
273
+ ## Why Atlas M10+?
274
274
 
275
- Claude Memory works on all Atlas tiers. The difference is search precision:
275
+ Claude Memory requires **MongoDB Atlas M10+** ($57/month) for vector search. This is a deliberate choice — not a limitation.
276
276
 
277
- | Feature | Free Tier (M0) | M10+ |
278
- |---------|---------------|------|
279
- | Store/recall memory | Yes | Yes |
280
- | Hooks (startup, pre/post-tool-use, stop) | Yes | Yes |
281
- | MCP tools (recall, remember, threads, stats) | Yes | Yes |
282
- | Keyword search (regex matching) | Yes | Yes |
283
- | TTL with renewal | Yes | Yes |
284
- | Verified commands with aliases | Yes | Yes |
285
- | Open threads | Yes | Yes |
286
- | **Semantic vector search** | No | **Yes** |
287
- | **Atlas Automated Embedding (Voyage AI)** | No | **Yes** |
277
+ We tested keyword/regex search (which works on the free tier) against semantic vector search with real developer queries. The results:
288
278
 
289
- **Free tier** uses keyword search your query terms need to match the words in stored memories. Works well when you search with the same terms you used when storing.
279
+ | Query Type | Keyword Search | Vector Search |
280
+ |------------|---------------|---------------|
281
+ | Exact matches ("prod-cluster-east") | 80% | 80% |
282
+ | Partial matches ("staging database") | 100% | 100% |
283
+ | Synonym queries ("how to undo a release") | **0%** | **60%** |
284
+ | Conceptual queries ("security best practices") | **0%** | **80%** |
285
+ | Natural questions ("what region is our database in") | **0%** | **100%** |
286
+ | **Overall** | **36%** | **84%** |
290
287
 
291
- **M10+** adds semantic vector search via Voyage AI auto-embedding. Atlas automatically generates and maintains vector embeddings for every document. This means "what's our production database?" finds "MongoDB Atlas prod-cluster-east with database api_prod" even though the words don't overlap.
288
+ Keyword search fails completely when you phrase things differently from how they were stored. That's how humans talk. A memory store that can't understand "how do I deploy" when you stored "docker build ECR push webhook" is useless.
292
289
 
293
- **Recommendation:** Start with the free tier. It's fully functional. Upgrade to M10+ if you find keyword search isn't precise enough for your workflow.
290
+ **$57/month is cheaper than re-explaining your deploy process every session.**
291
+
292
+ Vector embeddings are generated locally via [all-MiniLM-L6-v2](https://huggingface.co/sentence-transformers/all-MiniLM-L6-v2) (384 dimensions) — no external API keys, no per-query fees. Atlas just stores and searches the vectors.
294
293
 
295
294
  ---
296
295
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "claude-memory-store",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "description": "Persistent memory for Claude Code. Powered by MongoDB Atlas.",
5
5
  "homepage": "https://claude-memory.com",
6
6
  "repository": {