wontopos-mcp 1.0.5 → 1.0.7

package/index.mjs

@@ -27,15 +27,26 @@ import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
 import { z } from "zod";
 import { Client, WosError } from "wontopos";
+import { createRequire } from "node:module";
 
-const VERSION = "1.0.5";
+// Read the version from package.json rather than restating it: a hand-kept copy
+// silently drifts (1.0.6 shipped announcing itself as "1.0.5" in the MCP
+// handshake, so hosts logged — and bug reports cited — the wrong build).
+const VERSION = createRequire(import.meta.url)("./package.json").version;
 const flag = (v) => ["1", "true", "yes"].includes((v ?? "").trim().toLowerCase());
 const READ_ONLY = flag(process.env.WONTOPOS_READ_ONLY);
 // Store pinning (default ON): every call goes to WONTOPOS_USER_ID and the tools
 // do not even expose a user_id argument — a prompt-injected or confused model
 // cannot reach a sibling store. Opt out per install with ALLOW_STORE_OVERRIDE.
 const ALLOW_STORE_OVERRIDE = flag(process.env.WONTOPOS_ALLOW_STORE_OVERRIDE);
-const STORE = process.env.WONTOPOS_USER_ID || "default";
+// Whether the store was CHOSEN or fallen back to. Worth tracking, because the
+// fallback is silent in the worst way: if WONTOPOS_USER_ID never reaches this
+// process (a typo in the host config, an --env that did not take), everything goes
+// to `default` — and since every account is seeded with a `default` store, the boot
+// check below SUCCEEDS, so nothing looks wrong while the configured store sits
+// untouched. Say it out loud instead.
+const STORE_FROM_ENV = (process.env.WONTOPOS_USER_ID || "").trim();
+const STORE = STORE_FROM_ENV || "default";
 // Cap what a tool result may inject into the model's context. The SDK's 64MB cap
 // protects the process; this protects the conversation (a 2MB memory must not
 // become 2MB of context). Measured in UTF-8 BYTES, not JS chars: `str.length`
@@ -54,6 +65,22 @@ function truncateToBytes(s, maxBytes) {
   return s.slice(0, read);
 }
 const UUID_RE = /^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$/i;
+const DATE_ONLY_RE = /^\d{4}-\d{2}-\d{2}$/;
+/** Canonicalize event_date to the full RFC3339 the API requires.
+ *  The API accepts only a complete date-TIME: a bare "2026-03-14" — the form a
+ *  model naturally emits, and the form this tool's own example suggested — came
+ *  back as an opaque 400 "Invalid request body or parameters." Normalize here
+ *  instead of asking every agent to guess the shape.
+ *  Returns null when the value is not a date at all, so the caller can refuse it.  */
+function normalizeEventDate(raw) {
+  const s = String(raw).trim();
+  if (Number.isNaN(Date.parse(s))) return null;
+  // Date-only is completed by string append, never through Date: parsing and
+  // re-serializing would re-interpret it in the host's zone and can shift the
+  // stated day by one, which is exactly the fact the user was pinning down.
+  if (DATE_ONLY_RE.test(s)) return `${s}T00:00:00Z`;
+  return new Date(s).toISOString();
+}
 
 // First env var with a NON-EMPTY value wins. `??` only skips null/undefined, so
 // an empty WONTOPOS_API_KEY="" would shadow a valid WOS_API_KEY — the exact bug
@@ -167,7 +194,10 @@ server.registerTool(
       "('Sunwoo prefers dark mode in the console'), not a chat log. For your own side, store only " +
       "commitments you actually SAID to the user (speaker 'me') — never internal reasoning or thinking " +
       "output. Do NOT store fetched material: web search results, crawled pages, file contents, and " +
-      "tool outputs are session context, not memories. Identical content is deduplicated (status 'duplicate').",
+      "tool outputs are session context, not memories. A memory close enough to one already stored is " +
+      "rejected as status 'duplicate' and is NOT saved — the match is by meaning, not by exact text, so " +
+      "when a new fact only narrows or contrasts an existing one ('allergic to shellfish' next to " +
+      "'allergic to peanuts'), write it as one sentence that states both, or supersede the old one with update.",
     inputSchema: {
       content: z.string().describe("The memory, as one self-contained sentence."),
       speaker: z
@@ -177,7 +207,7 @@ server.registerTool(
       event_date: z
         .string()
         .nullish()
-        .describe("RFC3339 date when the event actually happened, if different from now."),
+        .describe("When the event actually happened, if different from now. A plain date ('2026-03-14') or a full RFC3339 timestamp; a bare date is read as UTC midnight."),
       ...storeArg,
     },
   },
@@ -187,11 +217,12 @@ server.registerTool(
       throw new Error("content too long (max 8192 bytes) — a memory is one fact; backfill large text with the SDK's add_bulk.");
     if (speaker && speaker !== "me")
       throw new Error("speaker must be 'me' (something the agent itself said) or omitted (the user's fact).");
-    if (event_date && Number.isNaN(Date.parse(event_date)))
-      throw new Error("event_date is not a parseable date — use RFC3339, e.g. 2026-07-01.");
+    const eventDate = event_date ? normalizeEventDate(event_date) : null;
+    if (event_date && !eventDate)
+      throw new Error("event_date is not a parseable date — use a date (2026-07-01) or RFC3339 (2026-07-01T09:00:00Z).");
     const metadata = {};
     if (speaker) metadata.speaker = speaker;
-    if (event_date) metadata.event_date = event_date;
+    if (eventDate) metadata.event_date = eventDate;
     return mem.add(content, uid(user_id), metadata);
   })
 );
