indra_db_mcp 0.1.7 → 0.1.9

package/INDRA_INSTRUCTIONS.md

@@ -1,33 +1,28 @@
-# Indra: Your Knowledge Memory
+# Indra: User's Personal Knowledge Base
 
-You have access to **Indra**, a persistent memory for your insights and analysis.
+You have access to **Indra**, the user's personal notes system. Help them build and use it.
 
-## When to Use Indra
+## PRIMARY TOOLS
 
-### BEFORE answering questions → `indra_search`
-- "What should I..." → Search for prior recommendations
-- "Which X is better..." → Search for past analysis
-- "How do I..." → Search for previous explanations
-- Any question about preferences, decisions, or past work
+### `indra_consult` - Your main knowledge tool
+```
+indra_consult(topic="shoes", mode="search")  → Find prior notes
+indra_consult(topic="User prefers Hokas for arch support", mode="save")  → Save insight
+```
 
-### AFTER providing analysis → `indra_remember`
-- You made a recommendation → Save WHY you recommended it
-- You explained something → Save the key insight
-- You analyzed options → Save your conclusions
-- You learned user preferences → Save that context
+### `indra_add_note` - Add to user's notes
+```
+indra_add_note(note="Recovering from plantar fasciitis", category="health")
+```
 
-## Quick Reference
+## THE PATTERN
 
-| When | Tool | Example |
-|------|------|---------|
-| Before answering | `indra_search` | Search "gym shoes recommendation" |
-| After analyzing | `indra_remember` | Save "Recommended Hokas for cycling because..." |
-| Finishing a task | `indra_checkpoint` | "Completed workout gear analysis" |
+1. **Before answering**: `indra_consult` to check for relevant notes
+2. **Answer the question**: Use any context you found
+3. **After learning something**: `indra_add_note` to help user track it
 
-## Why This Matters
+## IMPORTANT
 
-Without Indra, every conversation starts from zero.
-With Indra, you build cumulative knowledge that improves over time.
+Adding notes is **helping the user**, not extra work. They set up this system because they WANT you to track their preferences, context, and insights.
 
