@intangle/mcp-server 2.6.3 → 2.6.5

package/dist/index.js

@@ -258,9 +258,14 @@ try {
             contents: Array.isArray(result?.contents) ? result.contents : [],
         };
     });
-    server.setRequestHandler(ListResourceTemplatesRequestSchema, async () => ({
-        resourceTemplates: [],
-    }));
+    server.setRequestHandler(ListResourceTemplatesRequestSchema, async () => {
+        const result = await makeRemoteRpcCall("resources/templates/list", {});
+        return {
+            resourceTemplates: Array.isArray(result?.resourceTemplates)
+                ? result.resourceTemplates
+                : [],
+        };
+    });
     async function handleSearchContext(args) {
         const { space_id, query, topics, group_id, project_id, folder_id } = args;
         // Require space_id

package/dist/tool-definitions.js

@@ -495,7 +495,7 @@ const TOOL_DEFINITIONS = [
     {
         name: "update_memory",
         title: "Update Memory",
-        description: "Add, update, or delete items in a space. Supports any combination of operations in a single call.\n\nIMPORTANT: Include at least one operation: add, update, or delete.\n\nTIPS FOR RICH MEMORY: The more context you provide, the smarter the system becomes:\n- Include WHY something matters, not just WHAT it is\n- Note user preferences, patterns, and approaches you observe\n- Describe repeatable workflows as skills (step-by-step procedures)\n- Link related items using parent_id or linkedItemIds\n- Prefer updating an existing related memory when the new information refines or extends it instead of creating a duplicate\n- Use descriptive titles that capture the essence\n- Add context about decisions, reasoning, and outcomes\n\nUse project_id and group_id when you know the active project or group scope. The system learns from patterns - sharing how the user works helps it anticipate their needs.",
+        description: "Add, update, or delete items in a space. Supports any combination of operations in a single call.\n\nIMPORTANT: Include at least one operation: add, update, or delete.\n\nTIPS FOR RICH MEMORY: The more context you provide, the smarter the system becomes:\n- Include WHY something matters, not just WHAT it is\n- Note user preferences, patterns, and approaches you observe\n- Describe repeatable workflows as skills (step-by-step procedures)\n- Link related items using parent_id or linkedItemIds\n- Prefer updating an existing related memory when the new information refines or extends it instead of creating a duplicate\n- Use descriptive titles that capture the essence\n- Add context about decisions, reasoning, and outcomes\n- Every write should reassess the surrounding scope and improve organization when possible: prefer updating, merging, linking, reparenting, or retitling existing items over spraying disconnected new ones\n\nUse project_id and group_id when you know the active project or group scope. The system learns from patterns - sharing how the user works helps it anticipate their needs.",
         inputSchema: {
             type: "object",
             properties: {
@@ -566,7 +566,7 @@ const TOOL_DEFINITIONS = [
                                 },
                                 required: ["title", "content", "type"]
                             },
-                            description: "Array of items to add. ALWAYS pass 'type' field to skip auto-classification. System suggests 1-3 relevant topics based on content. Tasks can include subtasks array for hierarchical task management."
+                            description: "Array of items to add. ALWAYS pass 'type' field to skip auto-classification. System suggests 1-3 relevant topics based on content. Tasks can include subtasks array for hierarchical task management. Before adding, check whether updating, merging, linking, or reparenting an existing item would keep the touched scope cleaner."
                         }
                     }
                 },
@@ -632,7 +632,7 @@ const TOOL_DEFINITIONS = [
                                 },
                                 required: ["id"]
                             },
-                            description: "Array of items to update. Type automatically detected from ID prefix (mem_* = context, task_* = task, skill_* = skill). For context/skill items, status/priority/assignee are ignored."
+                            description: "Array of items to update. Type automatically detected from ID prefix (mem_* = context, task_* = task, skill_* = skill). For context/skill items, status/priority/assignee are ignored. Treat updates as a chance to improve title clarity, links, parent placement, deduplication, and overall organization of the touched scope."
                         }
                     }
                 },
@@ -725,17 +725,17 @@ const TOOL_DEFINITIONS = [
                 },
                 move_items: {
                     type: "array",
-                    description: "Optional item move operations. Set folder_id to null to move an item back to root.",
+                    description: "Optional item move operations. Omit folder_id to move an item back to root.",
                     items: {
                         type: "object",
                         properties: {
                             item_id: { type: "string", description: "Item ID to move." },
                             folder_id: {
-                                type: ["string", "null"],
-                                description: "Target folder ID, or null to remove from folder."
+                                type: "string",
+                                description: "Optional target folder ID. Omit this field to remove the item from its current folder."
                             }
                         },
-                        required: ["item_id", "folder_id"]
+                        required: ["item_id"]
                     }
                 },
                 delete: {

package/index.ts

@@ -343,9 +343,14 @@ try {
     }
   })
 
