wopee-mcp 1.2.2 → 1.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +257 -0
  2. package/package.json +1 -1
package/README.md ADDED
@@ -0,0 +1,257 @@
1
+ # Wopee MCP Server
2
+
3
+ A Model Context Protocol (MCP) server for interacting with Wopee.io's autonomous testing platform. This server provides tools for managing analysis suites, generating test cases, user stories, and dispatching autonomous testing agents.
4
+
5
+ ## Setup
6
+
7
+ ### Prerequisites
8
+
9
+ - Node.js (v18 or higher recommended)
10
+ - An IDE that supports MCP (Model Context Protocol), such as Cursor or VSCode
11
+
12
+ ### MCP Server Configuration
13
+
14
+ Add this server to your MCP configuration.
15
+
16
+ ### Configuration Example
17
+
18
+ ```json
19
+ {
20
+ "mcpServers": {
21
+ "wopee": {
22
+ "command": "npx wopee-mcp",
23
+ "env": {
24
+ "WOPEE_PROJECT_UUID": "your-project-uuid-here",
25
+ "WOPEE_API_KEY": "your-api-key-here"
26
+ }
27
+ }
28
+ }
29
+ }
30
+ ```
31
+
32
+ #### Required Environment Variables
33
+
34
+ - **`WOPEE_PROJECT_UUID`** - Your Wopee project UUID. This identifies which project you're working with.
35
+ - **`WOPEE_API_KEY`** - Your Wopee API key. You can create one at [cmd.wopee.io](https://cmd.wopee.io), in your project's settings.
36
+
37
+ #### Optional Environment Variables
38
+
39
+ - **`WOPEE_API_URL`** - The Wopee API endpoint URL. Should be specified only for testing/development purposes.
40
+
41
+ ## Getting Started
42
+
43
+ Most tools in this MCP server require a `suiteUuid` to operate. You have two options to get started:
44
+
45
+ ### Option 1: Use Existing Suites
46
+
47
+ Start by fetching your existing analysis suites:
48
+
49
+ ```
50
+ Use the wopee_fetch_analysis_suites tool to retrieve all available suites for your project.
51
+ ```
52
+
53
+ This will return a list of all analysis suites with their UUIDs, which you can then use with other tools.
54
+
55
+ ### Option 2: Create a New Suite
56
+
57
+ If you don't have any suites yet, create a fresh analysis suite:
58
+
59
+ ```
60
+ Use the wopee_dispatch_analysis tool to create and dispatch a new analysis/crawling suite.
61
+ ```
62
+
63
+ This will create a new suite and return its UUID, which you can use for subsequent operations.
64
+
65
+ ## Available Tools
66
+
67
+ ### Suite Management
68
+
69
+ #### `wopee_fetch_analysis_suites`
70
+
71
+ Fetches all analysis suites for your project. This is a good starting point to see what suites are available.
72
+
73
+ - **Returns:** Array of analysis suites with their UUIDs, names, statuses, and metadata
74
+
75
+ **Example Usage:**
76
+
77
+ ```
78
+ Fetch all existing analysis suites for my project
79
+ ```
80
+
81
+ #### `wopee_dispatch_analysis`
82
+
83
+ Creates and dispatches a new analysis/crawling suite for your project. Use this to start a fresh analysis session.
84
+
85
+ - **Returns:** Success message with the created suite information
86
+
87
+ **Example Usage:**
88
+
89
+ ```
90
+ Dispatch a new analysis suite
91
+ ```
92
+
93
+ ### Generation Tools
94
+
95
+ These tools generate various artifacts for a specific suite. All require a `suiteUuid`.
96
+
97
+ #### `wopee_generate_app_context`
98
+
99
+ Generates an application context markdown file for the selected suite. This provides a comprehensive overview of the application being analyzed.
100
+
101
+ - **Parameters:**
102
+ - `suiteUuid` - The UUID of the suite to generate context for
103
+ - **Returns:** Generated output in case of successful generation
104
+
105
+ **Example Usage:**
106
+
107
+ ```
108
+ Generate app context for suite abc-123-def-456
109
+ ```
110
+
111
+ #### `wopee_generate_general_user_stories`
112
+
113
+ Generates general user stories markdown file for the selected suite.
114
+
115
+ - **Parameters:**
116
+ - `suiteUuid` - The UUID of the suite
117
+ - **Returns:** Generated output in case of successful generation
118
+
119
+ **Example Usage:**
120
+
121
+ ```
122
+ Generate general user stories for my latest suite
123
+ ```
124
+
125
+ #### `wopee_generate_user_stories`
126
+
127
+ Generates detailed user stories JSON file for the selected suite.
128
+
129
+ - **Parameters:**
130
+ - `suiteUuid` - The UUID of the suite
131
+ - **Returns:** Generated output in case of successful generation
132
+
133
+ **Example Usage:**
134
+
135
+ ```
136
+ Generate user stories for suite abc-123-def-456
137
+ ```
138
+
139
+ #### `wopee_generate_test_cases`
140
+
141
+ Generates test cases for the selected suite based on the analysis and user stories.
142
+
143
+ - **Parameters:**
144
+ - `suiteUuid` - The UUID of the suite
145
+ - **Returns:** Generated output in case of successful generation
146
+
147
+ **Example Usage:**
148
+
149
+ ```
150
+ Generate test cases for suite abc-123-def-456
151
+ ```
152
+
153
+ ### Fetch Tools
154
+
155
+ These tools retrieve generated artifacts for a specific suite. All require a `suiteUuid`.
156
+
157
+ #### `wopee_fetch_app_context`
158
+
159
+ Fetches the application context markdown file for a suite.
160
+
161
+ - **Parameters:**
162
+ - `suiteUuid` - The UUID of the suite
163
+ - **Returns:** The application context markdown content
164
+
165
+ **Example Usage:**
166
+
167
+ ```
168
+ Fetch app context for my latest suite
169
+ ```
170
+
171
+ #### `wopee_fetch_general_user_stories`
172
+
173
+ Fetches the general user stories markdown file for a suite.
174
+
175
+ - **Parameters:**
176
+ - `suiteUuid` - The UUID of the suite
177
+ - **Returns:** The general user stories markdown content
178
+
179
+ **Example Usage:**
180
+
181
+ ```
182
+ Fetch general user stories for suite abc-123-def-456
183
+ ```
184
+
185
+ #### `wopee_fetch_user_stories`
186
+
187
+ Fetches the user stories JSON file for a suite.
188
+
189
+ - **Parameters:**
190
+ - `suiteUuid` - The UUID of the suite
191
+ - **Returns:** The user stories JSON content
192
+
193
+ **Example Usage:**
194
+
195
+ ```
196
+ Fetch user stories for suite abc-123-def-456
197
+ ```
198
+
199
+ #### `wopee_fetch_test_cases`
200
+
201
+ Fetches the test cases JSON file for a suite.
202
+
203
+ - **Parameters:**
204
+ - `suiteUuid` - The UUID of the suite
205
+ - **Returns:** The test cases JSON content
206
+
207
+ **Example Usage:**
208
+
209
+ ```
210
+ Fetch test cases for suite abc-123-def-456
211
+ ```
212
+
213
+ ### Agent Testing
214
+
215
+ #### `wopee_dispatch_agent`
216
+
217
+ Dispatches an autonomous testing agent to execute test cases for a selected suite.
218
+
219
+ - **Parameters:**
220
+ - `suiteUuid` - The UUID of the suite containing the test cases
221
+ - `analysisIdentifier` - The analysis identifier for the suite
222
+ - `testCases` - Array of test case objects to execute, each containing:
223
+ - `testCaseId` - The ID of the test case
224
+ - `userStoryId` - The ID of the associated user story
225
+ - **Returns:** Success message indicating the agent has been dispatched
226
+
227
+ **Example Usage:**
228
+
229
+ ```
230
+ Dispatch agent for my latest suite's user story US001 and test case TC003
231
+ ```
232
+
233
+ ## Typical Workflow
234
+
235
+ 1. **Start with a suite:**
236
+
237
+ - Use `wopee_fetch_analysis_suites` to see existing suites, OR
238
+ - Use `wopee_dispatch_analysis` to create a new suite
239
+
240
+ 2. **Generate artifacts:**
241
+
242
+ - Generate app context: `wopee_generate_app_context`
243
+ - Generate user stories: `wopee_generate_user_stories` or `wopee_generate_general_user_stories`
244
+ - Generate test cases: `wopee_generate_test_cases`
245
+
246
+ 3. **Fetch generated content:**
247
+
248
+ - Use the fetch tools to retrieve generated markdown/JSON files
249
+
250
+ 4. **Run tests:**
251
+ - Use `wopee_dispatch_agent` to execute test cases with the autonomous testing agent
252
+
253
+ ## Notes
254
+
255
+ - Most tools require a `suiteUuid`. Always start by fetching or creating a suite.
256
+ - `wopee_dispatch_analysis` tool will go through whole cycle of processing - crawling the application and generating all of the artifacts one by one.
257
+ - 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/package.json CHANGED
@@ -4,7 +4,7 @@
4
4
  "bin": {
5
5
  "wopee-mcp": "./build/index.js"
6
6
  },
7
- "version": "1.2.2",
7
+ "version": "1.3.0",
8
8
  "description": "Wopee.io MCP server",
9
9
  "main": "./build/index.js",
10
10
  "scripts": {