wopee-mcp 1.5.0 → 1.6.0

package/README.md

@@ -92,122 +92,40 @@ Dispatch a new analysis suite
 
 ### Generation Tools
 
-These tools generate various artifacts for a specific suite. All require a `suiteUuid`.
+These tools generate various artifacts for a specific suite. All require a `suiteUuid` and `fileType` to generate.
 
-#### `wopee_generate_app_context`
+#### `wopee_generate_file`
 
-Generates an application context markdown file for the selected suite. This provides a comprehensive overview of the application being analyzed.
-
-- **Parameters:**
-  - `suiteUuid` - The UUID of the suite to generate context for
-- **Returns:** Generated output in case of successful generation
-
-**Example Usage:**
-
-```
-Generate app context for suite abc-123-def-456
-```
-
-#### `wopee_generate_general_user_stories`
-
-Generates general user stories markdown file for the selected suite.
+Generates a specific file(artifact) for the selected suite.
 
 - **Parameters:**
   - `suiteUuid` - The UUID of the suite
-- **Returns:** Generated output in case of successful generation
-
-**Example Usage:**
-
-```
-Generate general user stories for my latest suite
-```
-
-#### `wopee_generate_user_stories`
-
-Generates detailed user stories JSON file for the selected suite.
-
-- **Parameters:**
-  - `suiteUuid` - The UUID of the suite
-- **Returns:** Generated output in case of successful generation
-
-**Example Usage:**
-
-```
-Generate user stories for suite abc-123-def-456
-```
-
-#### `wopee_generate_test_cases`
-
-Generates test cases for the selected suite based on the analysis and user stories.
-
-- **Parameters:**
-  - `suiteUuid` - The UUID of the suite
-- **Returns:** Generated output in case of successful generation
+  - `fileType` - `"APP_CONTEXT" | "GENERAL_USER_STORIES" | "USER_STORIES" | "TEST_CASES"`
+- **Returns:** Generated output in case of successful generation.
 
 **Example Usage:**
 
 ```
-Generate test cases for suite abc-123-def-456
+Generate app context for my most recent analysis suite
 ```
 
 ### Fetch Tools
 
-These tools retrieve generated artifacts for a specific suite. All require a `suiteUuid`.
+These tools retrieve generated artifacts for a specific suite. All require a `suiteUuid` and `fileType`.
 
-#### `wopee_fetch_app_context`
+#### `wopee_fetch_file`
 
-Fetches the application context markdown file for a suite.
+Fetches the enquired file(artifact) from the selected suite.
 
 - **Parameters:**
   - `suiteUuid` - The UUID of the suite
-- **Returns:** The application context markdown content
-
-**Example Usage:**
-
-```
-Fetch app context for my latest suite
-```
-
-#### `wopee_fetch_general_user_stories`
-
-Fetches the general user stories markdown file for a suite.
-
-- **Parameters:**
-  - `suiteUuid` - The UUID of the suite
-- **Returns:** The general user stories markdown content
-
-**Example Usage:**
-
-```
-Fetch general user stories for suite abc-123-def-456
-```
-
-#### `wopee_fetch_user_stories`
-
-Fetches the user stories JSON file for a suite.
-
-- **Parameters:**
-  - `suiteUuid` - The UUID of the suite
-- **Returns:** The user stories JSON content
-
-**Example Usage:**
-
-```
-Fetch user stories for suite abc-123-def-456
-```
-
-#### `wopee_fetch_test_cases`
-
-Fetches the test cases JSON file for a suite.
-
-- **Parameters:**
-  - `suiteUuid` - The UUID of the suite
-- **Returns:** The test cases JSON content
+  - `fileType` - `"APP_CONTEXT" | "GENERAL_USER_STORIES" | "USER_STORIES" | "TEST_CASES"`
+- **Returns:** The file contents in case of successful fetch.
 
 **Example Usage:**
 
 ```
-Fetch test cases for suite abc-123-def-456
+Fetch user stories for the latest suite
 ```
 
 ### Update Tools
@@ -259,9 +177,10 @@ Dispatch agent for my latest suite's user story US001 and test case TC003
 
 2. **Generate artifacts:**
 
-   - Generate app context: `wopee_generate_app_context`
-   - Generate user stories: `wopee_generate_user_stories` or `wopee_generate_general_user_stories`
-   - Generate test cases: `wopee_generate_test_cases`
+   - Generate app context: `wopee_generate_file` with `APP_CONTEXT` and specific `suiteUuid`
+   - Generate general user stories: `wopee_generate_file` with `GENERAL_USER_STORIES` and specific `suiteUuid`
+   - Generate user stories: `wopee_generate_file` with `USER_STORIES` and specific `suiteUuid`
+   - Generate test cases: `wopee_generate_file` with `TEST_CASES` and specific `suiteUuid`
 
 3. **Fetch generated content:**
 
