@telos.ready/mcp 1.0.1 → 1.1.0

package/README.md

@@ -180,6 +180,9 @@ npm run build
 ### Publishing
 
 ```bash
+npm whoami
+npm login
+npm version patch|minor|major
 npm publish --access public
 ```
 
@@ -217,7 +220,3 @@ If you encounter issues:
 
 ISC
 
-## Deploying
-npm whoami
-npm login
-npm version patch|minor|major

package/build/index.js

@@ -125,7 +125,43 @@ server.tool("ask-question", "Asks a question about an application and gets an an
         };
     }
 });
-// Tool 2: Add Ticket Comment
+// Tool 2: Search Documentation
+server.tool("search-documentation", "Searches documentation for an application to get relevant context. Documentation includes information about application resources, concepts, stories and known solutions. Provide both an application slug and a specific query.", {
+    applicationSlug: z
+        .string()
+        .describe('The application slug for the application you want to search documentation for, which is a unique identifier string used to reference specific applications.'),
+    query: z
+        .string()
+        .describe("The query to search for in the documentation."),
+}, async ({ applicationSlug, query }) => {
+    try {
+        const result = await telosClient.post("/mcp/search-documentation", {
+            applicationSlug,
+            query,
+        });
+        if (result.success) {
+            return {
+                content: [{ type: "text", text: result.result }],
+            };
+        }
+        else {
+            return {
+                content: [{ type: "text", text: `Error: ${result}` }],
+            };
+        }
+    }
+    catch (error) {
+        return {
+            content: [
+                {
+                    type: "text",
+                    text: `Error searching documentation for application ${applicationSlug}: ${error}`,
+                },
+            ],
+        };
+    }
+});
+// Tool 3: Add Ticket Comment
 server.tool("add-ticket-comment", "Adds a comment to an existing ticket. This tool allows adding a comment to a specific ticket with proper attribution.", {
     ticketReference: z
         .string()
@@ -167,7 +203,7 @@ server.tool("add-ticket-comment", "Adds a comment to an existing ticket. This to
         };
     }
 });
-// Tool 3: Add Documentation (Create Knowledge Ticket)
+// Tool 4: Add Documentation (Create Knowledge Ticket)
 server.tool("add-documentation", "Creates a new knowledge ticket with documentation content. Only use this tool if a comment cannot be added directly to a ticket. This tool creates a knowledge ticket that can be used to store and organize documentation, procedures, guides, or any other knowledge-based content for future reference.", {
     content: z
         .string()
@@ -205,7 +241,7 @@ server.tool("add-documentation", "Creates a new knowledge ticket with documentat
         };
     }
 });
-// Tool 4: Get Ticket Details
+// Tool 5: Get Ticket Details
 server.tool("get-ticket-details", "Gets the details of a ticket. The ticket reference must be provided. This tool will provide the initial description of the ticket and any comments that users have made on the ticket.", {
     ticketReference: z
         .string()
@@ -237,7 +273,7 @@ server.tool("get-ticket-details", "Gets the details of a ticket. The ticket refe
         };
     }
 });
-// Tool 5: Get Next Task
+// Tool 6: Get Next Task
 server.tool("get-next-task", "Gets the next task for a member and provides a ticket reference, next step and instructions for completing the task.", {
     applicationSlug: z
         .string()
@@ -269,7 +305,7 @@ server.tool("get-next-task", "Gets the next task for a member and provides a tic
         };
     }
 });
-// Tool 6: Get Git Branch for Ticket
+// Tool 7: Get Git Branch for Ticket
 server.tool("get-git-branch-for-ticket", "Gets the git branch to be used for development work on this ticket. All commits for this ticket must use this branch. Git branches must stay ahead of main.", {
     ticketReference: z
         .string()
@@ -301,7 +337,7 @@ server.tool("get-git-branch-for-ticket", "Gets the git branch to be used for dev
         };
     }
 });
-// Tool 7: Mark Ticket as Blocked
+// Tool 8: Mark Ticket as Blocked
 server.tool("mark-ticket-as-blocked", "Marks a ticket as blocked with a specified reason. This tool will load the ticket, add a comment with the blocking reason, and set the ticket status to blocked.", {
     ticketReference: z
         .string()
@@ -337,7 +373,7 @@ server.tool("mark-ticket-as-blocked", "Marks a ticket as blocked with a specifie
         };
     }
 });
-// Tool 8: Update Action Item
+// Tool 9: Update Action Item
 server.tool("update-action-item", "Updates the status of an action item in a ticket. This tool finds a specific action item in the ticket or its comments and updates its status to INCOMPLETE, INPROGRESS, or COMPLETED.", {
     ticketReference: z
         .string()
@@ -389,7 +425,7 @@ async function main() {
         await server.connect(transport);
         // Log success message
         console.error("✅ Telos MCP Server running on stdio");
-        console.error("Available tools: ask-question, add-ticket-comment, add-documentation, get-ticket-details, get-next-task, get-git-branch-for-ticket, mark-ticket-as-blocked, update-action-item");
+        console.error("Available tools: ask-question, search-documentation, add-ticket-comment, add-documentation, get-ticket-details, get-next-task, get-git-branch-for-ticket, mark-ticket-as-blocked, update-action-item");
         // Test connection in background without blocking or exiting
         // This is non-critical and should not cause the server to exit
         setImmediate(async () => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@telos.ready/mcp",
-  "version": "1.0.1",
+  "version": "1.1.0",
   "description": "Telos MCP server for managing tickets and project tasks",
   "main": "build/index.js",
   "type": "module",