@@ -306,10 +337,24 @@ server.registerTool(
       "'deep_recall' searches then expands around the top match — thorough answer to one specific " +
       "question; 'timeline' returns memories ordered by when events happened — 'when did X', " +
       "histories; 'gather' expands around the top few matches — collect everything related to a " +
-      "topic. Heavier than search, so reach for it when recall/search came back thin or the user " +
-      "asks for a full picture.",
+      "topic; 'equilibrium' re-widens retrieval when a long session has narrowed it to whatever " +
+      "the current turn resembles — for replies that loop or flatten, not for a factual lookup; " +
+      "'tone_stabilizer' returns the assistant's OWN earlier words so it can come back to its " +
+      "usual register (needs turns stored with speaker \"me\"). " +
+      "Heavier than search, so reach for it when recall/search came back thin or the user asks " +
+      "for a full picture. Call the API's GET /api/v1/engram for the live catalogue.",
     inputSchema: {
-      name: z.enum(["deep_recall", "timeline", "gather"]),
+      // A plain string, NOT an enum: the enum was pinned to the original three, so
+      // every engram the service added afterwards was uncallable from here until
+      // this package was republished. The API validates the name and answers 400
+      // with the list it accepts, so an unknown name fails clearly and a new engram
+      // works the day it ships.
+      name: z
+        .string()
+        .min(1)
+        .describe(
+          "Engram name: deep_recall | timeline | gather | equilibrium | tone_stabilizer (the service is the authority; an unknown name returns the accepted list)."
+        ),
       query: z.string().describe("What to retrieve, phrased like the user's need."),
       ...storeArg,
     },
@@ -367,13 +412,26 @@ await server.connect(transport);
     return inner?.(msg, extra);
   };
 }
-console.error(`wontopos-mcp ${VERSION} ready (store: ${STORE}${READ_ONLY ? ", read-only" : ""})`);
+console.error(
+  `wontopos-mcp ${VERSION} ready (store: ${STORE}${STORE_FROM_ENV ? "" : " — FALLBACK: WONTOPOS_USER_ID is not set"}${READ_ONLY ? ", read-only" : ""})`
+);
 
 // Boot check (one metered stats call, after connect so host startup never waits):
 // "ready" above is a claim — verify it. A wrong key can do nothing → exit loudly.
 // A missing store is recoverable (the agent can create_store) → warn and serve.
 mem.stats().then(
-  (s) => console.error(`wontopos-mcp: store "${STORE}" verified (${s?.total_memories ?? "?"} memories).`),
+  (s) => {
+    console.error(`wontopos-mcp: store "${STORE}" verified (${s?.total_memories ?? "?"} memories).`);
+    // Verified, but on the fallback store — the case a misconfiguration hides in.
+    // The seeded `default` always exists, so this check passes and the operator has
+    // no other signal that the store they configured is not the one in use.
+    if (!STORE_FROM_ENV) {
+      console.error(
+        'wontopos-mcp: WONTOPOS_USER_ID is not set, so this server is using the seeded "default" store. ' +
+          "If you meant a different store, set WONTOPOS_USER_ID in the MCP server's env and restart."
+      );
+    }
+  },
   (e) => {
     const status = e instanceof WosError ? e.status : 0;
     if (status === 401) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wontopos-mcp",
-  "version": "1.0.5",
+  "version": "1.0.7",
   "mcpName": "com.wontopos/mcp",
   "description": "(beta) Wontopos (WOS) long-term memory as an MCP server — one memory across Claude Code, Claude Desktop, Cursor, ChatGPT, and your own agents.",
   "keywords": [
@@ -32,7 +32,7 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
-    "wontopos": "^2.2.13",
+    "wontopos": "^2.2.22",
     "zod": "^3.23.0"
   }
 }