@danielsimonjr/memory-mcp 12.7.0 → 12.7.1

package/dist/index.js

@@ -31,8 +31,14 @@ process.stdin.on("close", shutdown);
 async function main() {
     // Initialize memory file path with backward compatibility
     const memoryFilePath = await ensureMemoryFilePath();
-    // Initialize manager context with the memory file path
-    managerContext = new ManagerContext(memoryFilePath);
+    // Honour MEMORY_STORAGE_TYPE. Passing a bare string here selects memoryjs's default
+    // (jsonl) backend unconditionally, so `MEMORY_STORAGE_TYPE=sqlite` was documented but
+    // silently ignored — and `diag` reported it as sqlite while writes went to memory.jsonl.
+    const storageType = process.env.MEMORY_STORAGE_TYPE === "sqlite" ? "sqlite" : "jsonl";
+    managerContext = new ManagerContext({
+        storagePath: memoryFilePath,
+        storageType,
+    });
     // Initialize and start MCP server
     const server = new MCPServer(managerContext);
     await server.start();

package/dist/server/toolHandlers.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"toolHandlers.d.ts","sourceRoot":"","sources":["../../src/server/toolHandlers.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAGH,OAAO,EACL,kBAAkB,EA2ClB,KAAK,cAAc,EAyBpB,MAAM,yBAAyB,CAAC;AAyBjC,wBAAgB,qBAAqB,CAAC,GAAG,EAAE,cAAc,GAAG,MAAM,GAAG,SAAS,CAE7E;AAkED;;;GAGG;AACH,MAAM,MAAM,YAAY,GAAG,UAAU,CAAC,OAAO,kBAAkB,CAAC,GAAG;IAAE,OAAO,CAAC,EAAE,OAAO,CAAA;CAAE,CAAC;AAEzF;;GAEG;AACH,MAAM,MAAM,WAAW,GAAG,CACxB,GAAG,EAAE,cAAc,EACnB,IAAI,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,KAC1B,OAAO,CAAC,YAAY,CAAC,CAAC;AAiF3B,eAAO,MAAM,YAAY,EAAE,MAAM,CAAC,MAAM,EAAE,WAAW,CAouGpD,CAAC;AAEF;;;;;;;GAOG;AACH,wBAAsB,cAAc,CAClC,IAAI,EAAE,MAAM,EACZ,IAAI,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAC7B,GAAG,EAAE,cAAc,GAClB,OAAO,CAAC,YAAY,CAAC,CAiBvB"}
+{"version":3,"file":"toolHandlers.d.ts","sourceRoot":"","sources":["../../src/server/toolHandlers.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAGH,OAAO,EACL,kBAAkB,EA2ClB,KAAK,cAAc,EAyBpB,MAAM,yBAAyB,CAAC;AAyBjC,wBAAgB,qBAAqB,CAAC,GAAG,EAAE,cAAc,GAAG,MAAM,GAAG,SAAS,CAE7E;AAgFD;;;GAGG;AACH,MAAM,MAAM,YAAY,GAAG,UAAU,CAAC,OAAO,kBAAkB,CAAC,GAAG;IAAE,OAAO,CAAC,EAAE,OAAO,CAAA;CAAE,CAAC;AAEzF;;GAEG;AACH,MAAM,MAAM,WAAW,GAAG,CACxB,GAAG,EAAE,cAAc,EACnB,IAAI,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,KAC1B,OAAO,CAAC,YAAY,CAAC,CAAC;AAiF3B,eAAO,MAAM,YAAY,EAAE,MAAM,CAAC,MAAM,EAAE,WAAW,CAuuGpD,CAAC;AAEF;;;;;;;GAOG;AACH,wBAAsB,cAAc,CAClC,IAAI,EAAE,MAAM,EACZ,IAAI,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAC7B,GAAG,EAAE,cAAc,GAClB,OAAO,CAAC,YAAY,CAAC,CAiBvB"}

package/dist/server/toolHandlers.js

@@ -37,7 +37,19 @@ function getStorageFilePath(ctx) {
     // type-cast). Older versions of this helper looked for `filePath` and
     // silently fell back to 'memory.jsonl' — which made diag / size / reindex
     // reports point at the wrong file. Try both field names defensively.
+    // SQLiteStorage exposes NEITHER field — it has a public `getFilePath()` accessor backed by
+    // `validatedDbFilePath`. Without this branch the helper fell through to the literal
+    // 'memory.jsonl', which resolves against cwd: diag then stat'd an unrelated file and reported
+    // it as your store (`exists: true` with that file's size) while writes went to memory.db.
     const storage = ctx.storage;
+    if (typeof storage.getFilePath === 'function') {
+        try {
+            const resolved = storage.getFilePath();
+            if (resolved)
+                return resolved;
+        }
+        catch { /* fall through to the field lookups below */ }
+    }
     return storage.memoryFilePath ?? storage.filePath ?? 'memory.jsonl';
 }
 // Sidecar path for the serialized Cue–Tag–Content graph, following the
@@ -2455,7 +2467,10 @@ export const toolHandlers = {
             runtime: { node: process.version, platform: process.platform, arch: process.arch, pid: process.pid },
             storage: {
                 path: storagePath,
-                type: process.env.MEMORY_STORAGE_TYPE ?? 'jsonl',
+                // Mirror index.ts's normalization exactly. Echoing the raw env var made diag report
+                // whatever was set (e.g. a typo, or 'sqlite' back when it was ignored) rather than the
+                // backend actually in use — a diagnostic that confirmed the bug instead of exposing it.
+                type: process.env.MEMORY_STORAGE_TYPE === 'sqlite' ? 'sqlite' : 'jsonl',
                 exists,
                 sizeBytes,
                 entities: stats.totalEntities,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@danielsimonjr/memory-mcp",
-  "version": "12.7.0",
+  "version": "12.7.1",
   "description": "Enhanced MCP memory server with hierarchies, compression, archiving, graph algorithms, semantic search, temporal KG, RBAC, bitemporal validity, OCC, procedural memory, causal reasoning, world model, do_not_remember exclusions, decision rationale, project context, heuristic guidelines, tool affordance + observer, observation dedup, spell correction, event memory, reconstructive memory, relation consolidation, agent reflection, and 241 advanced tools",
   "license": "MIT",
   "engines": {
@@ -59,7 +59,7 @@
   },
   "dependencies": {
     "@danielsimonjr/memoryjs": "^3.0.0",
-    "@modelcontextprotocol/sdk": "^1.21.1",
+    "@modelcontextprotocol/sdk": "^1.30.0",
     "zod": "^4.4.3"
   },
   "overrides": {
@@ -68,6 +68,7 @@
   "devDependencies": {
     "@types/node": "^26",
     "@vitest/coverage-v8": "^4.1.10",
+    "esbuild": "^0.28.1",
     "shx": "^0.4.0",
     "typescript": "^7.0.2",
     "vitest": "^4.1.5"