simplify3x-connect
NPM · SIMPLIFY3X-CONNECT
SimplifyQA test management: find, author, record, run and triage test cases.
Available components
Last scanned (14 hours ago)
Scores higher than 39% of npm servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 36 of 110 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 48136 tokens (~425/item across 113 items; 113 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety98
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 15 of 16 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "suite_remove_testcases" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 114 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.31.3 → 0.31.9 functional
- 19 Nov 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- Package version: 0.31.2 → 0.31.3 functional
- 18 Nov 26 −25
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Schema quality: 36396 → 44804 ▼ functional
- Schema quality: 36396 → 44644 ▼ functional
- Dependency health: 0.85 → unverified ▼ functional
- Destructive annotations: 77% → 93% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.28.1 → 0.31.2 functional
- Package version: 0.28.1 → 0.31.1 functional
- 17 Nov 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/simplify3x-connect@0.31.9
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 110 packages
| Packages resolved | 110 |
|---|---|
| Stale | 36 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
action_template_backup Back up / verify / restore the Action catalogue (Object Templates) ~248
Protects the project's ACTIONS (the Object Template lists: WEB Click / Enter Text / … plus custom methods) against a bad "Sync Actions" run, which SimplifyQA applies server-side and can replace a template's list. - action:"save" — writes a JSON snapshot of every action (name, display name, uniqueId, template, parameters) and reports the count per template. Do this BEFORE an AI/agent sync. - action:"verify" — compares a snapshot with the live catalogue and lists the actions missing per template. Read-only. - action:"restore" — re-CREATES the missing actions from the snapshot (never deletes or edits). Dry-run by default; pass `confirm:true` to write. `snapshotPath` is returned by save and accepted by verify/restore (default: the newest snapshot of this project).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What to do. |
| confirm | boolean | – | restore: true to actually re-create the missing actions. |
| dryRun | boolean | – | restore: report only (default true). |
| snapshotPath | string | – | verify / restore: the JSON file written by save. Default: newest for this project. |
No output schema declared.
No examples provided.
actions_catalog List the offline action-type catalog ~121
Static per-platform action-type vocabulary (web/android/ios/api/database/mainframe), used for offline draft validation. No network call. NOTE mainframe is deliberately EMPTY (no source list exists), and validate.ts skips validation entirely for an empty catalog — so a clean mainframe draft means "not checked", not "checked and fine".
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | desktop: there is no offline list; on SimplifyQA the live catalog includes the DESKTOP actions (dsk-*: Launch Application, Click, Type Text, Switch to Window by Name, …). |
No output schema declared.
No examples provided.
attachment_add Attach a file/screenshot to an epic, feature, user story or defect (SimplifyQA) ~222
Upload ONE file and attach it to an existing backlog item, then read the item's attachments back to confirm it is there (it will appear in the item's Attachments section in the UI). Pass the file as a LOCAL `filePath` (preferred — e.g. the screenshot path the user shared), or as `base64` + `fileName` when only the bytes are available. Max 20 MB.
| Name | Type | Req | Description |
|---|---|---|---|
| base64 | string | – | File content as base64 (when there is no local path). Requires fileName. |
| contentType | string | – | MIME type; inferred from the extension when omitted. |
| entityType | string | yes | Which backlog item to attach to (a defect too). |
| fileName | string | – | Name to store the attachment under (default: the file's own name). |
| filePath | string | – | Absolute path of the file to upload (read on this machine). |
| itemId | string | yes | Item id or business key (EP-66, FT-266, US-1326, DE-75). |
No output schema declared.
No examples provided.
attachment_delete Remove an attachment from an epic, feature, user story or defect (SimplifyQA) ~108
Remove ONE attachment from an existing backlog item by its id or stored/original file name, then read the item's attachments back to confirm it is gone. Use it to undo a wrong upload.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment | string | yes | Attachment id, or its original/stored file name. |
| entityType | string | yes | Which backlog item the attachment belongs to. |
| itemId | string | yes | Item id or business key (EP-66, FT-266, US-1326, DE-75). |
No output schema declared.
No examples provided.
attachment_download Download an attachment of an epic, feature, user story or defect (SimplifyQA) ~301
DOWNLOAD attachments of an epic, feature, user story or defect from SimplifyQA to a local folder — fetched from SimplifyQA with the user's login (not copied from a local file). Pass `entityType` + `itemId` (EP-69, FT-269, US-1330, DE-75). If the item has ONE attachment it is downloaded; if it has SEVERAL and you pass no choice, the tool LISTS them (name, size, id) — show that list to the user and call again with `attachments` (names or ids, one or several) or `all:true`. `outDir` is the folder to save into (default "./exports"; created if missing). The answer gives each saved path, file name and size and says whether the size matches what SimplifyQA reports; an existing file is never overwritten (a " (1)" is added).
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | true = download every attachment of the item. |
| attachments | array | – | Which attachments: file names or ids (one or several). Omit to be shown the list when there is more than one. |
| entityType | string | yes | Which backlog item the attachment belongs to. |
| itemId | string | yes | Item id or business key (EP-69, FT-269, US-1330, DE-75). |
| outDir | string | – | Folder to save into. Default "./exports". |
No output schema declared.
No examples provided.
backlog_delete Delete an epic / feature / user story / defect / task ~240
DESTRUCTIVE. Delete ONE epic, feature, user story, defect or task. `ref` is the item's NAME, business key (EP_12, FT_3, US_5, DF_7 …) or numeric id — resolved here, the user never supplies an internal id. TWO-STEP: call WITHOUT `confirm` to get a preview (what will be deleted + anything that depends on it); show it to the user and ASK; only then call again with `confirm:true`. An item that still has dependents (an epic with features/stories, a feature/story with children or test cases, a defect with test cases/tasks) is REFUSED with the blockers listed — nothing cascades. An ambiguous name lists the matches and deletes nothing. Needs the user's delete permission; no agent required. Requires a live connection.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Set true ONLY after the user has seen the preview and explicitly confirmed the delete. |
| kind | string | yes | Which kind of item to delete. |
| ref | string | yes | Name, business key (EP_/FT_/US_/DF_…) or numeric id of the item. |
No output schema declared.
No examples provided.
backlog_link Link an epic / feature / user story / defect to another item (Linkages) ~229
Create a LINK between an epic, feature, user story or DEFECT and another backlog item (defect, epic, feature, story, task) — the UI's Linkages section. `linkType` is a link type name/key such as "Clones" (case-insensitive; the available types are read from the project's link-type config and an unknown one is refused with the list). `destType` is the DESTINATION issue type (e.g. "defect"). The link is saved on the SOURCE item and read back from /pm/linkages to confirm.
| Name | Type | Req | Description |
|---|---|---|---|
| destId | string | yes | Destination id or business key (DE-2293). |
| destType | string | yes | Destination issue type. |
| linkType | string | yes | Link type name or key, e.g. "Clones". |
| sourceId | string | yes | Source item id or business key (EP-64, FT-266, US-1326, DE-75). |
| sourceType | string | yes | Item that owns the Linkages section (a defect too — its Linkages section). |
No output schema declared.
No examples provided.
backlog_unlink Remove a link between two backlog items (Linkages) ~283
DELETE a LINK between two backlog items — the UI's Linkages delete (the opposite of backlog_link). Pass the item that owns the link (`sourceType` + `sourceId`, e.g. epic EP-71) and the item it points to (`destType` + `destId`, e.g. defect DE-2293). If the source has more than one link to that item, say which with `linkType` (e.g. "Clones"). The link disappears from BOTH items' Linkages; the tool reads the source's Linkages back to confirm and checks the other side too. A link that is not there is reported with the links the source does have. Deleting is final — call it only when the user asked to remove the link.
| Name | Type | Req | Description |
|---|---|---|---|
| destId | string | yes | The linked item's id or business key (DE-2293). |
| destType | string | yes | The linked item's type. |
| linkType | string | – | Link type name or key (e.g. "Clones") — needed only when the source has several links to that item. |
| sourceId | string | yes | Source item id or business key (EP-71, FT-266, US-1326, DE-2293, TA-3). |
| sourceType | string | yes | Item type that owns the Linkages row. |
No output schema declared.
No examples provided.
cloud_runners List cloud runners (and which are online) ~51
List the cloud runner VMs registered to the connected project and which are online. Use this to show the user the cloud options, or to pick a specific runner id for tc_run. Requires a live connection.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
column_preference Read or change list-view COLUMN preferences (SimplifyQA) ~250
Read or change which columns a LIST VIEW shows for THIS user — the same write as ticking a column in the UI's Column Preference menu. Supported lists: epic, feature, userstory, testcase (Test Case list), suite (Suite test-case list), scenario (Test plan test-case list) and executionplan (Execution Plan test-case list, including "Execution Type"). action "get" returns the visible column keys of each list; action "set" enables or disables `column` (a label like "Execution Type", or its key like "executionType") on every list in `lists`, then reads the preferences back to confirm. The change applies to the UI after a refresh.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | get = read visible columns; set = enable/disable a column. |
| column | string | – | action "set": column LABEL ("Created On") or key ("createdAt"). |
| enabled | boolean | – | action "set": true to show the column (default), false to hide it. |
| lists | array | yes | Which list views to touch. testcase = Test Cases; suite = Suite test cases; scenario = Test plan test cases; executionplan = Execution Plan test cases. |
No output schema declared.
No examples provided.
create_module Create a module (folder), optionally with a nested subtree, in the test-case tree ~274
Create a new MODULE under the connected project. Set `isRoot:true` for a top-level folder; otherwise pass `parentId` (resolve via list_modules). To create a WHOLE HIERARCHY in one call (root + submodules + nested submodules), pass a `children` array — each child gets `isRoot:false` and its parentId auto-wired from the tree position (do NOT set `isRoot`/`parentId` on child nodes). Duplicate name in the same project is rejected server-side. On mid-subtree failure the response carries `failedAt`; every node before it is already persisted (no transactional rollback upstream). SimplifyQA-only. Requires a live connection.
| Name | Type | Req | Description |
|---|---|---|---|
| children | array | – | Optional subtree under this module. Each child = { name, description?, children? } — no isRoot/parentId (derived). |
| description | string | – | Free-text description. |
| isRoot | boolean | yes | True → top-level folder; false → child of `parentId`. |
| name | string | yes | Module name. Must be unique within the project. |
| parentId | string | – | Parent module id (required when isRoot is false; MUST be omitted when isRoot is true). |
| projectId | string | yes | Target project id (see list_projects). |
No output schema declared.
No examples provided.
defect_create Log a defect (create) ~827
Log a new DEFECT in the connected project — what Defect Management → Create Defect does — and return its key (DE-xx). Only `name` is required; state and priority default to the project's own default values, and the answer lists what was defaulted. Optional: `description`, `severity`, `category` (the project's own values; an unknown one is refused with the valid ones listed), `assignee` (email, name, user id or "me"), `releaseId` / `sprintId` (id, code or name), `storyId` (the USER STORY field: id or key, e.g. US-25), `testCases` (the TEST CASE field: "TC-41" or "TC-41:v1.0" — the test case then lists the defect, checked after saving), `module` (default: the project's Default module), `estimatedEffort`, `customFields` ({ key: value } — needed when the project marks custom fields mandatory), and the rest of the form: `environment`, `executionType` (alias `type`: Manual / Automation), `featureId`, `plannedStartDate` / `plannedEndDate` (YYYY-MM-DD), `linkages` ([{ destType, destId, linkType }], saved from the defect's side) and `attachments` ([{ filePath }]). Environment / Type are checked against the project's own list (or the form's: Development / QA / UAT, Manual / Automation); a bad value refuses the call before anything is created. A defect with the same name is refused. Reads the defect back. Needs the add_defect privilege. To log a defect FROM a failed execution step (evidence pre-filled), use defect_create_from_step instead; to change one later, defect_update.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | – | Email, name, numeric user id or "me". Default: unassigned. |
| attachments | array | – | ATTACHMENTS: files to attach to the defect (max 20 MB each). To remove or download one later: attachment_delete / attachment_download with entityType "defect". |
| category | string | – | – |
| customFields | object | – | Custom field values { "<field key>": value }. |
| description | string | – | – |
| environment | string | – | ENVIRONMENT: one of the project's own list, or the form's (Development, QA, UAT). An unknown value is refused with the valid ones. |
| estimatedEffort | number | – | – |
| executionType | string | – | TYPE (the form's Execution Type): Manual or Automation (or the project's own list). |
| featureId | string | – | FEATURE: a feature of this project — id, business key (FT-248) or exact name. |
| linkages | array | – | LINKAGES, saved from the DEFECT's side (the form's Linkages section). A link that already exists is left as it is. |
| module | string | – | Module name, code or id. Default: the project's Default module. |
| name | string | yes | Defect name (3–500 characters). |
| plannedEndDate | string | – | PLANNED END DATE, YYYY-MM-DD, on or after the start. |
| plannedStartDate | string | – | PLANNED START DATE, YYYY-MM-DD. |
| priority | string | – | – |
| releaseId | string | – | Release: id, code (RE-44) or exact name. |
| severity | string | – | – |
| sprintId | string | – | Sprint: id, code (SP-1) or exact name; it must belong to the release. |
| state | string | – | – |
| storyId | string | – | USER STORY field: story id or key (US-25). |
| testCases | array | – | TEST CASE field: "TC-41" or "TC-41:v1.0". |
| type | string | – | Same as executionType — the form's TYPE field. |
No output schema declared.
No examples provided.
defect_create_from_step Log a defect from a failed execution step ~400
Log a DEFECT from a FAILED step of an execution — what "Log Defect" in the execution report does — and link it to that step. Pass `executionId` (EX-170 or 170) and `step` (the step number in the report; it must have failed). If the execution ran several test cases, also pass `tc`. The defect is pre-filled from the report: test case + version, steps to replicate up to the failure, execution, environment, browser, expected vs actual and the error message, and the step's screenshots; its release / sprint / module come from the execution / test case. Optional: `name` (default "TC-41 step 7 failed: … (EX-170)"; a defect with that name already existing is refused — link it with defect_link_step instead), `description` (extra notes), `state` / `priority` / `severity` (the project's own values, default = the project's defaults), `assignee` (email, name, user id or "me"). Needs the add_defect privilege. Returns the defect key (DE-xx); the test case then lists it too. To attach a step to a defect that already exists, use defect_link_step.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | – | Email, name, numeric user id or "me". |
| description | string | – | Extra notes added to the defect description. |
| executionId | string | yes | Execution id or code: EX-170 or 170. |
| name | string | – | Defect name (3–500 characters). |
| priority | string | – | – |
| severity | string | – | – |
| state | string | – | – |
| step | integer | yes | Step number as shown in the report; it must be a FAILED step. |
| tc | string | – | Test case id or code (TC-41) — only when the execution ran several test cases. |
No output schema declared.
No examples provided.
defect_link_step Link a failed execution step to an existing defect ~239
Link a FAILED step of an execution to a defect that ALREADY EXISTS (e.g. DE-60) — what "link defect" on the report step does — and make sure the step's test case + version is on the defect's TEST CASE field, so the link shows from the defect, the test case and the execution report. Pass `executionId` (EX-170 or 170), `step` (must have failed) and `defectId` (id, code or exact name); `tc` only when the execution ran several test cases. Linking a step that is already linked changes nothing. To create a new defect from the step, use defect_create_from_step.
| Name | Type | Req | Description |
|---|---|---|---|
| defectId | string | yes | The existing defect: id, code (DE-60) or exact name. |
| executionId | string | yes | Execution id or code: EX-170 or 170. |
| step | integer | yes | Step number as shown in the report; it must be a FAILED step. |
| tc | string | – | Test case id or code (TC-41) — only when the execution ran several test cases. |
No output schema declared.
No examples provided.
defect_update Update a defect (state, assignee, environment, type, feature, dates, linkages, attachments, …) ~862
Change an existing DEFECT the way the SimplifyQA defect form does, then READ IT BACK and report each change. Pass `defectId` (id, code like DE-61, or exact name) and only what to change: - `storyId` — the form's USER STORY field (story id or key, e.g. US-25; "none" clears it). This is NOT a Linkages row. - `testCases` — the form's TEST CASE field: test cases to ADD, each "TC-41" or with its version "TC-41:v1.0" (no version = the test case's current one, and the answer says which). The defect then shows in each test case's linked defects — checked after saving. `removeTestCases` takes some out; `clearTestCases:true` empties the field. - `state`, `priority`, `severity` (the project's own values; an unknown one is refused with the valid ones listed), `assignee` (email, name, user id or "me") or `unassign:true`, `releaseId` / `sprintId` (id, code or name; "none" clears), `name`, `description`. - `environment`, `executionType` (alias `type`), `featureId`, `plannedStartDate`, `plannedEndDate` — the rest of the form ("none" clears one). Environment / Type are checked against the project's own list (or the form's: Development / QA / UAT, Manual / Automation). - `linkages` — LINKAGES saved from the defect's side: [{ destType, destId, linkType }]. - `attachments` — files to attach to the defect ([{ filePath }]). Needs the add_defect privilege.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | – | Email, name, numeric user id or "me". |
| attachments | array | – | ATTACHMENTS: files to attach to the defect (max 20 MB each). To remove or download one later: attachment_delete / attachment_download with entityType "defect". |
| clearTestCases | boolean | – | true = empty the TEST CASE field. |
| defectId | string | yes | Defect id, code (DE-61) or exact name. |
| description | string | – | – |
| environment | string | – | ENVIRONMENT: one of the project's own list, or the form's (Development, QA, UAT). An unknown value is refused with the valid ones. |
| executionType | string | – | TYPE (the form's Execution Type): Manual or Automation (or the project's own list). |
| featureId | string | – | FEATURE: a feature of this project — id, business key (FT-248) or exact name. |
| linkages | array | – | LINKAGES, saved from the DEFECT's side (the form's Linkages section). A link that already exists is left as it is. |
| name | string | – | New name (at least 3 characters). |
| plannedEndDate | string | – | PLANNED END DATE, YYYY-MM-DD, on or after the start. |
| plannedStartDate | string | – | PLANNED START DATE, YYYY-MM-DD. |
| priority | string | – | – |
| releaseId | string | – | Release: id, code (RE-44) or exact name; "none" clears it (and the sprint). |
| removeTestCases | array | – | Test cases to take out of the TEST CASE field. |
| severity | string | – | – |
| sprintId | string | – | Sprint: id, code (SP-1) or exact name; it must belong to the defect's release. "none" clears it. |
| state | string | – | – |
| storyId | string | – | USER STORY field: story id or key (US-25); "none" clears it. |
| testCases | array | – | TEST CASE field — test cases to add: "TC-41" or "TC-41:v1.0". |
| type | string | – | Same as executionType — the form's TYPE field. |
| unassign | boolean | – | true = clear the assignee. |
No output schema declared.
No examples provided.
delete_function Delete a reusable function (NOT a test case; two-step confirm) ~200
Soft-delete a reusable FUNCTION in the connected product. NOT for test cases: if the user asks to delete a TC or TC_* id, use `tc_delete` instead. Trigger words for THIS tool: "function", "FN_", "reusable function". TWO-STEP CONFIRM: call once with just `id` to preview the target (name + step count) and get a warning; then call again with `{ id, confirm: true }` to actually delete. Refuses to delete without `confirm:true`. `id` accepts the function's numeric id or business key. The backend refuses to delete a function that is still referenced by a test case, another function, or a workflow — this tool surfaces those references so the user can remove them first.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Set to true on the SECOND call to actually delete. |
| id | string | yes | The function id (or business key like FN_123) to delete. |
No output schema declared.
No examples provided.
delete_module Delete modules (with dependency dry-run) ~154
Delete one or more MODULES by id. Two phases: call with `confirm:false` (default) for a DRY RUN that returns each id's dependency footprint (test cases, functions, parameters, objects, defects, user stories that still reference the module). Call again with `confirm:true` to actually delete; the server drops only ids with EMPTY dependencies and silently skips the rest — surface those to the caller so they can move/remove the refs first. SimplifyQA-only. Requires a live connection.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | False (default) → dry-run; true → apply delete. |
| ids | array | yes | Module ids to delete. |
| projectId | string | yes | Project id the modules belong to. |
No output schema declared.
No examples provided.
delete_version Delete a version of a test case or function (two-step confirm) ~369
Soft-delete ONE version of a test case (`kind:"tc"`) or a reusable function (`kind:"fn"`) in the connected product. `versionId` comes from the parent's `versions[]` (populated by `tc_get` for TCs and `get_function` for FNs); pass the version's `name` too (backend validator requires it). TWO-STEP CONFIRM: call once with `confirm:false` (default) to get a DRY RUN — the response lists every entity still referencing this version (defects, suites, exec plans, scenarios, schedulers, pipelines, workflows for a TC; TCs, other FNs, workflows for a FN). Only when EVERY dependency map is empty is the delete allowed; the server itself REFUSES a `confirm:true` call when refs still exist, so `confirm:true` doesn't guarantee deletion — the tool inspects the response and reports honestly. Refuses to delete the LAST remaining version (the parent would be orphaned; use `tc_delete` / `delete_function` instead to remove the whole entity). SimplifyQA-only. Requires a live connection.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | False (default) → dry-run; true → apply delete (server still refuses if any dependency exists). |
| kind | string | yes | 'tc' for a test-case version; 'fn' for a function version. |
| parentId | string | yes | Parent TC or FN id (numeric or business key like TC_123 / FN_45). |
| versionId | string | yes | The version's uuid (from tc_get.versions[].id or get_function.versions[].id). |
| versionName | string | yes | The version's human name (e.g. 'v1.0'). Required by the backend validator. |
No output schema declared.
No examples provided.
environment_manage Create, update or delete a project environment (SimplifyQA) ~296
Manage the project's ENVIRONMENTS (project configuration > Environments, next to General). - action:"create" — needs `name` (optional `key`, else generated exactly like the UI). Refused when that name already exists. - action:"update" — needs `environment` (current name or key) and the new `name` and/or `key`. - action:"delete" — needs `environment`. TWO-STEP: the first call only previews; call again with `confirm:true` ONLY after the user explicitly says to delete (the default General environment is refused). Every write posts the WHOLE environment list to `/pm/fields/savefields`, exactly as the UI does, and is read back to confirm. A saved environment is selectable for executions, schedules, pipelines and execution plans, and the product provisions its own test data. List them with `sqa_query collection:"environments"`.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What to do. |
| confirm | boolean | – | delete: true on the SECOND call, only after the user explicitly said to delete. |
| environment | string | – | update / delete: the existing environment, by name or key. |
| key | string | – | Optional environment key (used as `environmentType` in test data). Generated when omitted on create. |
| name | string | – | create: the environment name (required). update: the NEW name (optional if only the key changes). |
No output schema declared.
No examples provided.
epic_create Create an epic ~868
Create a new EPIC in the connected project. `projectIds` defaults to the current project when omitted. `state` defaults to the project-configured default state when omitted; pass it only when overriding (must match an existing state in the project config — see epic_list / epic_get). Backend requires `name`, `estimatedEffort`, `plannedStartDate`, `plannedEndDate`. **`description` must be a DETAILED epic write-up as HTML (NOT markdown) derived from the source document (BRD, spec, user request). SQA UI renders this via a Tiptap editor and stores raw HTML — see the description field docstring for the exact allowed tags and required section structure. One-line summaries are not acceptable.** `customFields` may be omitted — an empty object is sent automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| actualEffort | number | – | – |
| actualEndDate | string | – | – |
| actualStartDate | string | – | – |
| customFields | object | – | Optional. Empty object `{}` sent automatically when omitted. |
| description | string | – | REQUIRED-QUALITY: rich HTML write-up sourced from the BRD/spec. NOT markdown — the SQA UI renders this through a Tiptap editor and stores the raw HTML string. Minimum 300 words when a BRD is availa… |
| estimatedEffort | number | yes | Estimated effort (hours). |
| name | string | yes | Epic name (3–500 chars). |
| ownerId | number | – | Numeric userId of the epic owner. |
| plannedBudget | number | – | – |
| plannedEndDate | string | yes | ISO date/datetime for planned end. |
| plannedStartDate | string | yes | ISO date/datetime for planned start. |
| projectIds | array | – | Project ids the epic belongs to. Defaults to [currentProject]. |
| remainingEffort | number | – | – |
| state | string | – | Optional. Defaults to the project-configured default epic state when omitted. |
| tags | array | – | – |
| teamId | array | – | – |
| watchList | array | – | Watch List (the UI email button): emails, full names or numeric userIds to receive notifications. Applied after creation. |
No output schema declared.
No examples provided.
epic_update Update an epic (partial) ~226
PATCH an existing EPIC — pass only the fields to change plus `updateVersion` (optimistic concurrency, from the last epic_get). Accepts id or business key (EP_123). Cannot rename the epic to a duplicate of another epic in the same customer.
| Name | Type | Req | Description |
|---|---|---|---|
| actualEffort | number | – | – |
| actualEndDate | string | – | – |
| actualStartDate | string | – | – |
| customFields | object | – | – |
| description | string | – | – |
| estimatedEffort | number | – | – |
| id | string | yes | Epic id or business key (EP_123). |
| name | string | – | – |
| ownerId | number | – | – |
| plannedBudget | number | – | – |
| plannedEndDate | string | – | – |
| plannedStartDate | string | – | – |
| projectIds | array | – | – |
| remainingEffort | number | – | – |
| state | string | – | – |
| tags | array | – | – |
| teamId | array | – | – |
| updateVersion | number | – | Optimistic-concurrency version from the last read. |
No output schema declared.
No examples provided.
excel_import Import test cases / test data / plan entries from a spreadsheet (.xlsx, .csv, .tsv) ~394
Bulk-import a spreadsheet into SimplifyQA — the MCP equivalent of the UI's Import. `kind:"testcases"` — one MANUAL test case per row. Recognised headers (case/spacing-insensitive): `name`/`title` (required), `description`, `steps` (one step per line, or `|` separated), `expected result`, `module`, `story`/`userstory`, `prerequisites`. A step column is prose, so the imported cases are MANUAL (automation needs real locators — record those). `kind:"testdata"` — one ITERATION per row for ONE test case: needs `tcId` + `environmentType`; every column is a parameter name (matched case-insensitively). `kind:"plan_entries"` — the first column is a test case code/id; needs `planId` (execution plan). Reports what was created / added and every rejected row with its reason. `dryRun:true` parses + reports without writing. The first row is the header unless `headerRow:false`.
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | Parse and report only — nothing is written. |
| environmentType | string | – | testdata: env key from tc_list_environments (required). |
| filePath | string | yes | Absolute path to the .xlsx / .csv / .tsv file on this machine. |
| headerRow | boolean | – | Treat the first row as headers (default true). |
| kind | string | yes | What to import. |
| module | string | – | testcases: default module/folder id or name for rows without a module column. |
| planId | string | – | plan_entries: the execution plan id/code. |
| storyRef | string | – | testcases: default user story id/code for rows without a story column. |
| tcId | string | – | testdata: the target test case (id or code). |
No output schema declared.
No examples provided.
execution_plan Create, update or delete an execution plan (SimplifyQA) ~1,620
Manage SimplifyQA execution plans. Read plans with sqa_query (collection "executionPlans"). Pick ONE `action`: - action:"create" — needs `name`, `plannedStartDate`, `plannedEndDate` (YYYY-MM-DD) and `environment` (name or key; see sqa_query collection "environments"). Optional: releaseId, sprintId, teamIds, planners, autoReExecCount, autoReExecTriggerOn, autoDefectLog, newBrowserSession, terminateOnFailure. - action:"update" — needs `planId` and at least one field to change (same fields as create). AUTO DEFECT LOGGING for the plan = `autoDefectLog:true` (create or update): failed steps then log a defect automatically. It needs the project's admin "Auto Defect Logging" switch on; if it is off the call is refused with that instruction — tell the user to ask an admin to enable it, then retry. - action:"delete" — needs `planId`. TWO-STEP: call without `confirm` to PREVIEW (nothing is deleted; it states what is permanently lost), show it to the user, and call again with `confirm:true` ONLY after the user explicitly says to delete. - action:"add_testcases" - needs `planId` and `tcIds`, `testCases` and/or `suiteIds` (a suite adds its test cases). Optional `assignTo` (user id or "me") and `assignDate` (YYYY-MM-DD); only assigned test cases can run. To pin a VERSION pass `testCases:[{ tcId:"TC-12826", version:"v2.0" }]` (or `versionId`, or one `versionId`/`version` for every `tcIds` entry) — the same test case can sit in the plan once per version, so v1.0 and v2.0 are two entries. A version that does not exist is an ERROR; a duplicate (same test case AND version) is skipped. - action:"remove_testcases" — needs `planId` and `tcIds`. TWO-STEP like delete: removing also DELETES those test cases' run history in SimplifyQA, which cannot be undone. - action:"stack_setup" — needs `planId` and `stacks` (how many, e.g. 2) or `stackConfigs`. Saves the Stack Setup (what the Stack canvas saves). Give `stacks` (a number: that many alike, test cases spread round-robin) OR `stackConfigs`…
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What to do. |
| agentId | string | – | run: this machine's agent id (optional; auto-picked, see local_agents). |
| append | boolean | – | stack_setup: add the stack(s) to the saved setup instead of replacing it. |
| assignDate | string | – | add_testcases: YYYY-MM-DD. |
| assignTo | string | – | add_testcases: user id, or "me". |
| autoDefectLog | boolean | – | create/update: log a defect automatically when a step fails (needs the project's admin Auto Defect Logging switch on). |
| autoReExecCount | integer | – | create/update. |
| autoReExecTriggerOn | string | – | create/update. |
| browser | string | – | stack_setup: browser for WEB test cases (default chrome). run, mode "cloud": the browser for the plan's web test cases — ONLY Chrome Headless, Firefox Headless or Edge Headless (pass chrome / firefox… |
| confirm | boolean | – | delete: true on the SECOND call, only after the user explicitly said to delete. |
| environment | string | – | create/update: environment name or key. |
| mode | string | – | run: "local" (this machine's agent), "cloud" (a configured cloud machine), or "stack" (the saved stack setup, divided across its stacks). |
| name | string | – | create/update: plan name (unique in the project). |
| newBrowserSession | boolean | – | create/update. |
| planId | string | – | Every action except create: plan id or code (PL-5). |
| plannedEndDate | string | – | create/update: YYYY-MM-DD, on or after the start. |
| plannedStartDate | string | – | create/update: YYYY-MM-DD. |
| planners | array | – | create/update: planner user ids. |
| releaseId | string | – | create/update: release id. |
| sprintId | string | – | create/update: sprint id (needs a release). |
| stackConfigs | array | – | stack_setup: describe each stack, in order — one entry per stack (this sets the number of stacks; leave `stacks` out or make it match). E.g. [{ mode:"local" }, { mode:"cloud" }, { mode:"remote", agen… |
| stackMode | string | – | stack_setup: what each stack runs on (default cloud). |
| stacks | integer | – | stack_setup: how many stacks (e.g. 2) — with append:true, how many to ADD. Omit when stackConfigs lists them. |
| suiteIds | array | – | add_testcases: suites whose test cases to add. |
| tcIds | array | – | add_testcases / remove_testcases: test case ids or codes. |
| teamIds | array | – | create/update: team ids. |
| terminateOnFailure | boolean | – | create/update. |
| testCases | array | – | add_testcases: test cases with an explicit version — lets one TC be added once per version (v1.0 AND v2.0). |
| version | string | – | add_testcases: pin one version by NAME for every tcIds entry (e.g. v2.0). |
| versionId | string | – | add_testcases: pin ONE version for every tcIds entry (id or name `version`). Omit = current version. |
| when | string | – | run: only "immediate" — execution plans cannot be scheduled in SimplifyQA. |
No output schema declared.
No examples provided.
failure_analysis Analyse failed SimplifyQA test cases, suites or execution plans ~996
Analyse FAILED SimplifyQA executions — test cases, suites, execution plans — together. ANALYSE: `codes` (TC-123 / SU-123 / PL-123, each → its latest execution) and/or `executionIds` (id or EX code); `code` / `executionId` work too. Returns an `analysisId` (FA-…), a card (scope, failures by category with counts and %, patterns, failed test cases) and evidence per pattern. VIEW: pass `analysisId` (no re-fetch) with `view` ("consolidated" | "suite"), `suiteId`, `pattern` (n or [n,…]), `category` or `page`. REVIEW: `{ analysisId, review: true, page? }` — every failed test case, as many per page as fit 18 images: its failed step and the same step in the last pass at the same detail (expected / actual, test data, full API, locator, logs), with every screenshot of both steps, the baseline of both runs and the element thumbnail. Images: the failed screenshot is this run. The baseline is the execution-time reference page with the target element boxed in red. The thumbnail is the target element as recorded. Same page as the baseline but the element missing or different from the thumbnail means the element or locator changed. A different page (error, blank, another screen) means the flow did not reach it. Recorded images show recording-time data: compare layout and element, not values. Do this, in order: (1) Read the card and the evidence. (2) Page the remaining groups with `pattern:[…]` exactly as the card's "Next:" line says, until every pattern's evidence has been read. (3) Review every failed test case with `review: true`, following its "Next:" line until done: compare the last passed step with the failed step (data, API, locator, logs, version, every image) and state what changed and what stayed the same. (4) Call `failure_analysis_classify` ONCE with a verdict for ALL groups (`splitOut` test cases whose review shows another cause; `mergeInto` groups that share one). (5) Reply starting with the classified card exactly as returned (same tables and rows, never reworded),…
| Name | Type | Req | Description |
|---|---|---|---|
| analysisId | string | – | VIEW an existing analysis (FA-…) instead of analysing again. |
| category | string | – | With analysisId: only this category. |
| code | string | – | One code (same as codes:[code]). |
| codes | array | – | TC-123 / SU-123 / PL-123 — each analysed at its latest execution. |
| compareWithLastPass | boolean | – | Compare each pattern's failure with the last pass (default true). |
| executionId | string | – | One execution id or EX code (same as executionIds:[id]). |
| executionIds | array | – | Execution ids or EX codes — only these executions. |
| includeImages | boolean | – | Return failed / last-passed screenshot pairs for the patterns shown as inline images (default true; analyse and view). Set false for text only. |
| includeLogs | boolean | – | Include execution logs (default true). |
| includeScreenshots | boolean | – | Include screenshot artifact URLs (default true). |
| maxLogLines | integer | – | Cap logs per step — the lines nearest the failure are kept (default 30). |
| page | integer | – | With analysisId: page of the groups list (or of the review with review:true). |
| pattern | – | – | With analysisId: these pattern groups, with full evidence. |
| review | boolean | – | With analysisId: review EVERY failed test case, as many per page as fit 18 images (failed step vs the last pass, with every image of both). Follow its "Next:" line until done. |
| runId | string | – | Same as executionId (kept for older calls). |
| suiteId | string | – | With analysisId: only this suite (SU-12 or 12). Without it: same as code SU-<id>. |
| tcId | string | – | Test case id — same as code TC-<id>. |
| view | string | – | View: one list (default) or per suite. |
No output schema declared.
No examples provided.
failure_analysis_classify Record verdicts for a failure analysis ~351
Record your verdict for EVERY pattern group of a failure analysis, in ONE call, after reading the evidence of all of them (page unseen groups with failure_analysis({ analysisId, pattern: [...] }) first — a group whose evidence was never shown is rejected) and reviewing every failed test case with failure_analysis({ analysisId, review: true }). Use `splitOut` for test cases whose review shows a different cause and `mergeInto` for groups that share a root cause. An incomplete review is accepted; the card then says how many test cases were reviewed. The MCP applies merges / splits, recomputes counts and %, and returns the classified card: start your reply with it exactly as returned. Calling again overwrites a group's verdict. Changes only this MCP's memory — nothing is written to SimplifyQA. Categories: APP_DEFECT — the application does something wrong with an unchanged test and unchanged data. NEW_CHANGE — the application changed on purpose (screen, label, flow, rule or expected value), so the test is now outdated. AUTOMATION_DATA — script, locator, timing/synchronisation, test data, configuration, environment/device, or a manual stop.
| Name | Type | Req | Description |
|---|---|---|---|
| analysisId | string | yes | Id from failure_analysis (FA-xxxxxxxx). |
| verdicts | array | yes | One entry per pattern group: { group, pattern (short name), rootCause (one or two sentences, from the evidence), category (APP_DEFECT | NEW_CHANGE | AUTOMATION_DATA), confidence (high | medium | low)… |
No output schema declared.
No examples provided.
failure_analysis_export Export a failure analysis to Excel / PDF ~402
Write the official report files for a stored failure analysis (from `failure_analysis`): Excel (`xlsx`) and/or PDF (`pdf`), plus `analysis.json`. Pass the `analysisId` it returned and the `format`. Optional filters (`suiteId`, `pattern`, `category`, `view`) are applied to every file. Files are saved under `outDir` (default ./qa-reports) and their paths returned. Protected test data is masked as ***. Optional `layout` reshapes the report to what the user asked for: `title`, `sections` (summary is always kept; order is fixed), test-case `columns` in the wanted order (keys: patternNo, source, code, name, iteration, failedStep, expected, actual, pattern, category, reason, lastPassed, failingSince, editedSincePass, report, screenshot, lastPassedScreenshot, baseline; code is always included), `groupBy` (pattern | source | category), `sortBy` (pattern | code | failingSince | lastPassed | category), and up to 5 `extraColumns` ({ header, values: { "<test case code>": "<text>" }, default? }) — fill extra values only from evidence you reviewed. Counts and percentages are always computed by the server. Omit `layout` for the standard report; a custom layout gets its own file name.
| Name | Type | Req | Description |
|---|---|---|---|
| analysisId | string | yes | Id from failure_analysis (FA-xxxxxxxx). |
| category | string | – | – |
| format | array | yes | Which files to write: "xlsx", "pdf" or both. |
| layout | object | – | Customise the report to the user request. Omit for the standard report. |
| outDir | string | – | Folder to save into. Default: ./qa-reports |
| pattern | – | – | Only these pattern ids. |
| suiteId | string | – | Only this suite. |
| view | string | – | – |
No output schema declared.
No examples provided.
feature_create Create a feature ~981
Create a new FEATURE. `projectIds` defaults to the current project when omitted. **HIERARCHY — ALWAYS RESOLVE BEFORE CALLING.** Features live under Epics. Before calling this tool, confirm with the user which `epicId` this feature belongs to. If the user has not told you: (1) ask them directly, or (2) if they name an epic, resolve the id via `epic_list`. When creating MULTIPLE features from a BRD, group them under the correct epic — do not scatter them. Skip epic linking only if the user explicitly says "no epic" or "standalone feature". `state` and `priority` default to the project-configured defaults when omitted; pass them only when overriding. Backend requires `name`, `estimatedEffort`, `plannedStartDate`, `plannedEndDate`. **`description` must be a DETAILED feature write-up as HTML (NOT markdown) — SQA UI renders it via a Tiptap editor. See the description field docstring for the exact allowed tags and required section structure. One-line summaries are not acceptable.** `customFields` may be omitted — an empty object is sent automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| actualEffort | number | – | – |
| actualEndDate | string | – | – |
| actualStartDate | string | – | – |
| customFields | object | – | Optional. Empty object `{}` sent automatically when omitted. |
| description | string | – | REQUIRED-QUALITY: rich HTML write-up sourced from the BRD/spec. NOT markdown — the SQA UI renders through a Tiptap editor and stores raw HTML. Minimum 250 words when the BRD covers this feature; NE… |
| epicId | number | – | Parent epic numeric id. RESOLVE VIA `epic_list` OR ASK THE USER before creating — do not leave a feature parent-less unless the user explicitly says "no epic". |
| estimatedEffort | number | yes | – |
| name | string | yes | – |
| orphan | boolean | – | Set true ONLY if the user has explicitly said the feature has no parent epic ("standalone", "no epic"). Required when `epicId` is omitted — the tool refuses otherwise. |
| ownerId | number | – | – |
| plannedEndDate | string | yes | – |
| plannedStartDate | string | yes | – |
| priority | string | – | Optional. Defaults to the project-configured default feature priority when omitted. |
| projectIds | array | – | – |
| remainingEffort | number | – | – |
| state | string | – | Optional. Defaults to the project-configured default feature state when omitted. |
| tags | array | – | – |
| teamId | array | – | – |
| watchList | array | – | Watch List (the UI email button): emails, full names or numeric userIds to receive notifications. Applied after creation. |
No output schema declared.
No examples provided.
feature_update Update a feature (partial) ~208
PATCH an existing FEATURE — pass only the fields to change plus `updateVersion` (optimistic concurrency, from the last feature_get). Accepts id or business key (FT_123).
| Name | Type | Req | Description |
|---|---|---|---|
| actualEffort | number | – | – |
| actualEndDate | string | – | – |
| actualStartDate | string | – | – |
| customFields | object | – | – |
| description | string | – | – |
| epicId | number | – | – |
| estimatedEffort | number | – | – |
| id | string | yes | Feature id or business key (FT_123). |
| name | string | – | – |
| ownerId | number | – | – |
| plannedEndDate | string | – | – |
| plannedStartDate | string | – | – |
| priority | string | – | – |
| projectIds | array | – | – |
| remainingEffort | number | – | – |
| state | string | – | – |
| tags | array | – | – |
| teamId | array | – | – |
| updateVersion | number | – | – |
No output schema declared.
No examples provided.
fn_clone Save a reusable function as a new function (same project + module) ~487
FOR REUSABLE FUNCTIONS ONLY. NOT for test cases: if the user names a `TC_*` key or asks to clone a test case / scenario / script, use `tc_clone` instead. Trigger words for THIS tool: "function", "reusable function", "FN_", "FN-". Save an existing reusable FUNCTION as a NEW function (new FN id) in the SAME project + module. Mirrors the FE in-editor "Save as new function" dialog (operation: SAVEASNEWFN). Clones ONE source version — pass `sourceVersionId` to pick which; defaults to the FN's newest version. `fnId` accepts the numeric id or business key (`FN_*`). `newName` is REQUIRED — backend rejects an empty name on SAVEASNEWFN. TESTDATA — TWO-STEP: call once WITHOUT `tdCopy` to get the "Copy Test Data" prompt and confirm with the user; then call again with `tdCopy` set. Mirrors the FE's "COPY TEST DATA" modal (Cancel = false, Confirm = true). The tool REFUSES to clone until `tdCopy` is passed — the prompt step is not skippable. `tdCopy:true` clones the source version's testdata iterations across every environment. `tdCopy:false` copies only the column STRUCTURE — one empty iteration (`ITR-1`) per environment; cells fall back to each parameter's project-level `defaultValue` if any. Requires a live connection.
| Name | Type | Req | Description |
|---|---|---|---|
| fnId | string | yes | The source function id or business key (e.g. FN_123). |
| newName | string | yes | Name for the new function (required by backend). |
| sourceVersionId | string | – | Which version of the source FN to clone; defaults to the FN's newest version. |
| sourceVersionName | string | – | Version to use, by NAME/number as the user says it (e.g. "v2", "2"). Preferred over sourceVersionId — the user should never need an id. If the source has several versions and this is omitted, the too… |
| tdCopy | boolean | – | REQUIRED to actually clone. Whether to clone the source version's testdata iterations. Omit on the first call to get the confirmation prompt; ask the user, then call again with the chosen value. |
No output schema declared.
No examples provided.
fn_save_as_new_version Snapshot a reusable function as a new version ~505
FOR REUSABLE FUNCTIONS ONLY. NOT for test cases: if the user names a `TC_*` key or asks to snapshot / create a new version of a test case, use `tc_save_as_new_version` instead. Trigger words for THIS tool: "function", "reusable function", "FN_", "FN-". Freeze the CURRENT server state of a reusable FUNCTION under a NEW version name — same FN id, a new version row with cloned steps. Mirrors the SimplifyQA UI "Save as new version" dialog (operation: SAVENEWVERSION, type: FN). `fnId` accepts the numeric id or business key (`FN_*`). `versionName` must be unique for this FN — the backend rejects duplicates. TESTDATA — TWO-STEP: call once WITHOUT `tdCopy` to get the "Copy Test Data" prompt and confirm with the user; then call again with `tdCopy` set. Mirrors the FE's "COPY TEST DATA" modal (Cancel = false, Confirm = true). The tool REFUSES to snapshot until `tdCopy` is passed — the prompt step is not skippable. `tdCopy:true` clones the source version's testdata iterations across every environment. `tdCopy:false` copies only the column STRUCTURE — one empty iteration (`ITR-1`) per environment; cells fall back to each parameter's project-level `defaultValue` if any. `sourceVersionId` picks which version to snapshot; omit to snapshot the FN's newest version (the FN doc has no inline current-version marker). Requires a live connection.
| Name | Type | Req | Description |
|---|---|---|---|
| fnId | string | yes | The function id or business key (e.g. FN_123). |
| sourceVersionId | string | – | Version to snapshot; defaults to the FN's newest version. |
| sourceVersionName | string | – | Version to use, by NAME/number as the user says it (e.g. "v2", "2"). Preferred over sourceVersionId — the user should never need an id. If the source has several versions and this is omitted, the too… |
| tdCopy | boolean | – | REQUIRED to actually snapshot. Clone testdata iterations from the source version. Omit on the first call to get the confirmation prompt; ask the user, then call again with the chosen value. |
| versionName | string | yes | Name for the new version (must be unique for this FN). |
No output schema declared.
No examples provided.
gap_analysis Coverage / gap report across a scope (sprint, release, epic, feature, stories, project) ~563
Aggregate COVERAGE report — for a chosen scope, walks each story and reports which have no tests, which have ACs not covered by any linked test case, which have no acceptance criteria at all, and (for release / projectWide scopes) which TCs are unlinked to any story. READ-ONLY: writes nothing, but emits a "Next actions" hint block for the agent to chain into tc_draft_create / tc_draft_open+update+save / story_update after asking the user. PICK EXACTLY ONE SCOPE — the tool errors if zero or more than one is provided: • `sprintId` — recommended for sprint reviews • `releaseId` — release readiness across all sprints in the release • `epicId` — coverage on one epic • `featureId` — coverage on one feature • `storyIds[]` — hand-picked batch (or a single story: the same info story_sync_testcases returns, wrapped in the gap format) • `projectWide: true` — every story (expensive; prefer a narrower scope when the user's question is really about a sprint / release / area) Reuses the same AC↔step matching as `story_sync_testcases` (Jaccard, sensitivity strict / normal / loose). Automation test cases COUNT toward `tcCount` but do NOT run drift (their steps are recorded, not AC-derived — computeDrift would false-flag every AC as uncovered). Orphan-TC detection runs only for `releaseId` / `projectWide` scopes. When the user's question is about a single story, prefer `story_sync_testcases` if they want the drift ops to apply; use this tool if they want a coverage verdict / report.
| Name | Type | Req | Description |
|---|---|---|---|
| epicId | string | – | Epic numeric id or business key (EP_123). |
| featureId | string | – | Feature numeric id or business key (FT_123). |
| projectWide | boolean | – | Set true to scan every story in the project (bounded by scanLimit). Prefer a narrower scope when possible — projectWide fans out into many adapter calls. |
| releaseId | string | – | Release id (from list_releases). |
| scanLimit | integer | – | Cap on the initial listStories fetch (and, for release/projectWide, the orphan-TC scan). Default 500. Raise for a genuinely huge project. |
| sensitivity | string | – | AC↔step match strictness (same as story_sync_testcases). Default `normal`. |
| sprintId | string | – | Sprint id (from list_sprints). |
| storyIds | array | – | One or more story ids/keys (US_123). |
No output schema declared.
No examples provided.
heal_apply Apply a heal plan (creates a NEW version) ~161
Applies a plan from `heal_plan` as ONE new test-case version: objects first, then step/action bindings, then the failing iteration's test data. The current version is never edited, so a running execution is not affected. `mode:"apply_and_verify"` also re-runs the test case and reports `verified` only when the healed step passes WITHOUT falling back to another locator. Refuses a stale plan (the test case moved to a different version since planning) — re-run heal_plan then.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmSharedObject | boolean | – | Required when the plan changes an object also used by other test cases (blast radius non-empty). |
| mode | string | – | Default 'apply'. |
| planId | string | yes | planId returned by heal_plan. |
No output schema declared.
No examples provided.
heal_plan Plan a heal for a failed test case (read-only) ~343
Replays a failed test case live, captures the DOM at the failing step, and returns a REVIEWABLE heal plan: objects (locators + properties), per-step actions, parameters, and the test data of the failing iteration only. This call never writes — apply it with `heal_apply({ planId })`. Use it when a test failed for a reason the healer may fix (locator/object changed, wrong action, unresolved `${param}`, bad test-data value). It also reports a diagnosis when the failure is NOT healable (app bug, environment, bad business data), with the reason. Rules baked in: the shared action catalog is never modified, shared parameters are never renamed (create + rebind instead), and only the iteration that failed may have test data patched.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | – | Limit which domains may change (default: all). e.g. ["parameter","testdata"] to skip locator churn. |
| maxAttemptsPerStep | integer | – | Replay retries at the failing step. Default 3. |
| runId | string | – | Specific failed run. Omit to use the latest failed run. |
| tcId | string | yes | The failing test case id (TC-123). |
| testFamily | string | – | TEST ONLY: family to report alongside testProposals (default object_state). |
| testProposals | array | – | TEST ONLY (needs QA_HEAL_TEST_HOOK=1): plan these raw proposals instead of calling heal_propose. The full validation/apply pipeline runs exactly as in production; only the browser-driven proposal ste… |
| url | string | – | Override start URL when the test case has no navigate step. |
No output schema declared.
No examples provided.
heal_status Read a heal plan and its result ~45
Returns the stored plan for a planId and, once applied, the apply report (version, verified, partial).
| Name | Type | Req | Description |
|---|---|---|---|
| planId | string | yes | planId returned by heal_plan. |
No output schema declared.
No examples provided.
impact_analysis Blast-radius report from a single anchor (defect / testcase / story / sprint / release) ~455
BLAST-RADIUS report from ONE anchor — walks the graph both ways to answer "if this is broken / unfinished, what does it affect?" READ-ONLY. PICK EXACTLY ONE ANCHOR: • `defectId` (DF_77) — walks defect → TC(s) → story → sprint → release, then sibling stories in the sprint. • `testCaseId` (TC_204) — walks TC → open defects on it → story → sprint → release. • `storyId` (US_103) — walks story → its TCs / defects / sprint / release / sibling stories. • `sprintId` — rolls up every story in the sprint: uncovered ACs, open critical / major defects, stories with no tests. • `releaseId` — per-sprint table with a rolled-up release verdict. VERDICT (traffic light, deliberately simple): · `AT_RISK` — any open critical defect, OR more than 30% of ACs uncovered. · `NEEDS_ATTENTION` — any open major defect, OR a story in scope has zero tests. · `READY` — otherwise. Reuses `gap_analysis`'s per-story analyser to count uncovered ACs, so the AC↔step match rules (Jaccard, sensitivity) are consistent between the two tools. Writes nothing — any triage the user chooses (reassign, descope, add TC) goes through the existing write tools after they confirm.
| Name | Type | Req | Description |
|---|---|---|---|
| defectId | string | – | Defect id or code (DF_77). |
| releaseId | string | – | Release id (from list_releases). |
| scanLimit | integer | – | Cap on the initial listStories fetch for sprint/release rollups. Default 500. |
| sensitivity | string | – | AC↔step match strictness passed through to gap analysis. Default `normal`. |
| sprintId | string | – | Sprint id (from list_sprints). |
| storyId | string | – | Story id or business key (US_103). |
| testCaseId | string | – | Test case id or code (TC_204). |
No output schema declared.
No examples provided.
journal_modify Modify a test case (steps, loops, if-else, nested) ~898
Apply granular edits to an EXISTING test case and persist them, opening the result in the test-case editor. Use journal_grep first to see the numbered steps, then pass ops (numbers are from that view, 1-based): • add_step / update_step / remove_step / move_step — edit individual steps • duplicate_step { n, through?, at? } — copy the WHOLE step (parameters, values, object, flags, settings) to the end or to `at`; use this for "add the same step again", not add_step. `through` is required when n opens an IF / loop / function block. • update_steps { where, patch } — one patch for EVERY matching step ("skip every step that uses X"); where: numbers, from/to, stepType, actionType, object, descriptionContains, parameter, or all:true • a step patch may carry swapParams [{ from, to, value? }] to replace one parameter with another in the same slot (recordedParam only adds) • add_assertions { n, assertions:[{ path, condition, expectedValue }] } — APPEND response assertions to an EXISTING API step (path: statusCode | responseTime | responseSize | $.body.x | $.headers.Name). The request, object, action, parameters and existing assertions are untouched — use this for "add only the assertion to step N". • update_step patch.api is MERGED into the saved API request (add an assertion: api.addAssertions [{ path, condition, expectedValue }]; api.assertions replaces the list) — edit an API step with this, never remove_step + add_step • wrap_in_loop { from, to, condition?, maxIterations? } — wrap steps from..to in a while loop • wrap_in_if { from, to, condition? } — wrap steps from..to in an if block • add_step with stepType "control_flow" and controlFlow { kind, condition } — kind "while" … "end_while" (WHILE), "do" … "end_do_while" (DO-WHILE; the condition goes on the closing step). Conditions: controlFlow.condition = { type: element_displayed | element_not_displayed | element_enabled | element_disabled | element_clickable | element_checked, objectId | objectName },…
| Name | Type | Req | Description |
|---|---|---|---|
| ops | array | yes | Ops to apply, in order. |
| tcId | string | yes | Test case id or business key. |
| versionId | string | – | SimplifyQA, multi-version test cases: the version to edit — its id or name (e.g. "v2.0"); step numbers are that version's (read it with journal_grep { versionId }). Omit to edit the CURRENT version.… |
No output schema declared.
No examples provided.
local_agents List THIS machine's local agent(s) ~107
List the LOCAL agent(s) registered from THIS machine — the desktop agent running on the box this MCP is on. Use for a LOCAL tc_run / suite_run. There is exactly one desktop agent per machine, so this is 0 or 1 row: empty means no agent is registered from this box (start the SimplifyQA desktop agent, or use mode:'remote' to dispatch to a teammate's). Use `remote_agents` for the other registered machines. Requires a live connection.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mobile_list_devices List mobile devices (Android or iOS) ~221
List MOBILE devices available to the project — union of the LOCAL roster (real devices + emulators/simulators registered via the desktop agent, from `/tm/mobileDevices/search`) and the CLOUD roster (whichever farm the project has integrated: LambdaTest / BrowserStack / SauceLabs / SimplifyQA Device Farm — the first non-empty one wins, matching the UI's single-provider-per-project model). Use before `tc_run` for an ANDROID or IOS test case to pick a `deviceId` (and read `deviceType` + `cloudDeviceType` off the same row). The `active` flag on local rows is last-known: stale by design (the SQA backend writes it when the desktop agent connects/disconnects, and a 7s-stale cron flips it back); a device the user just plugged in may still read `active:false` here. Cloud rows don't carry `active` — cloud farms are always assumed reachable. Requires a live connection.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | yes | Which mobile platform to list devices for. |
No output schema declared.
No examples provided.
object_create Create a new object in the Object Repository ~197
Create a new object (a locator-bound UI element) in the shared Object Repository. `objectType` (e.g. "WEB", "ANDROID") is REQUIRED and STRUCTURAL — it selects the object template and cannot be changed after creation (see object_update). `locators` is the set of captured selector strategies for this element. GET-OR-CREATE by NAME (case-insensitive): if an object with the same name already exists, this reuses it — updating its locators in place if they differ — instead of creating a duplicate. Requires a live connection (qa_connect).
| Name | Type | Req | Description |
|---|---|---|---|
| locators | array | – | Captured locator strategies for this element. |
| name | string | yes | Display name for the object (the UI's "Name" column). |
| objectType | string | yes | Object type / technology, e.g. "WEB", "ANDROID", "IOS", "DESKTOP". Required, and fixed once created. |
No output schema declared.
No examples provided.
object_delete Delete an object from the Object Repository (two-step confirm) ~227
Delete an object from the shared Object Repository. TWO-STEP CONFIRM, REQUIRED even for a single object: call once with just `id` to preview it (name/type + how many test cases, functions, or workflows still reference it); then call again with `{ id, confirm: true }` to actually delete. NEVER call this with confirm:true on the first call, and NEVER call it at all unless the user's own words asked to DELETE — a request to list, show, or read objects (object_list / object_get / "show me the objects in this test case") is NEVER a reason to call this tool. DEPENDENCY-CHECKED: if the object is still referenced by any test case, function, or workflow, the delete is REFUSED at confirm time too — it reports what still uses it instead of silently breaking those. Requires a live connection (qa_connect).
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Set to true on the SECOND call to actually delete. Omit (or false) to preview first. |
| id | string | yes | The object id to delete. |
No output schema declared.
No examples provided.
object_parameterize Parameterize an object locator (SimplifyQA) ~362
Turn part of a saved step's OBJECT locator into a "Parameter of object", as the SimplifyQA editor does: e.g. step 7 clicks the object whose locator is //a[normalize-space()='PIM'] — pass `replace:"PIM"`, `parameterName:"menu_name"` and the locator becomes //a[normalize-space()='{{<id>}}'], the step shows menu_name under "Parameter of object", and the test-data cell holds PIM. The recorder cannot do this itself. WITHOUT `confirm:true` it only reports what would change. The object is SHARED: other steps and test cases that use it will resolve the same parameter, so they need a value for it too. Reads the test data back and says whether the value is stored.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | true = write it. Omit to preview. |
| locator | string | – | Only rewrite the locator with this name (e.g. "Xpath by Role and Name"). Default: every locator containing the text. |
| parameterName | string | yes | Name of the parameter, e.g. menu_name. Created if it does not exist. |
| replace | string | – | The text inside the locator to turn into the parameter, when it differs from `value`. |
| step | integer | yes | 1-based number of the step whose object holds the locator. |
| tcId | string | yes | Test case id or code, e.g. TC-12862. |
| value | string | – | The value for the test-data cell, e.g. PIM. Also the locator text to replace unless `replace` is given. |
| versionId | string | – | A non-current version of the test case (id or name like v2.0). |
No output schema declared.
No examples provided.
object_update Update an object (name, description, parameter, module, or locators) ~634
Update an object in the shared Object Repository — rename it, change its description, set which parameter(s) it is bound to, move it to a different module, and/or fix locator values directly (e.g. a stale `data-test` attribute). Any combination of these can be set in ONE call when the user states them together. `locators` UPSERTS by strategy name: an entry matching an EXISTING locator name updates its value/unique in place, everything else on the object is untouched, and a name with no existing match is added as a NEW locator — you do not need to resupply the full locator set. DEFAULT LOCATOR: to make a locator the object's DEFAULT (the one the UI marks as default and the executor uses first — "make it default"), pass `defaultLocator: "<locator name>"`, e.g. add an xpath with `locators: [{ name: "xpath", value: "//input[@id='u']" }]` AND `defaultLocator: "xpath"` in one call. It can also name a locator already on the object (no need to resend its value). Only one default exists — it is cleared on the others. The result is re-read and the call REFUSES if the default did not take. `parameterNames` REPLACES the object's full parameter binding with these (resolved by exact name, case-insensitive) — pass the CURRENT set plus the new one if the user means "also bind" rather than "replace"; read the object first (object_get) if you need to know the current bindings. `moduleName` takes the module's NAME, never an id — it is resolved automatically. Both REFUSE clearly (naming the bad value and the valid options) if the name doesn't match anything, rather than silently saving nothing. The object's TYPE (technology) and TEMPLATE ID are NOT editable here — they are structural (they determine which attribute set is even valid) and stay whatever they already are; changing either means creating a new object, not updating this one. Requires a live connection (qa_connect).
| Name | Type | Req | Description |
|---|---|---|---|
| defaultLocator | string | – | NAME of the locator to make the object's DEFAULT, e.g. "xpath" — one you add in `locators` in this same call, or one already on the object. Use this whenever the user says "make it default". |
| description | string | – | New description for the object. |
| id | string | yes | The object id to update. |
| locators | array | – | Locators to upsert by name, e.g. [{ name: "data-test", value: "123456" }] to fix one attribute — every other locator on the object is left as-is. |
| moduleName | string | – | Move the object to this module, by NAME (resolved automatically — never pass an id). |
| name | string | – | New display name for the object. |
| parameterNames | array | – | REPLACES the object's bound parameters with these, resolved by exact name (case-insensitive). Pass the full desired set, not just the one being added. |
No output schema declared.
No examples provided.
How do I install the simplify3x-connect MCP server?
simplify3x-connect runs locally as an npm package, launched with npx -y simplify3x-connect. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · simplify3x-connect
claude mcp add com-simplifyqa-simplify3x-connect -- npx -y simplify3x-connect
What is the simplify3x-connect MCP server?
simplify3x-connect is an MCP server listed in the public MCP registry as com.simplifyqa/simplify3x-connect. SimplifyQA test management: find, author, record, run and triage test cases. This page covers its npm package (simplify3x-connect).
Is the simplify3x-connect MCP server safe to use?
simplify3x-connect scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the simplify3x-connect MCP server expose?
simplify3x-connect exposes 113 tools: project_info, qa_connect, qa_switch_project, qa_connection_status, qa_disconnect, and 108 more. Their descriptions and schemas cost roughly 44,141 tokens of context every time the server is loaded.
Is the simplify3x-connect MCP server still maintained?
simplify3x-connect is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the simplify3x-connect MCP server under?
simplify3x-connect declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the simplify3x-connect MCP server?
VerifyMCP ran 16 checks on simplify3x-connect, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.