@qualitas-id/mcp 1.2.0 → 1.2.1

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.
package/README.md CHANGED
@@ -7,7 +7,7 @@ MCP (Model Context Protocol) server for the [Qualitas](https://qualitas.id) test
7
7
 
8
8
  ## Features
9
9
 
10
- - **20 tools** for complete Qualitas platform interaction
10
+ - **22 tools** for complete Qualitas platform interaction
11
11
  - **Flow generation from scenarios** — describe a test in natural language, get a runnable flow
12
12
  - **Auto-beautify layout** — nodes are automatically arranged in clean topological order
13
13
  - **Fragment support** — create reusable flow fragments for common patterns
@@ -206,6 +206,13 @@ Add to `.vscode/mcp.json`:
206
206
  |---|---|---|
207
207
  | `extract_screenshot_text` | OCR from image URL, extract text and error messages | read-only |
208
208
 
209
+ ### Explore
210
+
211
+ | Tool | Description | Annotations |
212
+ |---|---|---|
213
+ | `explore_page` | **Explore a web page** — discover structure, forms, buttons, links, navigation, and network requests | write |
214
+ | `get_explore_results` | Get results of a previously started explore session | read-only |
215
+
209
216
  ## Flow Generation
210
217
 
211
218
  The `generate_flow_from_scenario` tool is the core feature. Describe a test scenario in natural language and get a complete, runnable flow.
@@ -241,6 +248,46 @@ Create reusable fragments for common patterns (login, registration, etc.):
241
248
 
242
249
  **Important:** Fragments MUST NOT have a `start` node. The fragment's nodes are inlined into the calling flow.
243
250
 
251
+ ## Page Exploration
252
+
253
+ The `explore_page` tool discovers what's on a web page — useful for QA testers who want to understand a page before creating test scenarios.
254
+
255
+ **What it returns:**
256
+ - Detected page type (login, dashboard, form, list, settings, etc.)
257
+ - Page headings
258
+ - Forms with fields and submit buttons
259
+ - Buttons with selectors
260
+ - Links with hrefs
261
+ - Navigation elements
262
+ - Input fields with names, types, placeholders
263
+ - Network requests (XHR/Fetch)
264
+ - Console errors
265
+
266
+ **Example — explore a public page:**
267
+
268
+ ```
269
+ explore_page(url="https://example.com", project_id="your-project-uuid")
270
+ ```
271
+
272
+ **Example — explore with login credentials:**
273
+
274
+ ```
275
+ explore_page(
276
+ url="https://app.example.com/login",
277
+ project_id="your-project-uuid",
278
+ credentials={
279
+ email: "user@example.com",
280
+ password: "secret123"
281
+ }
282
+ )
283
+ ```
284
+
285
+ **How it works:**
286
+ 1. Creates a mini test flow (navigate + optional login steps)
287
+ 2. Executes with debug mode and exploration mode enabled
288
+ 3. Captures DOM snapshot, scans all interactive elements, captures network requests
289
+ 4. Returns a structured summary of the page
290
+
244
291
  ## Docker
245
292
 
246
293
  ```bash
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@qualitas-id/mcp",
3
- "version": "1.2.0",
3
+ "version": "1.2.1",
4
4
  "description": "MCP server for Qualitas - AI-powered test automation platform",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -11,7 +11,7 @@ metadata:
11
11
 
12
12
  Use this guide when working with the Qualitas MCP server for test automation.
13
13
 
14
- ## MCP Tools Reference (20 tools)
14
+ ## MCP Tools Reference (22 tools)
15
15
 
16
16
  ### Projects
17
17
  | Tool | Description |
@@ -53,6 +53,12 @@ Use this guide when working with the Qualitas MCP server for test automation.
53
53
  | `extract_screenshot_text` | OCR from image URL, extract text and error messages |
54
54
  | `get_run_screenshot` | Get screenshot URLs for failed steps in a run |
55
55
 
56
+ ### Explore
57
+ | Tool | Description |
58
+ |------|-------------|
59
+ | `explore_page` | Explore a web page — discover structure, forms, buttons, links, navigation, network requests. Supports optional login credentials. |
60
+ | `get_explore_results` | Get results of a previously started explore session by run ID. |
61
+
56
62
  ## Fragment Rules
57
63
 
58
64
  ### CRITICAL: No Start Node in Fragments