@torqon/mcp 0.2.4 → 0.2.6

package/dist/index.js

@@ -75,19 +75,38 @@ function hasSignal(text) {
     const words = text.trim().split(/\s+/).filter(w => w.length > 2);
     return words.length >= 3;
 }
+// ── Fetch user's stored facts at startup ────────────────────────────────────
+// Facts are embedded directly in the server instructions, so Claude has them
+// in every conversation without needing to call any tool first.
+let userFactsBlock = '';
+if (API_KEY) {
+    try {
+        const res = await fetch(`${API_URL}/api/v1/memory`, { headers });
+        if (res.ok) {
+            const data = await res.json();
+            const facts = data?.results ?? [];
+            if (facts.length > 0) {
+                const lines = facts
+                    .map((f) => f.metadata?.type ? `- ${f.metadata.type}: ${f.content}` : `- ${f.content}`)
+                    .join('\n');
+                userFactsBlock = `\n<USER_MEMORY>\nThese are verified facts from the user's previous sessions. Treat as ground truth.\n${lines}\n</USER_MEMORY>`;
+                process.stderr.write(`[Torqon] Loaded ${facts.length} facts into context.\n`);
+            }
+        }
+    }
+    catch {
+        process.stderr.write('[Torqon] Could not fetch user memory at startup.\n');
+    }
+}
 // ── MCP Server ───────────────────────────────────────────────────────────────
-const server = new McpServer({ name: 'torqon', version: '0.2.4' }, {
-    instructions: `Torqon persistent memory is active for this conversation.
-
-RULE: Call auto_process with the full user message BEFORE you respond to anything — every message, no exceptions, including greetings and one-word replies. It runs in under 200ms and simultaneously stores new facts AND retrieves relevant memory.
+const server = new McpServer({ name: 'torqon', version: '0.2.6' }, {
+    instructions: `Torqon persistent memory is active.${userFactsBlock}
 
-After auto_process returns:
-- If it returns "[Torqon memory]" facts, treat them as ground truth. Use exact stored values (names, decisions, stack choices, numbers).
-- If it returns "No relevant memory found", answer normally.
+When the user shares new facts (name, project, decision, tech stack, deadline, preference), call store_memory to save them.
+When you need to look up something specific from memory, call retrieve_context.
+Call auto_process when the user sends a long message with project context worth storing and retrieving simultaneously.
 
-Also call store_memory explicitly whenever the user shares their name, a project name, a key decision, a tech stack choice, a deadline, a constraint, or a preference. auto_process stores automatically but store_memory is for high-value facts you want confirmed saved.
-
-Session ID: ${SESSION_ID}`,
+Session: ${SESSION_ID}`,
 });
 // Live memory loader — user runs /torqon_context once at conversation start.
 // Fetches all stored facts from the API and injects them directly into the prompt.

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@torqon/mcp",
-    "version": "0.2.4",
+    "version": "0.2.6",
     "type": "module",
     "main": "dist/index.js",
     "bin": {