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 →
parameter_update Edit a project parameter (Local / Runtime, default value, description) ~215
Edit a PARAMETER itself in the project - not a step's use of it. Typical: "make task_doc a Runtime parameter" (a store slot written by a Read action must be Runtime), or change its default value / description. Local <-> Runtime only: Global parameters are encrypted and shared and are not edited here. IMPACT: the change applies to EVERY test case that uses this parameter. So the call is a preview until you pass `confirm: true` - show the user what will change and that it affects every use, then call again with confirm. The parameter is re-read after the update and the call REFUSES if the change did not take. Requires a live connection.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Must be true to apply. Without it the call only describes what would change. |
| defaultValue | string | – | – |
| description | string | – | – |
| parameter | string | yes | The parameter's exact name (case-insensitive) or numeric id. |
| type | string | – | New access type. |
No output schema declared.
No examples provided.
pipeline Create / change / delete / run a SimplifyQA pipeline ~499
Manage SimplifyQA PIPELINES. Read them with sqa_query collection "pipelines". Actions: - action:"create" — needs `name`, `pipelineType` (TC or SU), `parentId` (the test case or suite), `mode` (local / remote / cloud), `releaseId` and `sprintId` (SimplifyQA requires both — ASK if unknown); optional `agentId`, `environment`, `browser` (TC), `description`. - action:"update" — needs `pipelineId`; any of `name`, `description`, `releaseId`, `sprintId`, `environment`, `agentId`, `mode`. - action:"delete" — needs `pipelineId`. TWO-STEP: the first call only previews; call again with `confirm:true` ONLY after the user explicitly says to delete. - action:"run" — needs `pipelineId`; call ONLY when the user explicitly asked to run it. - action:"run_status" / "stop" — need `executionId` (from run).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What to do. |
| agentId | string | – | create / update: agent id (local_agents / remote_agents). |
| browser | string | – | create: browser for the WEB test cases — the test case, or every WEB test case in the suite (default chrome). A CLOUD pipeline is headless: only Chrome Headless, Firefox Headless or Edge Headless exi… |
| confirm | boolean | – | delete: true on the SECOND call, only after the user explicitly said to delete. |
| description | string | – | create / update. |
| environment | string | – | create / update: environment name or key (default general). |
| executionId | string | – | run_status / stop: the execution id from run. |
| mode | string | – | create / update: where it runs. |
| name | string | – | create / update: pipeline name. |
| parentId | string | – | create: the test case or suite id / code. |
| pipelineId | string | – | update / delete / run: pipeline id or code. |
| pipelineType | string | – | create: TC (test case) or SU (suite). |
| releaseId | string | – | create / update: release id (required to create). |
| sprintId | string | – | create / update: sprint id (required to create). |
No output schema declared.
No examples provided.
project_create Create a project (SimplifyQA) ~84
Create a new PROJECT with a name and description. The new project is returned with its id and business code (PR-x), and is read back to confirm. Use qa_switch_project to work in it afterwards.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Project description. |
| name | string | yes | Project name. |
| users | array | – | Optional numeric userIds to add as project members. |
No output schema declared.
No examples provided.
project_delete Delete a project (SimplifyQA) ~116
DESTRUCTIVE. Delete ONE project by id or code (e.g. "5" or "PR-7"). TWO-STEP: call without `confirm` to get a preview of the project that will be deleted; show it and ASK the user; only then call again with `confirm:true`. It removes the project and everything inside it.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Set true only after the user explicitly confirms. |
| projectId | string | yes | Project id or code (e.g. "5", "PR-7"). |
No output schema declared.
No examples provided.
project_info Check the connection and project ~22
Validate the configured connection and return provider, org/project and entity counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
project_user_add Add or invite a user to a project (SimplifyQA) ~197
Add a person to a project with a role — the admin Project screen's "Invite Users". The email is resolved to an existing user; when nobody has it the user is INVITED (created and the invitation email sent) unless `invite:false`. Existing members are preserved — the project's member list is merged, never replaced — and the membership is read back to confirm. Defaults to the connected project and to the project's QA role.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address of the person to add, e.g. someone@yopmail.com. | |
| invite | boolean | – | Invite the user when the email is unknown (default true). false = fail instead. |
| name | string | – | Display name — used only when the user has to be invited. |
| projectId | string | – | Project id. Defaults to the connected project. |
| roleId | number | – | Role id inside that project. Default 1 (the QA role). |
No output schema declared.
No examples provided.
project_user_remove Remove a user from a project (SimplifyQA) ~109
Remove ONE person from a project (their membership row only — the user account and the person's other projects are untouched). Identify them by `email` or `userId`; the remaining membership is read back to confirm and the removed list is reported. The project's other members are preserved.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email of the person to remove. | |
| projectId | string | – | Project id. Defaults to the connected project. |
| userId | number | – | Numeric user id (alternative to email). |
No output schema declared.
No examples provided.
qa_connect Connect to a QA product ~436
Point this MCP at your QA product so it can work with EXISTING test cases -- list them, read their steps, modify them, and run them. Ask the user for their app URL and a token; do not guess either. The token is a product session JWT (then `projectId` is required, because the token alone carries no project context) or an MCP API key (then pass auth:"key" and projectId is optional -- a key is already project-scoped). The connection is VALIDATED before it is accepted (it fetches the project), so a wrong URL, token or project fails here with the reason rather than surfacing later as a confusing error, and a failed attempt leaves any working connection untouched. It is kept in memory for as long as the agent runs and is never written to disk or logged. NOT needed to record a new test case: recording, the live editor and drafts work offline with nothing configured.
| Name | Type | Req | Description |
|---|---|---|---|
| auth | string | – | Token kind. Omit to AUTO-DETECT from the token (JWT-shaped → "jwt"). "jwt" sends Authorization + x-project-id; "key" sends Authorization only. |
| baseUrl | string | – | The product BACKEND REST base (QA_BASE_URL) for DIRECT data ops (list/read/save/run). Provide this for a direct connection; `url` is only needed for recording / save-with-editor. |
| product | string | – | Which product to route this connection to (the product selector; defaults to the primary product). For a remote product, also pass its agent MCP `/mcp` endpoint as `url`. |
| projectId | string | – | Project id. REQUIRED with a JWT; optional with an API key. |
| token | string | yes | Bearer token: a product session JWT, or an MCP API key. |
| url | string | – | MCP endpoint to hop to — the product agent /mcp, used for recording and save-with-editor. OPTIONAL for a DIRECT (backend-REST) connection: pass `baseUrl` instead. Required when connecting through a r… |
No output schema declared.
No examples provided.
qa_connection_status Show the current connection ~81
Report whether this MCP is connected to a QA product, which URL and project, how the credentials arrived (startup config vs qa_connect), and whether a token is present. Also reports whether the LOCAL desktop agent (/mcp, default :4040) is reachable — the process that actually runs LOCAL executions on this machine. The token value itself is never returned.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
qa_disconnect Drop the connection ~55
Forget the runtime URL and token and fall back to whatever the agent started with (usually nothing). Use it before connecting to a different app or project, or to stop this MCP reaching a backend at all. Offline authoring is unaffected.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
qa_privileges Check what you may create in a project ~281
READ-ONLY preflight for recording: resolves the role the connected user holds in a project and that role's privilege keys, then says whether recording is allowed there. Answers the three failure modes BEFORE anything is created: invalid/expired token, no role in the project, or a role missing a write the recorder needs (add_testcase / add_parameter / add_object, plus mobile/mainframe/cloud integration keys for those technologies). Returns verdict ok | no-role | missing-privileges | invalid-token, the role name, the full privilege list, a `can` summary, and the exact keys to ask an admin for. The product agent runs the same check inside core_activate_technology, so you never need to call this first — call it when you want to warn the user, or to explain a refusal.
| Name | Type | Req | Description |
|---|---|---|---|
| need | array | – | Extra privilege keys to verify, e.g. ["add_userstory"]. |
| projectId | string | – | Project to check. Defaults to the selected project. |
| provider | string | – | Device provider for ANDROID/IOS (local|emulator|simplifyqa|lambdatest|browserstack|saucelabs) — cloud providers also need allow_cloud_integration. |
| technology | string | – | Check the extra privileges this recording technology needs (mobile/mainframe integration keys). Default: WEB. |
No output schema declared.
No examples provided.
qa_switch_project Switch the connected project ~131
Switch to a different project on the SAME connection — reuses the current URL + token, so you do NOT re-enter them. Pass the project id; if the user names a project, resolve the name to an id first (SimplifyQA: sqa_query collection "projects" with member:true; Walnut: list_projects). Validated before it is adopted, so a bad id leaves the current project in place.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | The project id to switch to. Find it by name with sqa_query collection "projects" (SimplifyQA) or list_projects (Walnut). |
No output schema declared.
No examples provided.
release_create Create a release (SimplifyQA) ~259
Create a SimplifyQA release in the connected project — what Releases → Create Release does — and return its key (RE-xx). Needs `name`, `plannedStartDate`, `plannedEndDate` (YYYY-MM-DD) and `estimatedEffort` (hours). The state defaults to New and the owner to the connected user (SimplifyQA requires one). A release with the same name is refused. It reads the release back. Only an admin user can create releases. Use the returned RE-xx as `releaseId` for runs, schedules and pipelines, and create sprints with sprint_create.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| estimatedEffort | number | yes | Estimated effort in hours (e.g. 2). |
| name | string | yes | Name (3–500 characters). |
| owners | array | – | Owners: emails, names, user ids or "me". Default: the connected user (SimplifyQA requires at least one owner). |
| plannedEndDate | string | yes | YYYY-MM-DD, on or after the start. |
| plannedStartDate | string | yes | YYYY-MM-DD. |
| state | string | – | Defaults to the project's first state (New). An unknown state is refused with the valid ones listed. |
No output schema declared.
No examples provided.
release_delete Delete a release (SimplifyQA) ~169
Delete a SimplifyQA release (Releases → Delete). TWO-STEP: call with `releaseId` (id, code like RE-45, or exact name) and no `confirm` to PREVIEW — it lists everything still linked (its sprints, stories, defects, tasks, execution plans, pipelines, schedules, other projects using it) and deletes nothing. Show that to the user, and call again with `confirm:true` ONLY after the user explicitly says to delete. A release that anything still uses is refused even with confirm. Only an admin user can delete a release.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | true on the SECOND call, only after the user explicitly said to delete. |
| releaseId | string | yes | Release id, code (RE-45) or exact name. |
No output schema declared.
No examples provided.
release_update Update or close a release (SimplifyQA) ~321
Change or CLOSE a SimplifyQA release. Read releases with sqa_query (collection "releases"). Pass `releaseId` (id, code like RE-44, or exact name) and either `close:true` (sets the project's completed-type state and the actual end date) or `state`, and/or name, dates, description, estimatedEffort, ownerIds. It reads the release back and reports the stored state. Only an admin user can edit a release in SimplifyQA. Closing warns when the release still has sprints that are not completed.
| Name | Type | Req | Description |
|---|---|---|---|
| actualEndDate | string | – | YYYY-MM-DD. |
| actualStartDate | string | – | YYYY-MM-DD. |
| close | boolean | – | true = close it: the project's completed-type state (Completed / Released / Closed) and the actual end date. Use this for "close release RE-44". |
| description | string | – | – |
| estimatedEffort | number | – | – |
| name | string | – | New name (3–500 characters). |
| ownerIds | array | – | Owner user ids (replaces the current owners). |
| plannedEndDate | string | – | YYYY-MM-DD, on or after the start. |
| plannedStartDate | string | – | YYYY-MM-DD. |
| releaseId | string | yes | Release id, code (RE-44) or exact name. |
| state | string | – | The state to set, as the project names it (e.g. "In-progress", "Completed"). An unknown state is refused with the valid ones listed. |
No output schema declared.
No examples provided.
remote_agents List REMOTE agents (other registered machines) ~102
List the LOCAL agents registered on OTHER machines (teammates' boxes) — the pool a REMOTE run dispatches to. Use to pick an `agentId` for a REMOTE tc_run / suite_run. Excludes this machine's own agent (that's `local_agents`). REMOTE dispatches to a specific teammate's registered desktop agent through the SimplifyQA queue; the picked agent's browsers / adb devices are what actually execute. Requires a live connection.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
report_download Download PDF reports for a test case or suite execution ~365
Generate and SAVE the PDF execution reports the SimplifyQA UI offers. • target "testcase" — report types: `detailed`, `summary` (pick one or both). • target "suite" — report types: `suite` (overall suite report), `detailed` (one detailed report per test case in the suite), `summary` (one summary report per test case). Pick one, several or all. `ref` is the test case id/key (TC_123) or the suite NAME / id. If the user did NOT say which report type(s) they want, call WITHOUT `reportTypes` — the tool replies with the choices; ASK the user, then call again. If they named the type ("the summary pdf report"), pass it directly and do not ask. The report is for ONE execution: by default the most recent one, and the response states which execution was used and how many others exist — pass `runId` (execution id) to pick another. Files are saved under `outDir` (default ./qa-reports) and their paths returned. Protected parameters are masked by the report service. Requires a live connection; no agent needed.
| Name | Type | Req | Description |
|---|---|---|---|
| outDir | string | – | Folder to save PDFs into. Default: ./qa-reports |
| ref | string | yes | Test case id/key (TC_123), or suite name / id. |
| reportTypes | array | – | Which reports. Omit to get the choices and ASK the user. testcase: detailed | summary. suite: suite | detailed | summary. |
| runId | string | – | Execution id to report on. Omit to use the most recent execution. |
| target | string | yes | Report for a test case or a suite. |
No output schema declared.
No examples provided.
run_history Recent execution history for a suite or test case ~209
Return the top-N most recent STANDALONE executions of a suite or test case (newest first), as a scoreboard — runId, state, timing, reportUrl, plus a per-test-case tally for SUITE runs (passed/failed/skipped of total). No step-level detail; use `run_status({ runId })` on any row to drill in. Pass EXACTLY one of `suiteId` or `tcId`. `limit` defaults to 5, capped at 20. Suite-child TC rows are excluded from a `tcId` query, so a test case that only runs inside suites returns empty. Requires a live connection.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many recent runs to return (default 5, max 20). |
| suiteId | string | – | A suite id (from suite_list) — returns the suite's recent executions. |
| tcId | string | – | A test case id — returns the TC's recent STANDALONE executions. |
No output schema declared.
No examples provided.
run_status Get a run status ~314
Read the status of a run — state (queued/running/passed/failed/skipped/notExecuted/stopped/error), progress, per-test-case rollup for a SUITE run (capped at 100 shown, ONE ROW PER TEST CASE — not per iteration), and a link. Every state SQA reports is its own bucket in the per-state tally (skipped and notExecuted are real, distinct outcomes — never counted as passed or folded into queued). While the run is still queued/running, the tally is labelled provisional. Pass EITHER `runId` (from tc_run / suite_run) or `suiteId` (from suite_list) to read that suite's LATEST execution. The suite rollup only says pass/fail/etc per test case, never WHY — to get one child's own step-level detail (which step failed, the error), call again with the SAME `runId`/`suiteId` plus `tcId` set to one of the ids shown in the rollup. Requires a live connection.
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | – | The run id returned by tc_run or suite_run. |
| suiteId | string | – | A suite id (from suite_list) — resolves to the suite's latest execution. |
| tcId | string | – | Drill into ONE child test case's step-level results within a SUITE run — its id from the rollup shown by a prior run_status call (without `tcId`). Ignored / refused for a single-TC run. |
No output schema declared.
No examples provided.
run_stop Stop a run ~158
Signal a running execution to stop, and poll briefly for the terminal state so the reply reflects reality (not a fire-and-forget). Pass EXACTLY one of: `runId` (from tc_run / suite_run), `suiteId` (stops the suite's LATEST execution), or `tcId` (stops the TC's LATEST standalone execution — suite-child rows are excluded). Requires a live connection.
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | – | The run id (from tc_run / suite_run). |
| suiteId | string | – | A suite id (from suite_list) — stops the suite's latest execution. |
| tcId | string | – | A test case id — stops the TC's latest STANDALONE execution. |
No output schema declared.
No examples provided.
schedule_control Pause / resume / cancel a schedule ~96
Change a schedule's state: `pause` (stop it firing but keep it — reversible with `resume`), `resume` (re-enable a paused schedule), or `cancel` (stop its pending / live run). To remove a schedule entirely, use schedule_delete instead. Requires a live connection.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | pause / resume / cancel. |
| scheduleId | string | yes | The schedule id (from schedule_list). |
No output schema declared.
No examples provided.
schedule_delete Delete a schedule ~100
Permanently DELETE a schedule (and tear down any run it currently owns). This cannot be undone — to only stop it temporarily use schedule_control (pause / cancel). CONFIRM with the user before deleting. Requires a live connection.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | SimplifyQA: the first call only previews; pass true on the SECOND call, after the user explicitly said to delete. |
| scheduleId | string | yes | The schedule id (from schedule_list). |
No output schema declared.
No examples provided.
schedule_list List schedules ~80
List the scheduled runs in the connected project — each with WHAT it runs (test case / suite), its cadence, next run time, status (scheduled / running / paused / cancelled), where it runs + the pinned agent, and its browser. Use this to find a schedule to edit, pause/resume, cancel, or delete. Requires a live connection.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
schedule_update Edit a schedule ~791
Change a schedule's NAME / WHAT IT RUNS (a test case or a suite — `testCaseId` or `suiteId`; the schedule switches between Test Case and Suite as the Scheduler form does, keeping the same id) / time / recurrence / end date / timezone / browser / environment / release / sprint, or RE-PIN its agent. Pass `scheduleId` (from schedule_list) and ONLY the fields to change. To re-pin: mode:'local' + `agentId` (from local_agents), or mode:'cloud' + a runner's `cloudRunnerCredentialId` (the `credentialId` from cloud_runners). Requires a live connection.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | – | Local re-pin: an agent credential_id from local_agents. |
| browser | string | – | New browser for a WEB test case / suite schedule. For a SCHEDULE on SimplifyQA, 'chrome' (and 'chromium') = Chrome, 'msedge'/'edge' = Edge, 'firefox', 'webkit'/'safari' = Safari — chrome is fine; on… |
| cloudRunnerCredentialId | string | – | Cloud re-pin: a runner's credentialId from cloud_runners. |
| dayOfMonth | integer | – | Monthly 'ON DAY': 1–30; default = the start's day. |
| daysOfWeek | array | – | Weekly: the weekdays to run on (MONDAY … SUNDAY or MON … SUN); default = the start's weekday. Monthly with `occurrence`: the one weekday. |
| endDate | string | – | New ISO end date (for recurring schedules). |
| environment | string | – | New environment id (Mongo id). |
| interval | integer | – | REPEAT EVERY N for hourly / daily / weekly / monthly — N hours / days / weeks / months (e.g. hourly + 2 = every 2 hours). Default 1; giving it alone changes the schedule's current cadence. With 'ever… |
| mode | string | – | Re-pin target: pair with agentId (local) or cloudRunnerCredentialId (cloud). |
| name | string | – | Rename the schedule (3–501 characters, unique in the project) — the name the Scheduler shows. |
| occurrence | string | – | Monthly 'ON THE': the first / second / third / last weekday of the month — give the weekday in daysOfWeek. |
| releaseId | string | – | Release: id, code (RE-44) or exact name; "none" clears it. A suite schedule needs one. |
| scheduleId | string | yes | The schedule id (from schedule_list). |
| scheduleType | string | – | New recurrence (same choices as the UI: once, every_5_minutes, hourly, daily, weekly, monthly). Anything but once needs an endDate. |
| scheduledFor | string | – | New start / next-run ISO datetime. |
| sprintId | string | – | Sprint: id, code (SP-1) or exact name; it must belong to the release. "none" clears it. |
| suiteId | string | – | Make it run THIS suite (id or code, e.g. SU-4) — a test-case schedule becomes a Suite schedule (which needs a release). Not together with testCaseId. |
| testCaseId | string | – | Make it run THIS test case (id or code, e.g. TC-35) — a suite schedule becomes a Test Case schedule. Not together with suiteId. |
| timezone | string | – | New IANA timezone (e.g. 'Asia/Kolkata'). |
No output schema declared.
No examples provided.
sprint_create Create a sprint under a release (SimplifyQA) ~283
Create a SimplifyQA sprint under an existing release and return its key (SP-xx). Needs `releaseId` (id, code like RE-44, or exact name — create the release first with release_create), `name`, `plannedStartDate`, `plannedEndDate` (YYYY-MM-DD) and `estimatedEffort` (hours). The state defaults to New and the owner to the connected user. A sprint with the same name in that release is refused; dates outside the release's are warned about. It reads the sprint back. Only an admin user can create sprints.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| estimatedEffort | number | yes | Estimated effort in hours (e.g. 2). |
| name | string | yes | Name (3–500 characters). |
| owners | array | – | Owners: emails, names, user ids or "me". Default: the connected user (SimplifyQA requires at least one owner). |
| plannedEndDate | string | yes | YYYY-MM-DD, on or after the start. |
| plannedStartDate | string | yes | YYYY-MM-DD. |
| releaseId | string | yes | The release this sprint belongs to: id, code (RE-44) or exact name. |
| state | string | – | Defaults to the project's first state (New). An unknown state is refused with the valid ones listed. |
No output schema declared.
No examples provided.
sprint_delete Delete a sprint (SimplifyQA) ~161
Delete a SimplifyQA sprint (Sprints → Delete). TWO-STEP: call with `sprintId` (id, code like SP-64, or exact name) and no `confirm` to PREVIEW — it lists everything still linked (stories, defects, tasks, execution plans, pipelines, schedules) and deletes nothing. Show that to the user, and call again with `confirm:true` ONLY after the user explicitly says to delete. A sprint that anything still uses is refused even with confirm. Only an admin user can delete a sprint.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | true on the SECOND call, only after the user explicitly said to delete. |
| sprintId | string | yes | Sprint id, code (SP-64) or exact name. |
No output schema declared.
No examples provided.
sprint_update Update or complete a sprint (SimplifyQA) ~322
Change or COMPLETE a SimplifyQA sprint. Read sprints with sqa_query (collection "sprints"). Pass `sprintId` (id, code, or exact name) and either `close:true` (sets the completed state and the actual end date) or `state`, and/or name, dates, description, estimatedEffort, ownerIds. It reads the sprint back and reports the stored state. Only an admin user can edit a sprint in SimplifyQA, and its editor refuses to complete a sprint that still has new / pending stories, tasks or defects (not checked here).
| Name | Type | Req | Description |
|---|---|---|---|
| actualEndDate | string | – | YYYY-MM-DD. |
| actualStartDate | string | – | YYYY-MM-DD. |
| close | boolean | – | true = close it: the project's completed-type state (Completed / Released / Closed) and the actual end date. Use this for "close release RE-44". |
| description | string | – | – |
| estimatedEffort | number | – | – |
| name | string | – | New name (3–500 characters). |
| ownerIds | array | – | Owner user ids (replaces the current owners). |
| plannedEndDate | string | – | YYYY-MM-DD, on or after the start. |
| plannedStartDate | string | – | YYYY-MM-DD. |
| sprintId | string | yes | Sprint id, code or exact name. |
| state | string | – | The state to set, as the project names it (e.g. "In-progress", "Completed"). An unknown state is refused with the valid ones listed. |
No output schema declared.
No examples provided.
sqa_query Query any SimplifyQA collection (catalog / search / get / related / custom_fields) ~1,138
THE ONLY READ TOOL ON SIMPLIFYQA. Use it for EVERY fetch / query / list / search / get / read / count request. The old per-collection read tools (tc_list, tc_get, story_list, story_get, epic_list, feature_list, list_modules, list_functions, suite_list, list_users, object_list, defect_list, task_list, list_releases, list_sprints, journal_grep, ...) are NOT registered on a SimplifyQA connection — do not look for them and do not invent one. FLOW: (1) `op:"catalog"` (optionally with a collection) to see descriptions/fields/relations, (2) `op:"search"` for a list or `op:"get"` for one row, (3) `op:"related"` to follow a FK (story → testcases, testcase → defects, suite → runs, module → testcases, ...). For "how many" use `op:"count"` (same `where`), and add `groupBy` for a breakdown ("defects by severity"). RULES: every search injects `deleted:false` and the active project; deleted rows are never returned. Unknown fields/operators are rejected locally (the backend silently returns 0 rows for unknown columns). `priority`/`status` do NOT exist on SimplifyQA test cases — use `reviewApproveStatus` or a custom field. CUSTOM FIELDS: `op:"custom_fields"` returns label → key → `customFields.<key>`; then pass the label as `field` with `custom:true` in `where` (or resolve one with `name`). EXAMPLES: - "list API test cases in module 46" → `{ op:"search", collection:"testcases", where:[{field:"tcType",op:"eq",value:"API"},{field:"moduleId",op:"eq",value:46}] }` - "defects for TC 684" → `{ op:"related", collection:"testcases", id:"684", relation:"defects" }` - "latest run of suite 120 + steps" → `{ op:"search", collection:"executions", where:[{field:"executionTypeId",op:"eq",value:120},{field:"type",op:"eq",value:"SUITE"}], sort:[{field:"id",dir:"desc"}], limit:1 }` then `{ op:"get", collection:"executions", id:"<runId>" }` - "testcases where SEVERITY is High" → `{ op:"search", collection:"testcases", where:[{field:"SEVERITY",custom:true,op:"contains",value:"High"}] }` - "release…
| Name | Type | Req | Description |
|---|---|---|---|
| allProjects | boolean | – | releases / sprints / epics / features, op:"search" or "count": read across EVERY project you have a role in instead of only the active one (no qa_switch_project needed). A projectId/projectIds filter… |
| allVersions | boolean | – | Stories/epics: return every version row instead of one row per item. |
| collection | string | – | Collection name or alias (testcases, tc, stories, defects, executions, ...). Required except for catalog. |
| dryRun | boolean | – | Return the compiled searchFields payload without calling the backend. |
| expand | array | – | For op:"get": relation names to expand (e.g. ["steps","versions"]). |
| groupBy | string | – | For op:"count": the field to break the count down by (e.g. "state", "severity", "ownerId", "tcType"). |
| id | string | – | Row id/business key — required for op:"get" and op:"related". |
| includeHidden | boolean | – | Include rows hidden by default (obsolete test cases; child runs and re-execution copies of executions). Naming the field in `where` does the same. |
| limit | integer | – | Page size (default 50, max 500). |
| name | string | – | For op:"custom_fields": optional label/key to resolve (omit to list all). |
| offset | integer | – | Row offset (not a page number — the engine sets skipStartIndex). |
| op | string | yes | Operation to run. "count" returns how many rows match (with `groupBy`, per value). |
| relation | string | – | Relation name from the catalog — required for op:"related". |
| select | array | – | Fields to return. Use ["*"] for the full row. Defaults to the collection summary projection. |
| sort | array | – | Sort fields. Example: [{ field:"id", dir:"desc" }]. |
| versionId | string | – | For op:"get"/"related" on testcases/functions: the version whose steps to read. |
| where | array | – | Filters, an ARRAY of { field, op?, value }. Combined with AND unless a filter sets condition:"or". Example: [{ field:"name", op:"contains", value:"login" }]. |
No output schema declared.
No examples provided.
story_create Create a user story ~1,306
Create a new USER STORY under the connected project. `projectId` defaults to the current project. **HIERARCHY — ALWAYS RESOLVE BEFORE CALLING.** A story lives under Epic → Feature → Story. Do NOT create orphan stories. Before calling this tool, confirm with the user which `epicId` and/or `featureId` the story belongs to. If the user has not told you: (1) ask them directly, or (2) if they name a parent, resolve the id via `epic_list` / `feature_list` first. When creating MULTIPLE stories from a BRD, group them under the same parent unless the BRD clearly splits them across features. Only skip parent linking if the user explicitly says "no parent" or "standalone". `state` and `priority` default to the project-configured defaults when omitted; pass them only when overriding. Backend requires `name`, `estimatedEffort`. **`description` and `acceptanceCriteria` must BOTH be HTML (NOT markdown) — SQA UI renders them via a Tiptap editor and persists raw HTML. See each field docstring below for the exact allowed tags, required section structure, and Given/When/Then format for AC. One-line descriptions and 3-line AC lists are not acceptable.** `customFields` may be omitted — an empty object is sent automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptanceCriteria | string | – | REQUIRED-QUALITY: comprehensive Given/When/Then criteria as HTML (SQA UI renders through a Tiptap editor). Use <ul><li>…</li></ul> — one AC per <li>. Aim for 5–15 criteria; a BRD with 3 acceptance… |
| customFields | object | – | Optional. Empty object `{}` sent automatically when omitted. |
| description | string | – | REQUIRED-QUALITY: rich HTML write-up sourced from the BRD/spec. NOT markdown — SQA UI stores raw HTML from a Tiptap editor. Minimum 200 words when the BRD covers this story. ALLOWED tags ONLY: <p>,… |
| epicId | number | – | Parent epic numeric id. RESOLVE VIA `epic_list` OR ASK THE USER before creating — do not leave a story parent-less unless the user explicitly says "no parent". |
| estimatedEffort | number | yes | – |
| featureId | number | – | Parent feature numeric id. RESOLVE VIA `feature_list` OR ASK THE USER before creating — a story typically lives under a feature. Skip only if the user explicitly says "no feature". |
| iterationId | number | – | Sprint numeric id (SQA `iterationId`). |
| moduleId | number | – | – |
| name | string | yes | – |
| orphan | boolean | – | Set true ONLY if the user has explicitly said the story has no parent ("standalone", "no epic/feature"). Required when BOTH `epicId` and `featureId` are omitted — the tool refuses otherwise so orphan… |
| ownerId | array | – | Numeric userIds of story owners. |
| plannedEndDate | string | – | – |
| plannedStartDate | string | – | – |
| priority | string | – | Optional. Defaults to the project-configured default story priority when omitted. |
| projectId | number | – | Defaults to the connected project. |
| releaseId | number | – | – |
| state | string | – | Optional. Defaults to the project-configured default story state when omitted. |
| tags | array | – | – |
| teamId | array | – | – |
| type | string | – | – |
| 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.
story_sync_testcases Sync a user story with its manual AND automation test cases (drift + recording plan) ~1,024
Compare a user STORY against every test case linked to it (via storyRef) and return a structured, ORDERED plan for bringing them up to date. MANUAL test cases → textual drift (ac_added / ac_reworded / ac_removed / step_stale) and the exact draft ops (add_step / update_step / remove_step). AUTOMATION test cases → `action: "rerecord"` (or `"up-to-date"`) plus the recording brief: the acceptance criteria to cover, story/module ids, current steps and testdata seeds. An automated TC cannot be re-texted — it must be re-recorded. HOW TO APPLY (one item at a time, in plan order — never in parallel): MANUAL item: 1. tc_draft_from_tc({ tcId }) 2. tc_draft_update({ draftId, ops: item.proposedOps }) 3. tc_save_as_new_version({ tcId, fromDraftId: draftId }) ← new version (v1.0 → v2.0) OBSOLETE item (action === "obsolete") — the scenario this TC tested was REMOVED from the story and NO step matches any current AC: ASK the user, then journal_modify({ tcId, ops: [{ op: "set_meta", patch: { obsolete: true } }] }). Do NOT strip its steps (that leaves an empty, still-active TC) and do NOT delete it. PARTIAL removal — only SOME steps belonged to the removed scenario: item.proposedOps carries ONE bulk remove_steps { numbers:[11,12,13,14,15] }; apply the MANUAL item steps 1-3 above. The result is a NEW VERSION without those steps (v1.0 keeps them). NEVER obsolete a partially-affected TC. AUTOMATION item (action === "rerecord"): 1. ASK the user AI-only or Hybrid, then core_activate_technology({ technology, testcaseId: item.testCaseId, versionName: item.nextVersionName, testcaseName: item.title, userstoryId: item.brief.userstoryId, moduleId: item.brief.moduleId, recordingMode, recordingModeAskedUser }) The recorder window opens on THAT test case (details + versions, steps cleared) and shows the pending version in the version dropdown (v1.0 → v2.0, v2.0 → v3.0). 2. Record the brief.acceptanceCriteria end-to-end (w…
| Name | Type | Req | Description |
|---|---|---|---|
| includeTestData | boolean | – | Include the automation brief's testdata seeds (default true; costs one extra read per automation TC). Set false for a fast check. |
| scanLimit | integer | – | Cap on how many TCs to fetch when `testCaseIds` is omitted. Default 200. |
| scope | string | – | Which linked test cases to plan for. Default "both" (manual drift + automation re-record plan). |
| sensitivity | string | – | Match-strictness for AC↔step overlap. strict=more drift flagged, loose=less. Default normal. |
| storyId | string | yes | Story id or business key (US_123). |
| testCaseIds | array | – | Restrict comparison to these TC ids/keys. Recommended for large projects; otherwise the tool walks up to `scanLimit` TCs. |
| versionStrategy | string | – | How a MANUAL update is written: "new" (default) = new version (v1.0 → v2.0) preserving history; "in-place" = overwrite the current version. |
No output schema declared.
No examples provided.
story_update Update a user story (partial) ~236
PATCH an existing USER STORY — pass only the fields to change plus `updateVersion` (optimistic concurrency, from the last story_get). Accepts id or business key (US_123). Pass `acceptanceCriteria` as a newline-separated string when replacing AC lines.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptanceCriteria | string | – | – |
| customFields | object | – | – |
| description | string | – | – |
| epicId | number | – | – |
| estimatedEffort | number | – | – |
| featureId | number | – | – |
| id | string | yes | Story id or business key (US_123). |
| iterationId | number | – | – |
| moduleId | number | – | – |
| name | string | – | – |
| ownerId | array | – | – |
| plannedEndDate | string | – | – |
| plannedStartDate | string | – | – |
| priority | string | – | – |
| projectId | number | – | – |
| releaseId | number | – | – |
| state | string | – | – |
| tags | array | – | – |
| teamId | array | – | – |
| type | string | – | – |
| updateVersion | number | – | – |
No output schema declared.
No examples provided.
suite_add_testcases Add test cases to a suite (optionally a specific VERSION of each) ~251
Add one or more EXISTING test cases to a suite (appended in order). `tcIds` takes ids or business keys (e.g. TC_123); use suite_list / tc_list to find them. To pin a VERSION, pass `testCases:[{ tcId:"TC-12826", version:"v2.0" }]` (or `versionId`) — the same test case can sit in the suite once per version (v1.0 and v2.0 are two rows). A requested version that does not exist is an ERROR (nothing is added twice as v1.0). Default = the test case's current version; an (tc, version) pair already in the suite is skipped. NOTE: a suite can only hold test cases of ONE category (all manual OR all automated) — the product rejects a mix. Returns the updated suite.
| Name | Type | Req | Description |
|---|---|---|---|
| suiteId | string | yes | The suite id to add to (from suite_list). |
| tcIds | array | – | Test case ids / business keys to add (their current version). |
| testCases | array | – | Test cases with an explicit version — lets one TC be added once per version. |
No output schema declared.
No examples provided.
suite_copy_testdata Copy a SUITE-LEVEL test-data row and save it on the suite ~241
Copy ONE existing suite-level row of suite `suiteId` into a NEW suite-level row and save it. Use for "copy ITR-1 into ITR-2 in SU-24's test data and save". The copy is written to the SUITE-LEVEL test data ONLY — member test cases' own test data is NEVER touched. `from` names the source row (default: the suite default row, normally ITR-1); `name` names the new row (default: the next free ITR-N). The tool then reads the suite's test data back and confirms the new row exists. Refuses a duplicate row name.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentType | string | yes | Environment key from tc_list_environments (e.g. general, general_1). |
| from | string | – | Source iteration name (e.g. "ITR-1") or id. Default: the suite default row. |
| name | string | – | Name for the new row (e.g. "ITR-2"). Default: next free ITR-N. |
| suiteId | string | yes | Suite id or business key (SU-24). |
No output schema declared.
No examples provided.
suite_create Create a new suite from a few test cases ~252
Create a NEW test suite in the connected project from a small set of existing test cases. `tcIds` accepts numeric ids, business keys (TC_123), OR plain test case NAMES — a name is resolved by searching the project (tc_list under the hood); an ambiguous name (multiple matches) or one with zero matches is reported back rather than guessed. NOTE: a suite can only hold test cases of ONE category (all manual OR all automated) — a mixed set is refused. NAME: if `name` is omitted, this tool does NOT create anything yet — it resolves the test cases, SUGGESTS a suite name, and returns a preview. Show the user the suggested name and the resolved test cases, ask them to confirm it or give their own, then call suite_create again with `name` set (and the same `tcIds`) to actually create it. Requires a live connection.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional suite description. |
| name | string | – | Suite name. Omit to get a suggested name + preview first (does not create). |
| tcIds | array | yes | Test case ids, business keys (TC_123), or plain names to include. |
No output schema declared.
No examples provided.
suite_get_testdata Read a suite's SUITE-LEVEL test data ~158
Read the SUITE-LEVEL test-data iterations of suite `suiteId` (SU-24) in an environment. Suite-level test data is a SEPARATE store from the member test cases' own test data. When the user says "SU-24 test data", ALWAYS use this — never tc_get_testdata on a member test case. `environmentType` is REQUIRED: call tc_list_environments, show the keys, and ASK which env. The result lists every iteration (name, default marker, parameter=value cells).
| Name | Type | Req | Description |
|---|---|---|---|
| environmentType | string | yes | Environment key from tc_list_environments (e.g. general, general_1). |
| suiteId | string | yes | Suite id or business key (SU-24). |
No output schema declared.
No examples provided.
suite_manage Update or delete a suite (SimplifyQA) ~857
Change, read or remove an existing SimplifyQA suite. Pick ONE `action`: - action:"get" — needs `suiteId`. READS the suite's Settings panel: execution type and autoReExecCount / autoDefectLog / autoReExecTriggerOn / newBrowserSession / terminateOnFailure / container limits. Use it to CONFIRM a setting after saving (also after a client restart — the settings live in the backend). - action:"update" — needs `suiteId` and at least one of `name`, `description`, `executionType` (the suite's Execution Type menu: "local", "remote", "cloud" or "stack"), `settings` (autoDefectLog, autoReExecCount, autoReExecTriggerOn, newBrowserSession, terminateOnFailure, minimumContainerCount, maximumContainerCount). - action:"delete" — needs `suiteId`. TWO-STEP: call without `confirm` to PREVIEW (nothing is deleted), show it to the user, and call again with `confirm:true` ONLY after the user explicitly says to delete. A suite still used by a schedule, pipeline, execution plan or test plan is refused. - action:"stack_setup" — needs `suiteId` and `stacks` (how many) or `stackConfigs`. Saves the suite's STACK setup (the Stack canvas behind Execution Type → Stack). Saves the Stack Setup (what the Stack canvas saves). Give `stacks` (a number: that many alike, test cases spread round-robin) OR `stackConfigs` (one entry per stack: its platform local / remote / cloud, browser, remote machine and, if the user says which, its test cases). `append:true` ADDS stacks to the saved setup instead of replacing it (existing stacks keep their platform; with no test cases named, all are re-spread over old + new). Every stack needs at least one test case, a REMOTE stack needs a machine, and CLOUD needs a cloud machine configured for the project. Run it afterwards with mode:"stack". `stackMode` "cloud" (default) or "local" and `browser` are the defaults for stacks that do not say. AUTO DEFECT LOGGING for the suite = action:"update" with settings:{ autoDefectLog:true } (failed steps then log a defect automatical…
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What to do with the suite. |
| append | boolean | – | action "stack_setup": add the stack(s) to the saved setup instead of replacing it. |
| browser | string | – | action "stack_setup": browser for WEB test cases (default chrome). |
| confirm | boolean | – | action "delete": true on the SECOND call, only after the user explicitly said to delete. |
| description | string | – | action "update": the new description. |
| executionType | string | – | action "update": the suite's Execution Type (the UI menu) — "stack" selects Stack execution. Sent as lastSelectedExecutionType. |
| name | string | – | action "update": the new name. |
| settings | object | – | action "update": execution settings to change. |
| 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 | – | action "stack_setup": where the stacks run (default cloud). |
| stacks | integer | – | action "stack_setup": number of stacks — with append:true, how many to ADD. Omit when stackConfigs lists them. |
| suiteId | string | – | Suite id or code (SU-12). Needed by every action. |
No output schema declared.
No examples provided.
suite_remove_testcases Remove test cases from a suite ~88
Remove one or more test cases from a suite. `tcIds` accepts ids or business keys; every occurrence of each is removed and the remaining test cases are reordered. Requires a live connection. Returns the updated suite with its test cases.
| Name | Type | Req | Description |
|---|---|---|---|
| suiteId | string | yes | The suite id to remove from. |
| tcIds | array | yes | Test case ids / business keys to remove. |
No output schema declared.
No examples provided.
suite_run Run a test suite (local / remote / cloud; now or scheduled) ~2,185
★ ORDER OF QUESTIONS (STRICT — applies whether you ask one at a time OR bundle several into a single message): when → mode → strategy (serial/parallel, IMMEDIATE runs) → release → sprint → environment → schedule fields → agent. Ask in THIS order, always — never schema-declaration order, never refusal-arrival order, never a 'natural UI' order (release first is WRONG). Skip sprint when release=''. Suites do NOT ask version / browser / device — each TC in the suite carries its own. ★ Execute an existing test SUITE — all its member test cases, in order — in the connected product. ASK the user for EVERY field the UI's Execute-suite dialog asks — never assume — in this DEPENDENCY ORDER: (0) if a previous run in this session left a config for the project, the tool refuses first asking `reuseConfig` (true=merge remembered mode/release/sprint/agent (the ENVIRONMENT is always asked), false=start fresh); (1) `when` immediate/schedule, (2) `mode` local/remote/cloud, (3) `strategy` SERIAL/PARALLEL — the UI's PARALLEL/SERIAL radio, shown for LOCAL, REMOTE and CLOUD alike (ask it for an immediate run), (4) `releaseId` (from list_releases; pass '' to skip), (5) `sprintId` (from list_sprints; skipped entirely when releaseId=''), (6) `environment` (from tc_list_environments), (7) for a schedule the start time + recurrence (ASK — Once / Every 5 Minutes / Hourly / Daily / Weekly / Monthly, never default) + end date + timezone, (8) THEN offer the eligible agent/runner. IF YOU BATCH SEVERAL REFUSED FIELDS INTO ONE AskUserQuestion, ORDER the questions EXACTLY as above (when → mode → strategy → release → sprint → environment → schedule fields → agent) — never in schema order or refusal order. UNLIKE `tc_run`, a suite does NOT ask for `versionId` or `browser` — each TC in the suite carries its own pinned version + execution platform (that's what the suite editor picks per row). ★ RECOMMEND PARALLEL when the suite has more than one test case that can run independently (they dispatch concur…
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | – | STEP 8 — for local: a credential_id from `local_agents` (this machine only; omit to auto-pick). For remote: REQUIRED — a credential_id from `remote_agents`. when:'immediate' → picked agent must be ON… |
| browser | string | – | Optional at the SUITE level — each TC in the suite has its own execution platform (that's the suite-editor pick per row). Provide only to OVERRIDE for every WEB TC. Values: 'chromium' (default), 'chr… |
| cloudRunnerId | string | – | STEP 8 (cloud) — a specific ONLINE runner id (from cloud_runners). For when:'schedule' omit to auto-pick a live VM at fire time. |
| dayOfMonth | integer | – | Monthly 'ON DAY': 1–30; default = the start's day. |
| daysOfWeek | array | – | Weekly: the weekdays to run on (MONDAY … SUNDAY or MON … SUN); default = the start's weekday. Monthly with `occurrence`: the one weekday. |
| endDate | string | – | SCHEDULE STEP — ISO end date; REQUIRED when scheduleType is anything but 'once'. ASK the user. |
| environment | string | – | STEP 6 — environment key (from tc_list_environments). ASK the user on EVERY suite run; the UI marks this required for a suite. Never inherited from a previous run — reuseConfig does not fill it. |
| headless | boolean | – | Headless. Defaults: cloud=true, local=false. (Immediate runs only.) |
| interval | integer | – | REPEAT EVERY N for hourly / daily / weekly / monthly — N hours / days / weeks / months (e.g. hourly + 2 = every 2 hours). Default 1. With 'every_5_minutes' it is the N in 'every N minutes'. Not for '… |
| maxConcurrent | integer | – | Cloud parallel only — maps to globalConfiguration.MAXIMUM_CONTAINER_COUNT on the wire. |
| mode | string | – | STEP 2 — where to run. REQUIRED, ASK the user if unstated. 'stack' runs the suite's saved Stack setup (the UI's Execution Type → Stack): set it up first with suite_manage action:'stack_setup'; immedi… |
| occurrence | string | – | Monthly 'ON THE': the first / second / third / last weekday of the month — give the weekday in daysOfWeek. |
| releaseId | string | – | STEP 4 — release from list_releases. ASK the user; pass '' to skip (no release / no sprint asked). |
| reuseConfig | boolean | – | Set only when the tool refused asking about REUSE. true = merge the previous run's mode/release/sprint/browser/agent/runner into any unset field; the ENVIRONMENT is never merged — it is asked on ever… |
| scheduleName | string | – | when:'schedule' — the schedule's NAME as the Scheduler shows it (3–501 characters, unique in the project), e.g. 'nightly smoke'. Omit it and the schedule is named '<TC-22> schedule' (numbered when ta… |
| scheduleType | string | – | SCHEDULE STEP — REQUIRED for when:'schedule'; ASK the user explicitly, never assume. The UI's Recurrence choices: 'once', 'every_5_minutes', 'hourly', 'daily', 'weekly', 'monthly'. Anything but 'once… |
| scheduledFor | string | – | STEP 6 — REQUIRED for when:'schedule'; ISO datetime of the first/only run (e.g. '2026-08-20T09:00:00Z'). |
| sprintId | string | – | STEP 5 — sprint from list_sprints (scoped to release). Only asked when releaseId is non-empty; skipped when releaseId=''. Pass '' to skip. |
| strategy | string | – | STEP 3 (immediate runs) — SERIAL or PARALLEL across the suite's test cases: the same choice the UI's Execute-suite dialog shows as a PARALLEL/SERIAL radio, and it applies to LOCAL, REMOTE and CLOUD a… |
| suiteId | string | yes | The suite id to run (from suite_list / suite_get). |
| terminateOnFailure | boolean | – | Stop dispatching remaining test cases after the first failure. Maps to globalConfiguration.TERMINATE_ON_FAIL on the wire. |
| timezone | string | – | IANA timezone for a schedule (e.g. 'Asia/Kolkata'). Default 'UTC'. |
| when | string | – | STEP 1 — when to run. REQUIRED, ASK the user if unstated. |
No output schema declared.
No examples provided.
task_create Create a task ~409
Create a TASK in the connected project — what Tasks → Create Task does — and return its key (TS-xx / TA-xx). Needs `name` and `estimatedEffort` (hours); everything else is optional and DEFAULTED, and the answer lists what was defaulted: type / state / priority = the project's own default values, planned dates = the sprint's (else the release's, else today). Optional: `description`, `assignee` (email, name, user id or "me" — one that matches nobody is refused), `releaseId` / `sprintId` (id, code or exact name; a sprint brings its release and must belong to the release named), `storyId` (the user story it belongs to: id or key), `type`, `state`, `priority`, `plannedStartDate` / `plannedEndDate` (YYYY-MM-DD). A task with the same name in the project is refused. Reads the task back. Needs the add_task privilege. Change it later with task_update.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | – | Email, name, numeric user id or "me". Default: unassigned. |
| description | string | – | – |
| estimatedEffort | number | yes | Estimate in hours. |
| name | string | yes | Task name (2–500 characters). |
| plannedEndDate | string | – | YYYY-MM-DD. |
| plannedStartDate | string | – | YYYY-MM-DD. |
| priority | string | – | – |
| releaseId | string | – | Release: id, code (RE-44) or exact name. |
| sprintId | string | – | Sprint: id, code (SP-1) or exact name; it must belong to the release. |
| state | string | – | – |
| storyId | string | – | User story it belongs to: id or key (US_123). |
| type | string | – | Task type — one of the project's own; default: the project's default type. |
No output schema declared.
No examples provided.
task_update Update a task (planned dates, assignee, state, …) ~460
Change an existing TASK — what the SimplifyQA editor does, then it READS THE TASK BACK and reports each change. Pass `taskId` (id, code like TA-3, or exact name) and only what to change: `plannedStartDate` / `plannedEndDate` (YYYY-MM-DD), `assignee` (email, name, user id or "me" — one that matches nobody is refused) or `unassign:true`, `state`, `priority` (the project's own values; an unknown one is refused with the valid ones listed), `releaseId` / `sprintId` (id, code or name; a sprint brings its release; "none" clears), `storyId` (the linked user story; "none" clears), `name`, `description`, `estimatedEffort`, `actualEffort`, `remainingEffort`. Needs the add_task privilege. A start date after the end date is refused — move the end date too.
| Name | Type | Req | Description |
|---|---|---|---|
| actualEffort | number | – | – |
| assignee | string | – | Who to assign it to: email (rohini.k@simplify3x.com), name, numeric user id, or "me". |
| description | string | – | – |
| estimatedEffort | number | – | – |
| name | string | – | New name (at least 3 characters). |
| plannedEndDate | string | – | YYYY-MM-DD. |
| plannedStartDate | string | – | YYYY-MM-DD. |
| priority | string | – | – |
| releaseId | string | – | Release: id, code (RE-44) or exact name; "none" clears it (and the sprint). |
| remainingEffort | number | – | – |
| sprintId | string | – | Sprint: id, code (SP-1) or exact name; it must belong to the task's release. "none" clears it. |
| state | string | – | – |
| storyId | string | – | Linked user story: id or key (US_123); "none" unlinks it. |
| taskId | string | yes | Task id, code (TA-3) or exact name. |
| unassign | boolean | – | true = clear the assignee. |
No output schema declared.
No examples provided.
tc_automate Turn a manual test case into a recording guide (creates a NEW automated TC) ~259
Read an EXISTING MANUAL test case and return a recording guide the model uses to drive a live recording via the connected agent's granular tools (web_launch_application, web_snapshot, web_click, web_enter_text, …, core_close_session). The Electron recorder window opens automatically on web_launch_application; each captured step streams into it. The user reviews and clicks Save in the recorder — that CREATES A NEW automated test case (via POST /tm/testcase); the source manual TC is left untouched. Pass `url` unless the manual steps already contain one, and `extra` for credentials / data / what to assert. Read-only from MCP: this tool composes text, it never writes. Requires a live connection.
| Name | Type | Req | Description |
|---|---|---|---|
| app_path | string | – | DESKTOP test cases only (tcType DESKTOP): the full path of the application's .exe. A DESKTOP test case needs no `url`; its guide uses the desktop_* tools. |
| extra | string | – | Extra guidance for the recording: credentials, data, assertions. |
| tcId | string | yes | The manual test case id (or business key TC_123) to automate. |
| url | string | – | Starting URL for the recording (the app under test). |
No output schema declared.
No examples provided.
tc_clone Save a test case as a new test case (same project + module) ~486
FOR TEST CASES ONLY. NOT for reusable functions: if the user names an `FN_*` key or asks to clone a function, use `fn_clone` instead. Trigger words for THIS tool: "test case", "TC", "TC_", "scenario", "script". Save an existing test case as a NEW test case (new TC id) in the SAME project + module. Mirrors the FE in-editor "Save as new TC" dialog (operation: SAVEASNEWTC). Clones ONE source version — pass `sourceVersionId` to pick which; defaults to the TC's currently selected version. `tcId` accepts the numeric id or business key (`TC_*`). `newName` is REQUIRED — backend rejects an empty name on SAVEASNEWTC. 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 |
|---|---|---|---|
| newName | string | yes | Name for the new test case (required by backend). |
| sourceVersionId | string | – | Which version of the source TC to clone; defaults to the TC's current 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… |
| tcId | string | yes | The source test case id or business key (e.g. TC_123). |
| 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.
tc_delete Delete a test case (two-step confirm) ~134
Soft-delete an existing test case in the connected product. TWO-STEP CONFIRM: call once with just `tcId` to preview the target (title + step count) and get a warning; then call again with `{ tcId, confirm: true }` to actually delete. Refuses to delete without `confirm:true`. `tcId` accepts the product's id or business key. Requires a live connection (qa_connect). Product-neutral.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Set to true on the SECOND call to actually delete. |
| tcId | string | yes | The test case id (or business key) to delete. |
No output schema declared.
No examples provided.
tc_draft_create Create a test-case draft ~897
MANUAL-ONLY authoring. Call this when the user asked for a MANUAL test case: they said "manual", "draft only", "plain prose", "no automation", or asked to cover a user story's acceptance criteria as manual cases. For those, this IS the right tool — call it. Do NOT use for automated tests. "create a test case", "record this flow", "add a test for X" (with no "manual" qualifier) mean AUTOMATED — route to the `web` / `mainframe` sub-agent to RECORD with real locators instead. Create a new in-memory test-case draft from steps you author yourself. Nothing is persisted -- no disk, no backend, no network. Use tc_draft_open to hand it to the test-case editor for viewing. DO NOT USE THIS FOR A REAL WEB APPLICATION. Steps written here have no locators, so the test case cannot execute -- it only reads plausibly. Whenever there is an app you can reach (the user gives a URL, names an environment, or asks for a test of a real flow), call the `web` sub-agent instead: that captures real locators, real element names and real parameters, and is the DEFAULT way to create a web test case. You do not need the user to say "record" -- if a test case for a real app is wanted, recording is how it is made. Legitimate uses: a MANUAL test case the user explicitly asked for (no automation), API/database steps that need no element binding, restructuring or drafting steps the user supplied verbatim, or sketching a plan when no app is reachable -- and say plainly that the result is not executable until recorded. PARAMETERISE EVERY DYNAMIC VALUE — this is mandatory for manual test cases whenever the step names a URL, credential, product name, form value, expected string, or anything the tester will type / compare. Instead of hard-coding "Enter admin in the Username field", write "Enter ${username} in the Username field" and pass `data: { username: "admin" }` at the TC level. Every `${name}` token becomes a Local parameter in the product and the value from `data` populates the test case's defa…
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| data | object | – | Default values for the `${name}` tokens in step descriptions — one entry per token. Populates the auto-created default test-data row (ITR-1) on save. Example: `{ username: "admin", password: "admin12… |
| description | string | – | Optional test-case description / summary. |
| executionPlatform | object | – | SimplifyQA-only, ANDROID/IOS only: the device the test case targets — { id: <device serial>, name, technologyType: "ANDROID"|"IOS", type: "REAL_DEVICE"|"CLOUD_DEVICE" }. The backend rejects a mobile… |
| folderOrModule | string | – | SimplifyQA-only: id of the MODULE / folder to file this test case under on save (from list_modules). ASK the user which module before drafting; SimplifyQA files test cases in a module tree. Walnut ig… |
| priority | string | – | – |
| steps | array | – | – |
| storyRef | string | – | Link this test case to a USER STORY — its id or business key (US_123, from story_list / story_get). Used when drafting MANUAL test cases for a story so they save linked to it. |
| technologyType | string | – | SimplifyQA-only: the test case's TECHNOLOGY (the form's Type) — WEB | API | ANDROID | IOS | DATABASE | MAINFRAME | DESKTOP | SAP. Applies to MANUAL test cases too (a manual Desktop/Android/iOS/API ca… |
| title | string | yes | – |
No output schema declared.
No examples provided.
tc_draft_discard Discard a test-case draft ~38
Delete an in-memory draft. Nothing was ever persisted, so there is nothing else to undo.
| Name | Type | Req | Description |
|---|---|---|---|
| draftId | string | yes | – |
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.