-  server.setRequestHandler(ListResourceTemplatesRequestSchema, async () => ({
-    resourceTemplates: [],
-  }))
+  server.setRequestHandler(ListResourceTemplatesRequestSchema, async () => {
+    const result = await makeRemoteRpcCall("resources/templates/list", {})
+    return {
+      resourceTemplates: Array.isArray(result?.resourceTemplates)
+        ? result.resourceTemplates
+        : [],
+    }
+  })
 
   async function handleSearchContext(args: any) {
     const { space_id, query, topics, group_id, project_id, folder_id } = args as {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@intangle/mcp-server",
-  "version": "2.6.3",
+  "version": "2.6.5",
   "description": "Model Context Protocol server for Intangle - AI context that persists across conversations",
   "main": "dist/index.js",
   "type": "module",

package/tool-definitions.ts

@@ -558,7 +558,7 @@ const TOOL_DEFINITIONS = [
     name: "update_memory",
     title: "Update Memory",
     description:
-      "Add, update, or delete items in a space. Supports any combination of operations in a single call.\n\nIMPORTANT: Include at least one operation: add, update, or delete.\n\nTIPS FOR RICH MEMORY: The more context you provide, the smarter the system becomes:\n- Include WHY something matters, not just WHAT it is\n- Note user preferences, patterns, and approaches you observe\n- Describe repeatable workflows as skills (step-by-step procedures)\n- Link related items using parent_id or linkedItemIds\n- Prefer updating an existing related memory when the new information refines or extends it instead of creating a duplicate\n- Use descriptive titles that capture the essence\n- Add context about decisions, reasoning, and outcomes\n\nUse project_id and group_id when you know the active project or group scope. The system learns from patterns - sharing how the user works helps it anticipate their needs.",
+      "Add, update, or delete items in a space. Supports any combination of operations in a single call.\n\nIMPORTANT: Include at least one operation: add, update, or delete.\n\nTIPS FOR RICH MEMORY: The more context you provide, the smarter the system becomes:\n- Include WHY something matters, not just WHAT it is\n- Note user preferences, patterns, and approaches you observe\n- Describe repeatable workflows as skills (step-by-step procedures)\n- Link related items using parent_id or linkedItemIds\n- Prefer updating an existing related memory when the new information refines or extends it instead of creating a duplicate\n- Use descriptive titles that capture the essence\n- Add context about decisions, reasoning, and outcomes\n- Every write should reassess the surrounding scope and improve organization when possible: prefer updating, merging, linking, reparenting, or retitling existing items over spraying disconnected new ones\n\nUse project_id and group_id when you know the active project or group scope. The system learns from patterns - sharing how the user works helps it anticipate their needs.",
     inputSchema: {
       type: "object",
       properties: {
@@ -641,7 +641,7 @@ const TOOL_DEFINITIONS = [
                 required: ["title", "content", "type"]
               },
               description:
-                "Array of items to add. ALWAYS pass 'type' field to skip auto-classification. System suggests 1-3 relevant topics based on content. Tasks can include subtasks array for hierarchical task management."
+                "Array of items to add. ALWAYS pass 'type' field to skip auto-classification. System suggests 1-3 relevant topics based on content. Tasks can include subtasks array for hierarchical task management. Before adding, check whether updating, merging, linking, or reparenting an existing item would keep the touched scope cleaner."
             }
           }
         },
@@ -713,7 +713,7 @@ const TOOL_DEFINITIONS = [
                 required: ["id"]
               },
               description:
-                "Array of items to update. Type automatically detected from ID prefix (mem_* = context, task_* = task, skill_* = skill). For context/skill items, status/priority/assignee are ignored."
+                "Array of items to update. Type automatically detected from ID prefix (mem_* = context, task_* = task, skill_* = skill). For context/skill items, status/priority/assignee are ignored. Treat updates as a chance to improve title clarity, links, parent placement, deduplication, and overall organization of the touched scope."
             }
           }
         },
@@ -812,17 +812,18 @@ const TOOL_DEFINITIONS = [
         move_items: {
           type: "array",
           description:
-            "Optional item move operations. Set folder_id to null to move an item back to root.",
+            "Optional item move operations. Omit folder_id to move an item back to root.",
           items: {
             type: "object",
             properties: {
               item_id: { type: "string", description: "Item ID to move." },
               folder_id: {
-                type: ["string", "null"],
-                description: "Target folder ID, or null to remove from folder."
+                type: "string",
+                description:
+                  "Optional target folder ID. Omit this field to remove the item from its current folder."
               }
             },
-            required: ["item_id", "folder_id"]
+            required: ["item_id"]
           }
         },
         delete: {