@kanbodev/mcp 1.1.3 → 1.1.5

package/README.md

@@ -116,6 +116,8 @@ The assistant respects your workflow transition rules — it checks which status
 > "Pull PROJ-78 back to the board and put it in To Do"
 >
 > "Show me the backlog for the mobile project"
+>
+> "Restore the deleted ticket PROJ-99 and put it in the backlog"
 
 ### Comments and collaboration
 
@@ -164,6 +166,10 @@ Batch operations work on up to 50 tickets at once.
 > "Make this description clearer: ..."
 >
 > "Check if this title is clear enough: 'fix thing'"
+>
+> "Create a ticket from my notes: users need to be able to export reports as PDF, it should respect filters, and show a progress bar for large exports"
+
+The last example passes your raw notes directly to `generate_description` — the AI organizes, structures, and expands them into a full ticket description rather than generating from scratch.
 
 ### Analytics and reporting
 

package/dist/index.js

@@ -16839,7 +16839,7 @@ var CONFIG = {
 };
 var SERVER_INFO = {
   name: "kanbo-mcp",
-  version: "1.1.3",
+  version: "1.1.5",
   description: "MCP server for Kanbo project management"
 };
 var PAT_CONFIG = {
@@ -24657,8 +24657,8 @@ KanboClient.prototype.reviveTicket = async function(projectId, ticketId, destina
 KanboClient.prototype.deleteTicket = async function(projectId, ticketId) {
   return this.delete(EP.TICKETS.GET(projectId, ticketId));
 };
-KanboClient.prototype.restoreTicket = async function(projectId, ticketId) {
-  return this.post(EP.TICKETS.RESTORE(projectId, ticketId));
+KanboClient.prototype.restoreTicket = async function(projectId, ticketId, location) {
+  return this.post(EP.TICKETS.RESTORE(projectId, ticketId), location ? { location } : {});
 };
 KanboClient.prototype.moveToBacklog = async function(projectId, ticketId) {
   return this.post(EP.TICKETS.BACKLOG(projectId, ticketId));
@@ -24914,8 +24914,8 @@ KanboClient.prototype.getMemberProfile = async function(userId) {
 KanboClient.prototype.polishTitle = async function(title, projectId) {
   return this.post(EP.AI.POLISH_TITLE, { title, projectId });
 };
-KanboClient.prototype.generateDescription = async function(title, projectId, releaseId) {
-  return this.post(EP.AI.GENERATE_DESCRIPTION, { title, projectId, releaseId });
+KanboClient.prototype.generateDescription = async function(title, projectId, releaseId, userNotes) {
+  return this.post(EP.AI.GENERATE_DESCRIPTION, { title, projectId, releaseId, userNotes });
 };
 KanboClient.prototype.findSimilarTickets = async function(query, projectId, limit) {
   return this.post(EP.AI.SIMILAR_TICKETS, { query, projectId, limit });
@@ -25512,7 +25512,7 @@ Start with a <p> overview using user story format: "As a [role], I want [goal],
         },
         description: {
           type: "string",
-          description: `Ticket description as KanboEditor HTML (max ${LIMITS.DESCRIPTION_MAX} chars). Use <p> for paragraphs, <h2>/<h3> for section headings, <ul>/<ol>/<li> for lists, <strong> for emphasis, <code> for technical terms. Start with a <p> overview, then add structured sections per ticket type. Example: "<p>As a user, I want to <strong>export data</strong> in CSV format.</p><h2>Requirements</h2><ul><li>Support CSV and JSON formats</li><li>Show progress for large exports</li></ul><h2>Technical Notes</h2><ul><li>Use existing <code>/api/export</code> endpoint</li></ul>". Use generate_description to AI-generate this, or write manually following the structure in the tool description above.`
+          description: `Ticket description as KanboEditor HTML (max ${LIMITS.DESCRIPTION_MAX} chars). Use <p> for paragraphs, <h2>/<h3> for section headings, <ul>/<ol>/<li> for lists, <strong> for emphasis, <code> for technical terms. Start with a <p> overview, then add structured sections per ticket type. Do NOT embed acceptance criteria in the description — use the separate acceptanceCriteria field instead (it renders as a standalone interactive checklist widget below the description). TICKET REFERENCES: To mention/link other tickets, use <span data-ticket-key="PROJ-123" class="ticket-tag">PROJ-123</span> — the system auto-creates cross-references. Example: "<p>As a user, I want to <strong>export data</strong> in CSV format.</p><h2>Requirements</h2><ul><li>Support CSV and JSON formats</li><li>Show progress for large exports</li></ul><h2>Technical Notes</h2><ul><li>Use existing <code>/api/export</code> endpoint</li><li>Related to <span data-ticket-key="PROJ-42" class="ticket-tag">PROJ-42</span></li></ul>". Use generate_description to AI-generate this, or write manually following the structure in the tool description above.`
         },
         statusId: {
           type: "string",
@@ -25560,7 +25560,7 @@ Start with a <p> overview using user story format: "As a [role], I want [goal],
         },
         acceptanceCriteria: {
           type: "string",
-          description: `Acceptance criteria as JSON string of array (max ${LIMITS.ACCEPTANCE_CRITERIA_MAX} chars). Format: [{"id":"ac-1","text":"Given a user on X page, When they do Y, Then Z happens","isChecked":false}]. Use Given/When/Then format. Include 3-8 criteria. Use unique IDs (ac-1, ac-2). Set isChecked to false for new tickets.`
+          description: `Acceptance criteria as JSON string of array (max ${LIMITS.ACCEPTANCE_CRITERIA_MAX} chars). Renders as a standalone interactive checklist widget below the description — do NOT embed AC in the description HTML. Format: [{"id":"ac-1","text":"Given a user on X page, When they do Y, Then Z happens","isChecked":false}]. Use Given/When/Then format. Include 3-8 criteria. Use unique IDs (ac-1, ac-2). Set isChecked to false for new tickets.`
         },
         parentId: {
           type: "string",
@@ -25616,7 +25616,7 @@ var updateTicketTool = {
         },
         description: {
           type: "string",
-          description: `New description as KanboEditor HTML (max ${LIMITS.DESCRIPTION_MAX} chars). Use <p>, <h2>, <h3>, <ul>, <li>, <strong>, <code> tags. Structure with <h2> section headings per ticket type. Use refine_description to AI-refine an existing description based on feedback instead of rewriting manually.`
+          description: `New description as KanboEditor HTML (max ${LIMITS.DESCRIPTION_MAX} chars). Use <p>, <h2>, <h3>, <ul>, <li>, <strong>, <code> tags. Structure with <h2> section headings per ticket type. Do NOT embed acceptance criteria in the description — use the separate acceptanceCriteria field. TICKET REFERENCES: To mention other tickets, use <span data-ticket-key="PROJ-123" class="ticket-tag">PROJ-123</span>. Use refine_description to AI-refine an existing description based on feedback instead of rewriting manually.`
         },
         assigneeId: {
           type: ["string", "null"],
@@ -25654,7 +25654,7 @@ var updateTicketTool = {
         },
         acceptanceCriteria: {
           type: ["string", "null"],
-          description: `Acceptance criteria as JSON string of array (max ${LIMITS.ACCEPTANCE_CRITERIA_MAX} chars): [{"id":"ac-1","text":"Given... When... Then...","isChecked":false}], or null to clear. Preserve existing criteria IDs when updating.`
+          description: `Acceptance criteria as JSON string of array (max ${LIMITS.ACCEPTANCE_CRITERIA_MAX} chars): [{"id":"ac-1","text":"Given... When... Then...","isChecked":false}], or null to clear. Renders as a standalone interactive checklist widget below the description. Preserve existing criteria IDs when updating.`
         },
         parentId: {
           type: ["string", "null"],
@@ -25915,7 +25915,7 @@ var deleteTicketTool = {
 var restoreTicketTool = {
   tool: {
     name: "restore_ticket",
-    description: "Restore a soft-deleted ticket from trash back to its previous location.",
+    description: "Restore a soft-deleted ticket from trash back to the board, backlog, completed, or abandoned area. Defaults to the ticket's previous location if no location is specified.",
     inputSchema: {
       type: "object",
       properties: {
@@ -25926,6 +25926,11 @@ var restoreTicketTool = {
         ticketId: {
           type: "string",
           description: "Ticket ID to restore"
+        },
+        location: {
+          type: "string",
+          enum: ["board", "backlog", "completed", "abandoned"],
+          description: "Where to restore the ticket (optional — defaults to previous location)"
         }
       },
       required: ["projectId", "ticketId"]
@@ -25934,7 +25939,7 @@ var restoreTicketTool = {
   handler: async (args) => {
     try {
       const client = getKanboClient();
-      const response = await client.restoreTicket(args.projectId, args.ticketId);
+      const response = await client.restoreTicket(args.projectId, args.ticketId, args.location);
       return successResult(response.data);
     } catch (error2) {
       return errorResultFromError(error2);
@@ -28556,6 +28561,10 @@ The AI gathers project context automatically (related tickets, statuses, workflo
         releaseId: {
           type: "string",
           description: "Release ID for additional context — helps generate release-relevant descriptions (optional)"
+        },
+        userNotes: {
+          type: "string",
+          description: "Raw notes or brain dump from the user (max 5000 chars). When provided, the AI uses these as the primary source of intent — organizing, structuring, and expanding them rather than generating from scratch (optional)"
         }
       },
       required: ["title", "projectId"]
@@ -28564,7 +28573,7 @@ The AI gathers project context automatically (related tickets, statuses, workflo
   handler: async (args) => {
     try {
       const client = getKanboClient();
-      const response = await client.generateDescription(args.title, args.projectId, args.releaseId);
+      const response = await client.generateDescription(args.title, args.projectId, args.releaseId, args.userNotes);
       return successResult(response.data);
     } catch (error2) {
       return errorResultFromError(error2);
@@ -28574,7 +28583,7 @@ The AI gathers project context automatically (related tickets, statuses, workflo
 var findSimilarTicketsTool = {
   tool: {
     name: "find_similar_tickets",
-    description: "Semantic search for similar tickets. Use BEFORE creating a ticket to check for duplicates. Also useful for finding related work. Returns similarity scores.",
+    description: "Semantic search for similar tickets using vector similarity (cosine). Use cases: (1) BEFORE creating a ticket to check for duplicates, (2) find related work to a given ticket — pair with get_completed_tickets to discover closed tickets that addressed the same topic, (3) general discovery of thematically related tickets across the project. Returns results ranked by similarity score.",
     inputSchema: {
       type: "object",
       properties: {
@@ -29411,6 +29420,7 @@ var TOOL_INDEX = {
     },
     acceptance_criteria: {
       priority: 'HIGH — ALWAYS include acceptance criteria when creating tickets. This is the primary definition of "done".',
+      rendering: "AC renders as a standalone interactive checklist widget below the description. Just set the acceptanceCriteria field — do NOT embed AC in the description HTML.",
       format: 'JSON string of array: [{"id":"ac-1","text":"...","isChecked":false}]',
       rules: [
         "REQUIRED for every ticket — never skip acceptance criteria",
@@ -29419,14 +29429,26 @@ var TOOL_INDEX = {
         'For simpler criteria, use direct statements: "Users can export data in CSV format"',
         "Include at least one happy-path criterion and one error/edge-case criterion",
         'Each criterion must be verifiable — someone can clearly say "yes, met" or "no, not met"',
-        'Do NOT include vague criteria like "Code is clean" or "Feature works correctly"'
+        'Do NOT include vague criteria like "Code is clean" or "Feature works correctly"',
+        "Do NOT embed acceptance criteria in the description HTML — use the dedicated acceptanceCriteria field"
       ],
       example: '[{"id":"ac-1","text":"Given a user on the project settings page, when they select CSV format and click Export, then a CSV file downloads containing all tickets","isChecked":false},{"id":"ac-2","text":"Given an export with more than 100 items, when export is initiated, then a progress indicator is visible until completion","isChecked":false},{"id":"ac-3","text":"Given an export in progress, when it exceeds 30 seconds, then the user sees a timeout error with a retry option","isChecked":false}]',
       id_format: "Use unique IDs (ac-1, ac-2, etc.). Set isChecked to false for new tickets. Max 10000 chars total."
     },
+    ticket_references: {
+      description: "Mention/link other tickets in description HTML to auto-create cross-references.",
+      format: '<span data-ticket-key="PROJ-123" class="ticket-tag">PROJ-123</span>',
+      rules: [
+        "Use the ticket key (e.g., WHLZ-55, UNO-1) in the data-ticket-key attribute",
+        "The system automatically resolves keys to ticket IDs and creates bidirectional references",
+        'Referenced tickets appear in the "References" section of both the source and target tickets',
+        "Self-references are filtered out automatically"
+      ],
+      example: '<p>This depends on <span data-ticket-key="WHLZ-42" class="ticket-tag">WHLZ-42</span> for the auth middleware.</p>'
+    },
     tags: "Apply 2-5 tags per ticket AFTER creation using set_ticket_tags. Use lowercase-kebab-case. Common categories: feature area (auth, billing), technology (react, api), work type (feature, bug, refactor). Create missing tags with create_tag first.",
     ticket_type: "Always set typeSlug when creating tickets. Common types: feature, bug, task, improvement, story, spike, docs. Use list_ticket_types to see project-specific types. The typeSlug determines which template_structure sections to use.",
-    related_tickets: "ALWAYS call find_similar_tickets before creating a ticket to check for duplicates and related work. If a related parent ticket exists, link via parentId when creating. Use get_ticket_children to view subtasks of a ticket.",
+    related_tickets: "ALWAYS call find_similar_tickets before creating a ticket to check for duplicates and related work. If a related parent ticket exists, link via parentId when creating. Use get_ticket_children to view subtasks of a ticket. To find closed tickets related to a specific ticket, call find_similar_tickets with the ticket title/description, then cross-reference results with get_completed_tickets.",
     ai_workflow: "For best results, use the AI tools in this order: find_similar_tickets (check duplicates/related) → check_clarity (verify title) → generate_description (AI-generate HTML + acceptance criteria) → suggest_attributes (AI-suggest priority, size, tags) → create_ticket (ALWAYS include acceptanceCriteria + parentId if related) → set_ticket_tags. The generate_description tool gathers project context (related tickets, workflow) automatically."
   },
   categories: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kanbodev/mcp",
-  "version": "1.1.3",
+  "version": "1.1.5",
   "description": "MCP (Model Context Protocol) server for Kanbo - AI-native project management",
   "type": "module",
   "main": "dist/index.js",