wopee-mcp 1.23.1 → 1.23.2

package/build/tools/shared/schemas.js

@@ -16,10 +16,12 @@ export const SuiteAnalysisConfigSchema = z.object({
 });
 export const GenerateAIDataHandlerInputSchema = z.object({
     type: z.nativeEnum(GenerateArtifactType, {
-        description: "Chosen type of file(artifact) to generate",
+        description: "Type of test artifact to generate. One of: APP_CONTEXT, GENERAL_USER_STORIES, USER_STORIES_WITH_TEST_CASES, TEST_CASES, TEST_CASE_STEPS, REUSABLE_TEST_CASES, REUSABLE_TEST_CASE_STEPS. Start with APP_CONTEXT, then generate stories and test cases from it.",
     }),
     suiteUuid: z
-        .string({ description: "UUID of the suite to generate file(artifact) for" })
+        .string({
+        description: "UUID of the analysis suite to generate artifacts for. Get this from wopee_create_blank_suite or wopee_fetch_analysis_suites.",
+    })
         .min(1, "Suite UUID is required"),
 });
 export const GenerateAIDataInputSchema = z.object({
@@ -34,14 +36,16 @@ export const GenerateAIDataInputSchema = z.object({
 });
 export const FetchArtifactHandlerInputSchema = z.object({
     type: z.nativeEnum(ArtifactType, {
-        description: "Chosen file(artifact) to fetch",
+        description: "Type of test artifact to retrieve. One of: APP_CONTEXT (application description), GENERAL_USER_STORIES (stories without test cases), USER_STORIES (stories with test cases), PLAYWRIGHT_CODE (generated test code — requires identifier), PROJECT_CONTEXT (project-level context).",
     }),
     suiteUuid: z
-        .string({ description: "UUID of the suite to fetch the file from" })
+        .string({
+        description: "UUID of the analysis suite to fetch artifacts from. Get this from wopee_fetch_analysis_suites.",
+    })
         .min(1, "Suite UUID is required"),
     identifier: z
         .string({
-        description: "Identifier for the test case to fetch playwright code for, ex. `US004:TC006`, should be provided only for `PLAYWRIGHT_CODE` artifact type",
+        description: "Test case identifier in format 'US004:TC006'. Required only when type is PLAYWRIGHT_CODE. Ignored for all other artifact types.",
     })
         .optional(),
 });
@@ -67,17 +71,19 @@ export const FetchArtifactInputSchema = z.object({
 });
 export const UpdateArtifactHandlerInputSchema = z.object({
     type: z.nativeEnum(ArtifactType, {
-        description: "Chosen file(artifact) to update",
+        description: "Type of test artifact to update. One of: APP_CONTEXT, GENERAL_USER_STORIES, USER_STORIES, PLAYWRIGHT_CODE (requires identifier), PROJECT_CONTEXT. Must match the type used when the artifact was generated.",
     }),
     content: z.string({
-        description: "Content of the file(artifact) to update",
+        description: "The complete new content to replace the existing artifact. This is a destructive overwrite — the entire previous content is replaced. Pass the full updated content, not a partial diff.",
     }),
     suiteUuid: z
-        .string({ description: "UUID of the suite to update the file for" })
+        .string({
+        description: "UUID of the analysis suite containing the artifact to update. Get this from wopee_fetch_analysis_suites.",
+    })
         .min(1, "Suite UUID is required"),
     identifier: z
         .string({
-        description: "Identifier for the test case to update playwright code for, ex. `US004:TC006`, should be provided only for `PLAYWRIGHT_CODE` artifact type",
+        description: "Test case identifier in format 'US004:TC006'. Required only when type is PLAYWRIGHT_CODE. Ignored for all other artifact types.",
     })
         .optional(),
 });

package/build/tools/wopee_create_blank_suite/index.js

@@ -7,7 +7,7 @@ export const wopeeCreateBlankSuite = {
     name: ToolName.WOPEE_CREATE_BLANK_SUITE,
     config: {
         title: "Create blank analysis suite",
-        description: "Create a new empty analysis suite in the current project. Use this as the first step when starting a new testing workflow — the returned suite UUID is required by generate, fetch, update, and dispatch tools. Takes no input parameters; uses the project configured via WOPEE_PROJECT_UUID. Returns the created suite object including its UUID and metadata.",
+        description: "Create a new empty analysis suite in the current project. Use this as the first step when you want to manually build a test suite — the returned suite UUID is needed by wopee_generate_artifact, wopee_fetch_artifact, wopee_update_artifact, and wopee_dispatch_agent. If you want to auto-analyze a web app instead, use wopee_dispatch_analysis which creates and populates a suite in one step. Takes no input parameters; uses WOPEE_PROJECT_UUID from environment. Not idempotent: each call creates a new suite. Returns the suite object with UUID, name, type, and status. Fails if WOPEE_PROJECT_UUID is not configured.",
     },
     handler: async () => {
         try {

package/build/tools/wopee_dispatch_agent/index.js

@@ -9,7 +9,7 @@ export const wopeeDispatchAgent = {
     name: ToolName.WOPEE_DISPATCH_AGENT,
     config: {
         title: "Dispatch autonomous testing agent",
-        description: "Run an autonomous AI testing agent on specific test cases within a suite. The agent navigates the web app, executes test steps, captures screenshots, and reports pass/fail results. Requires a suite UUID and test case ID (e.g. TC001) with its parent user story ID (e.g. US001). Use wopee_generate_artifact first to create test cases, then this tool to execute them. Rate limit: 10 seconds between dispatches per project; concurrent calls auto-retry with backoff. Returns executed test case results including status and agent report.",
+        description: "Execute a specific test case by dispatching an autonomous AI agent. The agent opens a real browser, navigates the web app, follows the test case steps, captures screenshots at each step, and reports pass/fail with detailed findings. Prerequisite: test cases must exist in the suite — generate them first with wopee_generate_artifact (type USER_STORIES_WITH_TEST_CASES). Do NOT use this to analyze or crawl an app — use wopee_dispatch_analysis for that. Side effects: creates execution records and screenshots on the Wopee.io platform. Rate limit: 10 seconds between dispatches per project; concurrent calls auto-retry with exponential backoff. On success, returns executed test case results. On failure (invalid suite/test case ID), returns an error message. Use wopee_fetch_executed_test_cases afterward to get full results.",
         inputSchema: WopeeDispatchAgentInputSchema.shape,
     },
     handler: async (input) => {

package/build/tools/wopee_dispatch_analysis/index.js

@@ -9,7 +9,7 @@ export const wopeeDispatchAnalysis = {
     name: ToolName.WOPEE_DISPATCH_ANALYSIS,
     config: {
         title: "Dispatch analysis crawl",
-        description: "Create a new analysis suite and dispatch an AI crawling agent to explore and analyze a web application. The agent autonomously navigates the app starting from a given URL, discovers pages, and builds a sitemap. Optionally accepts login credentials, cookie preferences, custom variables, and additional instructions to guide the crawl. Use this instead of wopee_create_blank_suite when you want to auto-analyze a web app in one step. Rate limit: 10 seconds between dispatches per project; concurrent calls auto-retry with backoff. Returns the created analysis suite.",
+        description: "Create a new analysis suite AND dispatch an AI crawling agent in one step. The agent opens a real browser, navigates from the starting URL, discovers pages, and maps the application structure. Use this when you want to auto-analyze a web app — it combines suite creation and crawling. Use wopee_create_blank_suite instead if you want to manually populate the suite. Optionally accepts starting URL, login credentials, cookie preferences (ACCEPT_ALL, DECLINE_ALL, IGNORE), custom variables, and free-text instructions to guide the crawl. Not idempotent: each call creates a new suite and starts a new crawl. Side effects: creates a suite and execution records on the platform. Rate limit: 10 seconds between dispatches per project; concurrent calls auto-retry with exponential backoff. Returns the created suite object on success.",
         inputSchema: WopeeDispatchAnalysisInputSchema.shape,
     },
     handler: async (input) => {

package/build/tools/wopee_fetch_analysis_suites/index.js

@@ -7,7 +7,7 @@ export const wopeeFetchAnalysisSuites = {
     name: ToolName.WOPEE_FETCH_ANALYSIS_SUITES,
     config: {
         title: "List analysis suites",
-        description: "List all analysis suites in the current project. Returns an array of suites with their UUIDs, names, types, and statuses. Use this to find existing suites before generating content or dispatching agents. Takes no input parameters; uses the project configured via WOPEE_PROJECT_UUID. Each suite UUID can be passed to other tools like wopee_generate_artifact, wopee_fetch_artifact, or wopee_dispatch_agent.",
+        description: "List all analysis suites in the current project. Returns an array of suite objects with UUIDs, names, types (ANALYSIS, AGENT, etc.), and running statuses (IDLE, IN_PROGRESS, FINISHED). Use this to discover existing suites before calling other tools — you need a suite UUID for wopee_generate_artifact, wopee_fetch_artifact, wopee_update_artifact, and wopee_dispatch_agent. Read-only: does not create or modify anything. Takes no input; uses WOPEE_PROJECT_UUID from environment. Returns an empty array if no suites exist. Fails if WOPEE_PROJECT_UUID is not configured.",
     },
     handler: async () => {
         try {

package/build/tools/wopee_fetch_artifact/index.js

@@ -5,7 +5,7 @@ export const wopeeFetchArtifact = {
     name: ToolName.WOPEE_FETCH_ARTIFACT,
     config: {
         title: "Fetch test artifacts",
-        description: "Retrieve test artifacts from a suite. Supported types: APP_CONTEXT (application description), GENERAL_USER_STORIES (user stories without test cases), USER_STORIES (user stories with test cases), PLAYWRIGHT_CODE (Playwright test code for a specific test case — requires identifier like 'US004:TC006'), PROJECT_CONTEXT (project-level context). Use after wopee_generate_artifact to review test artifacts, or to retrieve existing artifacts for editing with wopee_update_artifact.",
+        description: "Retrieve a specific test artifact from a suite. Returns the artifact content as text. Use this to review what wopee_generate_artifact created, or to retrieve existing artifacts before editing with wopee_update_artifact. Does NOT modify any data — this is a read-only operation. If the requested artifact type has not been generated yet for this suite, returns an empty result. For PLAYWRIGHT_CODE, you must provide the test case identifier (e.g. 'US004:TC006'); omitting it returns an error. For all other types, the identifier parameter is ignored.",
         inputSchema: FetchArtifactHandlerInputSchema.shape,
     },
     handler: async (input) => await fetchArtifact(input),

package/build/tools/wopee_fetch_executed_test_cases/index.js

@@ -8,7 +8,7 @@ export const wopeeFetchExecutedTestCases = {
     name: ToolName.WOPEE_FETCH_EXECUTED_TEST_CASES,
     config: {
         title: "Fetch test execution results",
-        description: "Retrieve the results of test cases that have been executed by the autonomous agent. Returns each test case with its execution status (IN_PROGRESS, FINISHED, FAILED), agent report, and code report. Use this after wopee_dispatch_agent to check whether tests passed or failed and to review detailed findings. Requires the suite UUID; optionally accepts an analysis identifier (e.g. A068) to filter results.",
+        description: "Retrieve results of test cases executed by the autonomous agent. Returns each test case with its execution status (IN_PROGRESS, FINISHED, FAILED), agent report (natural language findings), and code report (technical details). Read-only: does not trigger any execution. Use this after wopee_dispatch_agent to check results — if status is IN_PROGRESS, wait and call again. Requires suite UUID. Optionally accepts an analysis identifier (e.g. A068, found in suite data) to filter to a specific analysis run. Returns an empty array if no test cases have been executed in this suite. Do NOT use this to fetch test artifacts like user stories or code — use wopee_fetch_artifact for that.",
         inputSchema: WopeeFetchExecutedTestCasesInputSchema.shape,
     },
     handler: async (input) => {

package/build/tools/wopee_generate_artifact/index.js

@@ -5,7 +5,7 @@ export const wopeeGenerateArtifact = {
     name: ToolName.WOPEE_GENERATE_ARTIFACT,
     config: {
         title: "Generate test artifacts",
-        description: "Generate AI-powered test artifacts for a suite. Supported types: APP_CONTEXT (analyze the application and create a description), GENERAL_USER_STORIES (generate user stories from app context), USER_STORIES_WITH_TEST_CASES (generate user stories with detailed test cases), TEST_CASES (generate test cases for existing user stories), TEST_CASE_STEPS (generate step-by-step instructions for test cases), REUSABLE_TEST_CASES (generate reusable/shared test cases), REUSABLE_TEST_CASE_STEPS (generate steps for reusable test cases). Typical workflow: generate APP_CONTEXT first, then USER_STORIES_WITH_TEST_CASES, then use wopee_dispatch_agent to execute them.",
+        description: "Generate AI-powered test artifacts for a suite using the Wopee.io AI engine. Each call creates one artifact type — call multiple times for different types. Generation order matters: APP_CONTEXT must be generated before user stories, and user stories before test cases. If called out of order, the AI may produce lower quality results. On success, returns confirmation that generation started. Use wopee_fetch_artifact to retrieve the generated content once ready. Do NOT use this to update existing artifacts — use wopee_update_artifact instead. Generating the same type again overwrites the previous version.",
         inputSchema: GenerateAIDataHandlerInputSchema.shape,
     },
     handler: async (input) => await generateAIDataFile(input),

package/build/tools/wopee_update_artifact/index.js

@@ -5,7 +5,7 @@ export const wopeeUpdateArtifact = {
     name: ToolName.WOPEE_UPDATE_ARTIFACT,
     config: {
         title: "Update test artifacts",
-        description: "Update previously generated content in a suite. Use this to refine user stories, test cases, app context, or Playwright code after reviewing them with wopee_fetch_artifact. Requires the content type (APP_CONTEXT, GENERAL_USER_STORIES, USER_STORIES, PLAYWRIGHT_CODE, or PROJECT_CONTEXT), the suite UUID, and the new content as a string. For PLAYWRIGHT_CODE, also provide the test case identifier (e.g. 'US004:TC006'). This enables an iterative workflow: generate → review → update → dispatch.",
+        description: "Replace the content of a previously generated test artifact in a suite. This is a destructive overwrite — the full content is replaced, not patched. Use this after reviewing artifacts with wopee_fetch_artifact to fix incorrect user stories, refine test case steps, or edit generated Playwright code. Do NOT use this to create new artifacts — use wopee_generate_artifact instead. Prerequisite: the artifact must already exist (generated via wopee_generate_artifact). On success, returns confirmation. On failure (e.g. invalid suite UUID, missing artifact), returns an error message. Idempotent: calling with the same content multiple times produces the same result.",
         inputSchema: UpdateArtifactHandlerInputSchema.shape,
     },
     handler: async (input) => await updateArtifact(input),

package/package.json

@@ -4,7 +4,7 @@
   "bin": {
     "wopee-mcp": "./build/index.js"
   },
-  "version": "1.23.1",
+  "version": "1.23.2",
   "mcpName": "io.github.Wopee-io/wopee-mcp",
   "description": "Wopee.io MCP server for autonomous testing platform",
   "main": "./build/index.js",