@@ -273,5 +192,5 @@ Dispatch agent for my latest suite's user story US001 and test case TC003
 ## Notes
 
 - Most tools require a `suiteUuid`. Always start by fetching or creating a suite.
-- `wopee_dispatch_analysis` tool will go through whole cycle of processing - crawling the application and generating all of the artifacts one by one.
+- `wopee_dispatch_analysis` tool will go through whole cycle of processing - crawling the application and generating all of the files(artifacts) one by one.
 - It is advisable to use [cmd.wopee.io](https://cmd.wopee.io) for a convenient visual representation of the generated data and results of the agent runs.

package/build/index.js

@@ -1,6 +1,7 @@
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
 import { TOOLS } from "./tools/index.js";
+import { PROMPTS } from "./prompts/index.js";
 const server = new McpServer({
     name: "wopee-mcp",
     version: "1.0.0",
@@ -8,6 +9,9 @@ const server = new McpServer({
 for (const { name, config, handler } of TOOLS) {
     server.registerTool(name, config, handler);
 }
+for (const { name, config, handler } of PROMPTS) {
+    server.registerPrompt(name, config, handler);
+}
 async function main() {
     const transport = new StdioServerTransport();
     await server.connect(transport);

package/build/prompts/fetch_project_summary/index.js

@@ -0,0 +1,60 @@
+import { PromptName } from "../shared/types.js";
+export const fetchProjectSummary = {
+    name: PromptName.FETCH_PROJECT_SUMMARY,
+    config: {
+        title: "Fetch project summary",
+        description: "Fetch project summary in pre-formatted markdown tables",
+    },
+    handler: () => ({
+        messages: [
+            {
+                role: "user",
+                content: {
+                    type: "text",
+                    text: `Please, fetch my analysis suites using 'wopee_fetch_analysis_suites' tool and if there are more than 5 suites, ask the user to specify how many suites he wishes to use for further processing. Then for each suite in the list, fetch its user stories/test cases using 'wopee_fetch_file' tool with the file type 'USER_STORIES' OR 'TEST_CASES' (no need to specify both arguments as they both return the same output).
+          
+          After fetching all of the necessary data, summarize and display two readable markdown tables as an output in the same chat conversation. Do NOT create, write, or save any files to disk - only display the formatted tables in your response:
+
+          - The first table should have the following columns:
+            - analysis name
+            - number of user stories
+            - number of test cases
+
+          ### Example of the first table:
+
+          | 📊 Analysis Name | 📝 User Stories | ✅ Test Cases |
+          |-------------------|-----------------|---------------|
+          | Analysis - A068   | 5               | 8             |
+          | Analysis - A067   | 5               | 7             |
+
+          ___
+
+          - The second table should have the following columns:
+            - analysis name
+              - user story category
+                - user story name
+                  - test case name
+                    - number of steps
+
+          ### Example of the second table:
+          | 📊 Analysis Name | 📁 User Story Category | 📋 User Story Name | 🧪 Test Case Name | 🔢 Steps |
+          |-------------------|------------------------|-------------------|-------------------|-------------|
+          | Analysis - A068 | User Authentication | Authentication and Access to Promotions | Successful Sign In and Promotion Visibility | 7 |
+          | | | | Login Form Validation - Empty Required Fields | 4 |
+          | | | | Login Failure with Invalid Credentials | 7 |
+          | | Account Support | Account Assistance and Support Navigation | Navigate to sign-in page and verify 'Forget your password?' link | 2 |
+          | | | | Password help link redirects to support page | 5 |
+          | Analysis - A067 | User Authentication | Sign In with @tesena.com Email to Access Catalogue | Sign in form loads with all required elements present | 5 |
+          | | | | Sign in with valid @tesena.com credentials redirects to catalogue | 5 |
+
+          ___
+
+          ## Important Notes:
+            - Use short, yet descriptive names for the column headers.
+            - Please, add emojis for the column headers.
+          `,
+                },
+            },
+        ],
+    }),
+};

package/build/prompts/index.js

@@ -0,0 +1,2 @@
+import { fetchProjectSummary } from "./fetch_project_summary/index.js";
+export const PROMPTS = [fetchProjectSummary];

package/build/prompts/shared/types.js

@@ -0,0 +1,4 @@
+export var PromptName;
+(function (PromptName) {
+    PromptName["FETCH_PROJECT_SUMMARY"] = "fetch-project-summary";
+})(PromptName || (PromptName = {}));

package/package.json

@@ -4,7 +4,7 @@
   "bin": {
     "wopee-mcp": "./build/index.js"
   },
-  "version": "1.5.0",
+  "version": "1.6.0",
   "description": "Wopee.io MCP server",
   "main": "./build/index.js",
   "scripts": {