@skyramp/mcp 0.0.12 → 0.0.14

package/README.md

@@ -83,7 +83,7 @@ Add the following configuration. For more information, read the [Cursor MCP docu
 }
 ```
 
-[![Install MCP Server on MacOS](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/install-mcp?name=skyramp-mcp&config=eyJjb21tYW5kIjoibnB4IC15IEBza3lyYW1wL21jcEBsYXRlc3QifQ==)
+[![Install MCP Server on MacOS](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/en/install-mcp?name=skyramp-mcp&config=eyJjb21tYW5kIjoibnB4IC15IEBza3lyYW1wL21jcEBsYXRlc3QifQ==)
 
 ### Note: To pull latest changes restart the MCP server
 
@@ -120,7 +120,7 @@ On Windows, you might need to use this alternative configuration:
 }
 ```
 
-[![Install MCP Server on Windows](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/install-mcp?name=skyramp-mcp&config=eyJjb21tYW5kIjoiY21kIC9rIG5weCAteSBAc2t5cmFtcC9tY3BAbGF0ZXN0In0=)
+[![Install MCP Server on Windows](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/en/install-mcp?name=skyramp-mcp&config=eyJjb21tYW5kIjoiY21kIC9rIG5weCAteSBAc2t5cmFtcC9tY3BAbGF0ZXN0In0=)
 
 ## Available tools
 

package/build/tools/executeSkyrampTestTool.js

@@ -56,7 +56,7 @@ For detailed documentation visit: https://www.skyramp.dev/docs/quickstart`,
         },
     }, async (params) => {
         var docker = new Docker();
-        var image = "public.ecr.aws/skyramp/rampup/runner:mcp-v0.0.3";
+        var image = "public.ecr.aws/skyramp/rampup/runner:mcp-v0.0.4";
         // Use path.basename for safer filename extraction
         const filename = path.basename(params.testFile);
         if (!filename) {

package/build/tools/generateE2ERestTool.js

@@ -19,6 +19,9 @@ export class E2ETestService extends TestGenerationService {
             playwrightInput: params.playwrightInput,
         };
     }
+    async handleApiAnalysis(params, generateOptions) {
+        return null;
+    }
 }
 export function registerE2ETestTool(server) {
     server.registerTool("skyramp_e2e_test_generation", {

package/build/tools/generateFuzzRestTool.js

@@ -5,6 +5,7 @@ const fuzzTestSchema = {
     ...baseTestSchema,
     responseData: z
         .string()
+        .default("")
         .describe("Sample response body data, provided either as an inline JSON/YAML string or as an absolute file path prefixed with '@' (e.g., @/absolute/path/to/file)"),
 };
 export class FuzzTestService extends TestGenerationService {

package/build/tools/generateIntegrationRestTool.js

@@ -18,6 +18,9 @@ export class IntegrationTestService extends TestGenerationService {
             playwrightInput: params.playwrightInput,
         };
     }
+    async handleApiAnalysis(params, generateOptions) {
+        return null;
+    }
 }
 export function registerIntegrationTestTool(server) {
     server.registerTool("skyramp_integration_test_generation", {

package/build/tools/generateLoadRestTool.js

@@ -47,6 +47,9 @@ export class LoadTestService extends TestGenerationService {
             loadTargetRPS: params.loadTargetRPS,
         };
     }
+    async handleApiAnalysis(params, generateOptions) {
+        return null;
+    }
 }
 export function registerLoadTestTool(server) {
     server.registerTool("skyramp_load_test_generation", {

package/build/utils/modularization-prompts.js

@@ -1,16 +1,10 @@
 export function getModularizationPrompt() {
     return `
 **IMPORTANT: Now please modularize the code by**
-
-1. Group related lines logically (e.g., login steps together) to improve readability and parameterize the test function(s) with meaningful parameters to make it more flexible.
-2. Parameterize the test function(s) with meaningful parameters to make it more flexible. Preserve the original order of code lines within each function
-3. Do not change or remove any existing lines of code, variable names, function names, or function structures.
-4. Only extract reusable logical sections into helper functions or parameterized structures where applicable.
-5. SEARCH REPOSITORY FOR CODE THAT CAN BE REUSED AND USE IT. WITHOUT BREAKING NEW OR EXISTING TESTS/FUNCTIONS/CODE.
-6. Do not create any new test cases or a new modular file but only helper functions with modularization done in the same file.
-7. Make sure the logic is same and the test works as expected.
-8. Do not add any new logic or classes or any other files.
+Please modularize and parameterize the test function(s) in the following code, modularize each functionality done by user into clear separate logical groups to make it more readable, and parameterize the modularized function(s) with necessary meaningful parameters to make it more flexible, making sure to keep the order of code lines, existing variable names, existing function names, existing function structures as same, without altering or removing any existing code lines. Keep the skyramp command comments in the beginning of the code. Respond with the complete, modularized code only. DO NOT ADD DEPENDENCY INSTRUCTIONS IN THE CODE.
 
 Please refactor the code with these modularization principles. Respond with the complete, modularized code only.
+
+
   `;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skyramp/mcp",
-  "version": "0.0.12",
+  "version": "0.0.14",
   "main": "build/index.js",
   "type": "module",
   "bin": {