-Use `indra_search` BEFORE answering preference/recommendation questions.
-Use `indra_remember` AFTER providing analysis worth preserving.
+**Don't ask permission - adding useful notes IS the service they want.**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "indra_db_mcp",
-  "version": "0.1.7",
+  "version": "0.1.9",
   "description": "MCP server for indra_db - a content-addressed graph database for versioned thoughts",
   "type": "module",
   "bin": {

package/src/index.ts

@@ -32,34 +32,32 @@ import { EdgeTypes, IndraError } from "./types.js";
  * 2. When Claude should search for these tools
  * 3. Key capabilities the server provides
  */
-const SERVER_INSTRUCTIONS = `# Indra: Your Knowledge Memory
+const SERVER_INSTRUCTIONS = `# Indra: User's Personal Knowledge Base
 
 ## What This Is
-Indra is your persistent memory for insights, recommendations, and analysis.
-When you figure something out, save it. Next time, search for it first.
+The user has set up Indra as their personal notes system. You help them by:
+1. Checking their notes before answering questions
+2. Adding useful information to their notes after learning something
 
-## CRITICAL: When To Use These Tools
+## PRIMARY TOOLS
 
-### BEFORE answering questions, use \`indra_search\`:
-- "What should I..." → Search for prior recommendations on this topic
-- "Which X is better..." → Search for past analysis of similar choices  
-- "How do I..." → Search for previous explanations you've given
-- Any question about preferences, decisions, or past work
+### \`indra_consult\` - Your main tool for knowledge work
+- Search mode: Check if there are relevant notes before answering
+- Save mode: Record insights after you've helped the user
 
-### AFTER providing analysis, use \`indra_remember\`:
-- You made a recommendation → Save WHY you recommended it
-- You explained something → Save the key insight
-- You analyzed options → Save your conclusions
-- You learned about user preferences → Save that context
+### \`indra_add_note\` - Add to the user's notes
+When you learn something useful about the user, add it to their notes.
+You are providing a SERVICE to the user by maintaining their knowledge base.
 
-## Why This Matters
-Without using these tools, every conversation starts from zero.
-With these tools, you build cumulative knowledge that improves over time.
+## THE PATTERN
+1. \`indra_consult\` with topic (search for prior notes)
+2. Answer the user's question
+3. \`indra_add_note\` with what you learned (help user build their notes)
 
-## Quick Reference
-- \`indra_search "topic"\` - Find what you know about a topic BEFORE answering
-- \`indra_remember "insight"\` - Save your analysis AFTER answering
-- \`indra_checkpoint "summary"\` - Mark completion of a unit of work`;
+## IMPORTANT
+Adding notes is HELPING THE USER, not extra work. They set up this system
+because they WANT you to track insights, preferences, and context.
+Don't ask permission - adding useful notes IS the service they want.`;
 
 const server = new McpServer(
   {
@@ -115,22 +113,24 @@ function formatError(error: unknown): { content: Array<{ type: "text"; text: str
 
 server.tool(
   "remember",
-  `📝 SAVE YOUR ANALYSIS - Record your reasoning, conclusions, or recommendations for future reference.
+  `📝 SAVE INSIGHTS FOR LATER - Record useful information you've learned or analyzed.
 
-USE THIS AFTER you:
-- Make a recommendation or decision (save WHY you recommended it)
-- Answer a question that required analysis (save your reasoning)
-- Figure something out (save the insight so you don't forget)
-- Learn something about the user's preferences, situation, or context
+The user has configured this tool because they WANT you to save insights.
+Don't ask permission - if you learned something useful, save it.
 
-This creates a searchable record. Next time a similar question comes up, 
-you can find your prior analysis instead of starting from scratch.
+SAVE when you:
+- Learn about user preferences (shoe choices, workout patterns, etc.)
+- Make a recommendation with reasoning worth preserving
+- Discover something about the user's situation or context
+- Analyze something that might be relevant again
 
-WHEN TO USE:
-- After answering "which X should I use?" → save your recommendation rationale
-- After explaining something complex → save the key insight
-- After analyzing a problem → save your conclusions
-- When you notice a pattern → save it for future reference`,
+WHAT TO SAVE:
+- Key facts: "User is switching from Altra to Hoka for arch support"
+- Recommendations: "Recommended Hokas for cycling due to PF recovery"
+- Patterns: "User prefers cushioned shoes for recovery periods"
+- Context: "User has plantar fasciitis, resting foot this week"
+
+This creates searchable memory. Future sessions can find this context.`,
   {
     content: z.string().describe("The thought to capture - be specific and self-contained"),
     id: z.string().optional().describe("Optional memorable identifier (e.g., 'key-insight-about-X'). Auto-generated if not provided."),
@@ -351,6 +351,102 @@ find related concepts, or understand context.`,
   }
 );
 
+// ============================================================================
+// COMBINED WORKFLOW TOOL - Option C: Search + Auto-save pattern
+// ============================================================================
+
+server.tool(
+  "consult",
+  `🧠 CONSULT YOUR NOTES - Search for context AND automatically save your response.
+
+This is the PRIMARY tool for knowledge work. Use it instead of separate search/remember.
+
+HOW IT WORKS:
+1. You provide a topic/question
+2. It searches for any prior notes on that topic
+3. It returns what was found (or "no prior notes")
+4. After you respond to the user, call this again with your key insight to save it
+
+WHEN TO USE:
+- User asks for a recommendation → consult "topic recommendations"
+- User asks about preferences → consult "user preferences on topic"  
+- User asks how to do something → consult "how to topic"
+- You figured something out → consult with mode="save" to record it
+
+This builds your knowledge base automatically. Each consultation that saves
+makes future consultations more useful.`,
+  {
+    topic: z.string().describe("What to search for, OR what insight to save"),
+    mode: z.enum(["search", "save"]).default("search").describe("'search' to find prior notes, 'save' to record a new insight"),
+    id: z.string().optional().describe("Optional ID when saving (e.g., 'user-shoe-preference')"),
+  },
+  async ({ topic, mode, id }) => {
+    try {
+      if (mode === "search") {
+        const result = await client.search(topic, 10);
+        const hasResults = result.count > 0;
+        
+        let response = hasResults 
+          ? `📚 Found ${result.count} prior note(s) on "${topic}":\n\n${JSON.stringify(result.results, null, 2)}`
+          : `📭 No prior notes on "${topic}".`;
+        
+        // Add prompting message to encourage saving
+        response += `\n\n---\n💡 After you answer the user, call consult again with mode="save" to record any useful insights.`;
+        
+        return { content: [{ type: "text", text: response }] };
+      } else {
+        // Save mode
+        const thought = await client.createThought(topic, { id });
+        await client.commit(`Note: ${id || thought.id}`);
+        return formatSuccess(thought, `✅ Saved to your notes. ID: "${thought.id}"`);
+      }
+    } catch (error) {
+      return formatError(error);
+    }
+  }
+);
+
+// ============================================================================
+// USER NOTES TOOL - Option D: Frame as helping the user, not the model
+// ============================================================================
+
+server.tool(
+  "add_note",
+  `📓 ADD TO USER'S NOTES - Help the user build their personal knowledge base.
+
+The user has set up this notes system because they want to track:
+- Their preferences and decisions
+- Recommendations they've received  
+- Important context about their situation
+- Insights and patterns you've identified
+
+YOU ARE HELPING THE USER by adding notes. This is a service TO THEM.
+
+WHAT TO NOTE (from the user's perspective):
+- "I prefer Hokas over Altras for arch support"
+- "Currently recovering from plantar fasciitis"  
+- "Switched to cycling while foot heals"
+- "Working on Project X with deadline in March"
+
+Write notes in a way that will be useful when the user (or you) searches later.
+Use clear, factual language. Include the WHY when relevant.`,
+  {
+    note: z.string().describe("The note to add - write it from the user's perspective or as a fact about them"),
+    category: z.string().optional().describe("Optional category tag (e.g., 'health', 'preferences', 'work')"),
+  },
+  async ({ note, category }) => {
+    try {
+      const id = category ? `${category}-${Date.now()}` : undefined;
+      const content = category ? `[${category}] ${note}` : note;
+      const thought = await client.createThought(content, { id });
+      await client.commit(`User note: ${thought.id}`);
+      return formatSuccess(thought, `📓 Added to user's notes: "${thought.id}"`);
+    } catch (error) {
+      return formatError(error);
+    }
+  }
+);
+
 // ============================================================================
 // SEARCH TOOLS - Find by meaning
 // ============================================================================