wopee-mcp 1.12.0 → 1.14.0

package/README.md

@@ -70,6 +70,59 @@ If you're unsure about your proxy settings, check your VS Code settings (`settin
 - `http://10.x.x.x:8080`
 - `http://username:password@proxy.company.com:8080` (if authentication is required)
 
+### TLS / Certificate Issues
+
+**This is not required for MCP to work.** If you see HTTPS or certificate-related errors, that indicates a TLS or certificate trust issue in your environment.
+
+If the server fails with errors such as **`UNABLE_TO_VERIFY_LEAF_SIGNATURE`** or **`certificate has expired`**, it may be due to:
+
+- **Self-signed certificates** (e.g. when `WOPEE_API_URL` points to an internal or dev server)
+- **Corporate proxy / SSL inspection** (traffic re-encrypted with a corporate CA your machine doesn’t trust)
+- **Missing CA certificates** in Node’s trust store
+
+#### Preferred solutions (secure)
+
+1. **Use a valid TLS certificate** – e.g. Let’s Encrypt, or an internal CA – and ensure the **full certificate chain** is served.
+2. **Install the corporate or internal CA** so Node trusts it:
+
+   Example:
+
+   ```bash
+   export NODE_EXTRA_CA_CERTS=/etc/ssl/certs/internal-ca.pem
+   ```
+
+   In MCP config `env`:
+
+   ```json
+   "env": {
+     "WOPEE_PROJECT_UUID": "your-project-uuid-here",
+     "WOPEE_API_KEY": "your-api-key-here",
+     "NODE_EXTRA_CA_CERTS": "/path/to/ca.pem"
+   }
+   ```
+
+#### Insecure workaround (not recommended)
+
+For **local debugging only**, you may disable TLS verification in Node. This should **never** be used in production, as it disables HTTPS security and exposes traffic to interception.
+
+```bash
+export NODE_TLS_REJECT_UNAUTHORIZED=0
+```
+
+Or in MCP config `env`:
+
+```json
+"env": {
+  "WOPEE_PROJECT_UUID": "your-project-uuid-here",
+  "WOPEE_API_KEY": "your-api-key-here",
+  "NODE_TLS_REJECT_UNAUTHORIZED": "0"
+}
+```
+
+Treat this as a **debug-only escape hatch**, not a normal setup step.
+
+**Note:** Some users have reported setting `PYTHONHTTPSVERIFY=0` as well. This MCP server does not use Python; that variable has no effect on it. It would only apply if you run a Python-based MCP host or other tooling that also performs HTTPS in the same environment—outside the scope of this server.
+
 ## Getting Started
 
 Most tools in this MCP server require a `suiteUuid` to operate. You have two options to get started:
@@ -122,6 +175,8 @@ Fetch all existing analysis suites for my project
 
 Creates and dispatches a new analysis/crawling suite for your project. Use this to start a fresh analysis session.
 
+- **Parameters:**
+  - `additionalInstructions` *(optional)* - Additional instructions to guide the agent during the analysis/crawling phase (e.g. focus areas, things to ignore, login steps, etc.)
 - **Returns:** Success message with the created suite information
 
 **Example Usage:**
@@ -130,6 +185,10 @@ Creates and dispatches a new analysis/crawling suite for your project. Use this
 Dispatch a new analysis suite
 ```
 
+```
+Dispatch a new analysis suite and focus on the checkout flow
+```
+
 #### `wopee_create_blank_suite`
 
 Creates a blank analysis suite for your project. Use this when you want to manually configure and populate a suite rather than having it automatically analyzed.

package/build/tools/wopee_dispatch_analysis/factory.js

@@ -1,5 +1,5 @@
 import { getConfig } from "../../utils/getConfig.js";
-export const createDispatchAnalysisInput = () => {
+export const createDispatchAnalysisInput = (input) => {
     const { WOPEE_PROJECT_UUID } = getConfig();
     if (!WOPEE_PROJECT_UUID)
         throw new Error("WOPEE_PROJECT_UUID is not set");
@@ -10,7 +10,7 @@ export const createDispatchAnalysisInput = () => {
             username: null,
             password: null,
             cookiesPreference: null,
-            additionalInstructions: null,
+            additionalInstructions: input.additionalInstructions ?? null,
             additionalVariables: null,
         },
         rerun: null,

package/build/tools/wopee_dispatch_analysis/index.js

@@ -1,5 +1,5 @@
 import { _parseError } from "../shared/helpers.js";
-import { DispatchAnalysisInputSchema } from "./schema.js";
+import { DispatchAnalysisInputSchema, WopeeDispatchAnalysisInputSchema, } from "./schema.js";
 import { createDispatchAnalysisInput } from "./factory.js";
 import { DispatchAnalysis } from "../shared/gql-queries.js";
 import { requestClient } from "../../utils/requestClient.js";
@@ -9,11 +9,12 @@ export const wopeeDispatchAnalysis = {
     config: {
         title: "Dispatch analysis",
         description: "Create and dispatch analysis/crawling suite for a project",
+        inputSchema: WopeeDispatchAnalysisInputSchema.shape,
     },
-    handler: async () => {
+    handler: async (input) => {
         try {
-            const input = createDispatchAnalysisInput();
-            const parsedInput = DispatchAnalysisInputSchema.parse(input);
+            const rawInput = createDispatchAnalysisInput(input);
+            const parsedInput = DispatchAnalysisInputSchema.parse(rawInput);
             const result = await requestClient(DispatchAnalysis, {
                 input: parsedInput,
             });

package/build/tools/wopee_dispatch_analysis/schema.js

@@ -15,3 +15,8 @@ export const DispatchAnalysisInputSchema = z.object({
     suiteAnalysisConfig: SuiteAnalysisConfigSchema,
     rerun: RerunOptionsSchema.nullable().default(null),
 });
+export const WopeeDispatchAnalysisInputSchema = z.object({
+    additionalInstructions: z
+        .string({ description: "Additional instructions for the agent" })
+        .nullish(),
+});

package/package.json

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