@mnemoverse/mcp-memory-server 0.14.1 → 0.14.2

package/dist/index.js

@@ -343,7 +343,7 @@ registerMemoryResources(server, { apiFetch });
  * lists all twelve tools, and writes nothing to stderr — the 401 only appears
  * mid-conversation, on the first real tool call. A user who mistyped the key
  * sees a green connection and later reads the silent failure as "the product
- * does not work" (Olya's assistant, 2026-08-16).
+ * does not work" (a user's assistant, 2026-08-16).
  *
  * So: if a key IS configured, verify it once at startup with the cheapest
  * authenticated call and put the verdict on stderr, which MCP clients surface

package/dist/tools.js

@@ -1837,7 +1837,7 @@ export function registerMemoryTools(server, deps) {
                 .string()
                 .min(CORE_LIMITS.roomName.minLength)
                 .max(CORE_LIMITS.roomName.maxLength)
-                .describe("Room name, unique within your account (e.g. 'me-and-olya')."),
+                .describe("Room name, unique within your account (e.g. 'launch-team')."),
             description: z
                 .string()
                 .max(CORE_LIMITS.roomDescription.maxLength)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mnemoverse/mcp-memory-server",
-  "version": "0.14.1",
+  "version": "0.14.2",
   "description": "Hosted AI agent memory over MCP that learns from outcomes — feedback re-ranks recall — with shared rooms for multi-agent work; one key or OAuth across Claude Code, Cursor, VS Code & ChatGPT, no infra to run",
   "type": "module",
   "bin": {

package/tools.json

@@ -1,7 +1,7 @@
 {
   "$comment": "generated by scripts/generate-tools-manifest.mjs from the built server; do not edit",
   "name": "@mnemoverse/mcp-memory-server",
-  "version": "0.14.1",
+  "version": "0.14.2",
   "count": 11,
   "tools": [
     {