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 →
tc_draft_from_journal Load a recording journal as an automation draft ~195
Load the steps from a recording session (the journal on the connected agent) into a new AUTOMATION draft. Use this to save a recording that finished — including one from an earlier session. Then review with tc_draft_get and persist with tc_save. If the recording targeted an existing TC, pass its id via `tcId` so the draft inherits title/module/project and tc_save UPDATES that TC instead of creating a new one. Requires a live connection (qa_connect) with an agent that owns the recording journal.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | yes | The recording session id — the same id used when the recording started. |
| tcId | string | – | Optional: an existing TC id to inherit title/module/project from (and to UPDATE on save). |
| title | string | – | Optional draft title (overrides tcId meta). Defaults to "Recording <sessionId>" when no tcId is passed. |
No output schema declared.
No examples provided.
tc_draft_from_tc Load an existing test case as a draft for in-place editing ~282
Fetch a REAL test case from the connected product and hydrate it into a draft, carrying the original tcId. Because the draft carries the id, a later `tc_save({ draftId })` UPDATES that SAME test case (preserving id, run history, parameters, testdata bindings, and suite membership) instead of creating a sibling. THIS is the tool for "tag/retag this EXISTING test case with a user story or module" — `journal_modify`'s `set_meta` does NOT support that on SimplifyQA (journal-only ops there), so this draft round-trip is the only path: 1. tc_draft_from_tc({ tcId }) 2. tc_draft_update({ draftId, ops: [{ op: "set_meta", patch: { storyRef?, folderOrModule?, title?, priority?, ... } }] }) — resolve a story/module NAME to an id via story_list / list_modules FIRST; never guess one. 3. tc_save({ draftId }) Same three steps also apply to applying a `story_sync_testcases` drift report (pass the filtered `proposedOps` at step 2 instead of a set_meta patch). Requires a live connection (qa_connect).
| Name | Type | Req | Description |
|---|---|---|---|
| tcId | string | yes | The existing test-case id to load as a draft. |
No output schema declared.
No examples provided.
tc_draft_get Get a test-case draft ~37
Fetch a draft by id: readable steps table, validation summary, and the neutral TestCase.
| Name | Type | Req | Description |
|---|---|---|---|
| draftId | string | yes | – |
No output schema declared.
No examples provided.
tc_draft_open Open a draft in the test-case editor ~85
Show this draft in the product's real editor. Prefers the local agent's own native window when the agent is running; otherwise returns a link to open. The draft rides in the URL fragment -- nothing is uploaded, no backend call is made.
| Name | Type | Req | Description |
|---|---|---|---|
| draftId | string | yes | – |
| frontendOrigin | string | – | – |
| useAgentWindow | boolean | – | – |
No output schema declared.
No examples provided.
tc_draft_update Update a test-case draft ~587
Apply one or more ops (set_meta | add_step | update_step | remove_step | move_step | duplicate_step) to a draft. Steps renumber contiguously from 1 after every op. To COPY a step ("add the same step 2 at the end") use duplicate_step { n, at? } — never rebuild it with add_step: duplicate_step clones the WHOLE step (parameters and their values, object, flags, browser, API request, settings) so nothing is lost. For an IF / loop / function block pass `through` too (the last step of the block). update_steps { where, patch } applies ONE patch to EVERY step matching `where` (numbers, from/to, stepType, actionType, object, descriptionContains, parameter) — use it for "skip every step that uses X"; an empty `where` is refused unless all:true. To change WHICH parameter a step uses, put `swapParams: [{ from, to, value? }]` in the step patch (it replaces the parameter in the SAME slot; `recordedParam` only adds). To edit a project parameter itself (Local <-> Runtime, default value) use parameter_update. To change an API step IN PLACE (add an assertion, change the URL / a header / the body) use update_step with `patch.api`: it is MERGED into the saved request, so only what you pass changes. `api.addAssertions: [{ path, condition, expectedValue }]` appends assertions (e.g. path "statusCode", "$.body.id", "$.headers.X"); `api.assertions` replaces the whole list. NEVER remove_step + add_step to edit a step — that deletes it and creates a different one. STEP TYPE — for add_step / update_step on a MANUAL test case (tc.category === "manual", or every existing step arrived with stepType "manual"), pass `stepType: "manual"`. For an AUTOMATED test case pick the execution technology ("web", "api", "android", …). Getting this wrong routes the row to the wrong UI card and it renders blank in the desktop viewer. CALLING A SAVED FUNCTION — a function step is `{ stepType: "function", actionType: "function", description, functionCall: { testCaseId: "FN-12" } }` (the numeric id also works).…
| Name | Type | Req | Description |
|---|---|---|---|
| draftId | string | yes | – |
| ops | array | yes | – |
No output schema declared.
No examples provided.
tc_edit_open Open an existing test case for live prompt-driven step editing ~401
One-shot: hydrate an EXISTING test case as a draft, open it in the desktop TC-viewer window, and bind a live-edit session so subsequent tc_draft_update calls stream the changes into the window in real time (TC_EDIT_RESYNC on each op batch, per plan/tc-edit-live-protocol.md). ⚠️ THIS OPENS THE DESKTOP RECORDER/VIEWER WINDOW (scrcpy / SCRPY). Use it ONLY when the user explicitly wants to WATCH the edits live or asks to open the test case in the viewer. For a plain prompt like "add a step to TC N at step 3", "remove step 2", "change step 3" do NOT use it — call journal_modify({ tcId, ops:[{ op:"add_step", at, step }] }), which edits the saved test case directly with no window. Returns { draftId, sessionId, tcId }. Follow up with tc_draft_update({ draftId, ops }) for edits and tc_save({ draftId }) to persist. Requires a live connection (qa_connect); the desktop app must be running on the same machine or the window-open call silently no-ops (the draft still mutates correctly — only the live view is lost).
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | – | Bearer token forwarded to the desktop window for API calls. |
| baseUrl | string | – | sqa-ui origin (defaults to whatever the desktop app is configured with). |
| hashRoute | string | – | Optional Angular hash route override, e.g. "#/user/testcase/details/593". Defaults to "#/user/testcase/details/<numericTcId>" (matches the browser UI route). Pass this only if the product's testcase-… |
| projectId | string|number | – | – |
| tcId | string | yes | The existing test-case id to open for editing. |
| userId | string|number | – | – |
No output schema declared.
No examples provided.
tc_generate_testdata Save generated testdata rows to a test case ~660
Persist up to 20 testdata rows for TC `tcId` into a SPECIFIC environment. Testdata is stored per environment — rows saved here only affect the env you pass. WORKFLOW: (1) call tc_list_environments and ASK the user which env; (2) call tc_get_testdata with that env to read seeds; (3) call this tool with the SAME `environmentType`. `environmentType` is REQUIRED here — this tool refuses when it is omitted. Two ways to feed values: 1) Model-generated — pass `rows: [{paramName: value}, ...]`. Call tc_get_testdata first for the parameter names + seeds, tc_get for step context, then produce rows that fit the flow. 2) Formula-driven — pass `formulas: {paramName: {name, args?}}` (names from tc_list_formulas). Each formula is evaluated per row by the SimplifyQA desktop AGENT (the same engine the UI and the executor use, so every formula from tc_list_formulas works, including nested ones) and both the value and the source `=NAME(...)` expression are stamped. The agent must be running (QA_MCP_URL). For nested / custom formulas pass `expression` instead of `name`+`args`. Use `count` to say how many rows, or provide `rows` for constant columns; mixing is fine (formulas win over row values for the same param). Rows are appended as new iterations; they do not become the default. Hard cap: 20 rows. VERSIONS: SimplifyQA TCs can have multiple versions with different params. When the TC has more than one version and `versionId` is omitted, this tool REFUSES and lists the available versions — ASK the user which one, then call again with `versionId`. Pass `versionId: ''` to accept the TC's currently-selected version.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many rows to generate when using formulas without explicit rows. Ignored if rows is set. |
| entityType | string | – | 'TC' (default) = `tcId` is a test case. 'FN' = `tcId` is a reusable FUNCTION id — reads/saves the FUNCTION's own testdata iterations. |
| environmentType | string | – | Env `key` (from tc_list_environments). REQUIRED — this tool refuses when omitted. Ask the user which env before generating. |
| formulas | object | – | Per-column formula assignments applied to every row. Outer keys are param names from tc_get_testdata. Wins over rows[i] for the same key. |
| rows | array | – | Rows keyed by param name (from tc_get_testdata). 1..20 rows. Omit when using formulas + count. |
| tcId | string | yes | Test case id (or business key like TC_123). With entityType "FN": the function id. |
| versionId | string | – | Version to save testdata into (an id from the TC's `versions[]`). Omit to trigger the ASK-user prompt when the TC has multiple versions. Pass '' to accept the TC's currently-selected version without… |
No output schema declared.
No examples provided.
tc_get_testdata Read the current testdata template for a test case ~556
Fetch the default iteration (template row) for TC `tcId` in a specific environment — the parameter list plus the CURRENT seed values. Testdata is per-env: seeds may differ across envs. `environmentType` is REQUIRED — this tool refuses when it is omitted, since silently guessing an env previously caused false "testdata not found" results. FIRST call tc_list_environments and ask the user which env they want. Then read the template here, and use the seeds + the test case's steps (from tc_get) to reason about realistic values before calling tc_generate_testdata. VERSIONS: SimplifyQA TCs can have multiple versions with different params/seeds. When the TC has more than one version and `versionId` is omitted, this tool REFUSES and lists the available versions — ASK the user which one, then call again with `versionId`. Pass `versionId: ''` to accept the TC's currently-selected version. Single-version TCs are read directly. FUNCTIONS: if a step in this TC calls a reusable FUNCTION, the `parameters` array (and the row list in this response's text) includes ONE extra row for it — a row whose "seed" is the function's NAME + VERSION, not its testdata (a called function's testdata is its own separate tc_get_testdata call, never guessed or fabricated here). It is a normal row in the SAME table as the TC's own parameters — do not pull it out into separate prose afterward. When one or more functions were called, this response ALSO ends with an explicit prompt listing each one and the exact tc_get_testdata args to fetch its testdata — ASK the user which (if any) they want BEFORE calling tc_get_testdata again for a function; do not fetch one unprompted, and do not skip the ask just because there is only one.
| Name | Type | Req | Description |
|---|---|---|---|
| entityType | string | – | 'TC' (default) = `tcId` is a test case. 'FN' = `tcId` is a reusable FUNCTION id — reads/saves the FUNCTION's own testdata iterations. |
| environmentType | string | – | Env `key` (from tc_list_environments). REQUIRED — this tool refuses when omitted. Ask the user which env before reading testdata. |
| tcId | string | yes | Test case id (or business key like TC_123). With entityType "FN": the function id. |
| versionId | string | – | Version to read testdata for (an id from the TC's `versions[]`). Omit to trigger the ASK-user prompt when the TC has multiple versions. Pass '' to accept the TC's currently-selected version without p… |
No output schema declared.
No examples provided.
tc_heal Diagnose and heal a failed test-case run ~326
One-shot alias for heal_plan + heal_apply. Default `mode:"suggest"` only diagnoses and proposes — it writes NOTHING. Pass `mode:"apply"` (new version) or `mode:"apply_and_verify"` (new version + re-run) to write. Covers objects (locators/properties), actions (per step only — the catalog is never modified), parameters, and the test data of the failing iteration. Every response carries a classification and rationale, even when the failure is not healable (app bug, bad business data, environment).
| Name | Type | Req | Description |
|---|---|---|---|
| confirmSharedObject | boolean | – | Required when applying a plan that changes an object used by other test cases. |
| domains | array | – | Limit which domains may change (default: all). |
| maxAttemptsPerStep | integer | – | Replay retries at the failing step. Default 3. |
| mode | string | – | Default 'suggest' (no writes). 'apply' persists a NEW version; 'apply_and_verify' also re-runs. |
| runId | string | – | Specific failed run to heal against. |
| tcId | string | yes | The failing test case id. |
| 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 for the replay. |
No output schema declared.
No examples provided.
tc_list_environments List environments configured for the connected project ~101
List every environment configured for the currently connected project (e.g. general, staging, production). Testdata is stored PER ENVIRONMENT — each env has its own iteration rows. ALWAYS call this before tc_get_testdata / tc_generate_testdata, show the user the options, and ASK which env they want to generate testdata for. Never assume. The value to pass onward as `environmentType` is the `key` field on each returned env.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tc_list_formulas List testdata formulas available in the current project ~181
Return the formulas the connected project can use for testdata generation — DEFAULT prefabs (FIRST_NAME, LAST_NAME, COUNTRY_NAME, EMAIL_ID, PHONE_NUMBER, …) plus any CUSTOM formulas defined at customer or project scope. EVERY line starts with the NAME to pass as `name`; the parenthesised part after it is the human signature (it can differ — e.g. the name is EMAIL_ID while its signature reads EMAIL(...)), and `args:` lists the argument keys the formula accepts (matched case-insensitively). Feed a chosen `{name, args}` into `tc_generate_testdata.formulas` and that column is auto-filled fresh per row by the agent's formula engine. Use this when the user says "use a formula" / "generate an email" / "first name, phone, country…" / "list formulas".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tc_record_append Record additional steps into a TC that is already open in the editor ~277
Start a live-browser recording session whose captured steps stream into the tc-viewer window bound by an earlier `tc_edit_open`. Each user interaction becomes a TC_EDIT_INSERT event in the editor. Returns instructions the model must follow (this tool itself does not touch the driver): 1. `core_activate_technology({ technology:"WEB", mcpTcEditSessionId, testcaseName })` — starts the browser and binds captures to this window. The response `structuredContent.sessionId` is the RECORDING session id — remember it for step 3. 2. Use `web_*` tools to drive the browser. Every captured step shows up live in the editor. 3. When done, `tc_record_stop({ draftId, recordingSessionId })` reads the recording journal and appends the captured steps to the draft. Then `tc_save({ draftId })` to persist. A DESKTOP test case gets a desktop guide instead: technology "DESKTOP", `desktop_launch_application({ app_path })` first, then `desktop_snapshot` + `desktop_*` verbs. The draft must have been opened via `tc_edit_open` first — its stored sessionId is what binds the recorder to the correct window.
| Name | Type | Req | Description |
|---|---|---|---|
| draftId | string | yes | The draft id from tc_edit_open. |
No output schema declared.
No examples provided.
tc_record_stop Append recorded steps to the draft after tc_record_append ~172
Read the recording journal for a session and add each captured step to the draft as an `add_step` op. Pairs with `tc_record_append`. Follow with `tc_save({ draftId })` to persist. CAVEAT: The recording journal is process-scoped and may contain steps from earlier recordings in the same Java-server process. Pass `fromIndex` to skip the first N steps if the journal accumulated prior state — usually the count of steps recorded before `tc_record_append` was called.
| Name | Type | Req | Description |
|---|---|---|---|
| draftId | string | yes | – |
| fromIndex | integer | – | Optional: skip the first N steps in the journal (defaults to 0 = take all). |
| recordingSessionId | string | yes | The session id from `core_activate_technology`'s response.structuredContent.sessionId. |
No output schema declared.
No examples provided.
tc_replace_with_functions Replace steps of a SAVED test case with existing functions ~223
After the user has chosen (from tc_suggest_functions) which functions to use, swap the matching steps of an already-saved test case for a call to each chosen function. Use this when the user saved from the recorder window; if the recording is not saved yet, pass the choice to tc_save instead. `functionIds` = the user's picks; omit for all matches. The replaced steps' own testdata is dropped and the function's default iterations are used. ONLY call after the user said yes.
| Name | Type | Req | Description |
|---|---|---|---|
| functionIds | array | – | Function ids to apply (from tc_suggest_functions). Omit = all matches. |
| replace | array | – | Explicit picks: replace exactly these seqs with these functions, skipping the matcher. Takes precedence over functionIds. This is the "use FN-12 for steps 3-6" path. |
| tcId | string | yes | Saved test case id or business key. |
| versionId | string | – | Version to edit (an id from the TC versions[]). Omit for the current version. |
No output schema declared.
No examples provided.
tc_run Run a test case (local / remote / cloud; now or scheduled) ~2,448
★ ORDER OF QUESTIONS (STRICT — applies whether you ask one at a time OR bundle several into a single message): when → mode → release → sprint → version → environment → browser/device → 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 a step only when the flag below says it's skippable (sprint when release='', version when TC has one version, browser vs. device by TC type). ★ Execute ONE existing test case in the connected product. ASK the user for EVERY field the Execute 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/env/browser/agent, false=start fresh); (1) `when` immediate/schedule, (2) `mode` local/remote/cloud, (3) `releaseId` (from list_releases; pass '' to skip — no release), (4) `sprintId` (from list_sprints; skipped entirely when releaseId=''), (5) `versionId` (from tc_get's `versions[]`; pass '' for current), (6) `environment` (from tc_list_environments), (7) FOR WEB TCs: `browser`; FOR ANDROID/IOS TCs: `deviceType` + `deviceId` (via `mobile_list_devices`), (8) for a schedule the start time + recurrence (ASK — Once / Every 5 Minutes / Hourly / Daily / Weekly / Monthly, never default) + end date + timezone, (9) THEN offer the eligible agent/runner and pass the pick. IF YOU BATCH SEVERAL REFUSED FIELDS INTO ONE AskUserQuestion, ORDER the questions EXACTLY as above (when → mode → release → sprint → version → environment → browser/device → schedule fields → agent) — never in schema order or refusal order. `mode` decides WHERE it runs: • 'local' — THIS machine's desktop agent (its own browser). Call `local_agents` (0 or 1 row per box). For when:'immediate' the tool first probes the desktop agent (:4040) and refuses cleanly if it's not up. Omit `agentId` to auto-pick this mach…
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | – | STEP 9 — for local: a credential_id from `local_agents` (must be THIS machine's row; omit to auto-pick). For remote: REQUIRED — a credential_id from `remote_agents`. when:'immediate' → the picked age… |
| browser | string | – | STEP 7 (WEB TCs) — browser, default 'chromium' (bundled + isolated). Others: 'chrome'/'msedge' (installed channel), 'firefox', 'webkit'. ON THE CLOUD (mode 'cloud') the ONLY choices are Chrome Headle… |
| cloudDeviceType | string | – | REQUIRED when `deviceType` is cloud_* — which cloud farm the device came from (read off the matching row's `cloudDeviceType`). |
| cloudRunnerId | string | – | STEP 9 (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. |
| deviceId | string | – | STEP 7 (ANDROID/IOS TCs) — the target device id. LOCAL: adb serial or emulator name. CLOUD: the marketplace device name. Enumerate with `mobile_list_devices`. |
| deviceName | string | – | STEP 7 (ANDROID/IOS TCs) — the human-readable device name (e.g. 'Oppo-Cph2375-Ab1fe936', 'Pixel 7'). Read off the matching row's `displayName` (preferred) or `name` field from `mobile_list_devices`.… |
| deviceType | string | – | STEP 7 (ANDROID/IOS TCs) — the KIND of device the picked `deviceId` is (read off the matching row from `mobile_list_devices`). |
| devices | array | – | STEP 7 (ANDROID/IOS TCs) — for PARALLEL execution on MULTIPLE devices. Pass an array of device specs to create ONE execution with one run per device (parallel). When provided, the single-device field… |
| 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 run; the UI marks this required. 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 '… |
| mode | string | – | STEP 2 — where to run. REQUIRED, ASK the user if unstated. |
| occurrence | string | – | Monthly 'ON THE': the first / second / third / last weekday of the month — give the weekday in daysOfWeek. |
| osVersion | string | – | Optional OS version to stamp on the wire platform object for ANDROID/IOS — read off the matching row from `mobile_list_devices`. |
| releaseId | string | – | STEP 3 — tag the run with a RELEASE (from list_releases). Optional in the UI; pass '' after asking to skip. The tool refuses when undefined so the user is 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 8 — REQUIRED for when:'schedule'; ISO datetime of the first/only run (e.g. '2026-08-20T09:00:00Z'). |
| sprintId | string | – | STEP 4 — tag the run with a SPRINT (from list_sprints, scoped to release). Only asked when releaseId is non-empty; skipped entirely when releaseId=''. Pass '' after asking to skip. |
| strategy | string | – | STEP 3 (IMMEDIATE runs) — SERIAL or PARALLEL: the same PARALLEL/SERIAL radio the UI's Execute dialog shows above Release (it applies to LOCAL, REMOTE and CLOUD alike). ASK the user; the tool refuses… |
| tcId | string | yes | The test case id (or business key) to run. |
| timezone | string | – | IANA timezone for a schedule (e.g. 'Asia/Kolkata'). Default 'UTC'. |
| versionId | string | – | STEP 5 — override the TC's currently-selected VERSION for this run (an id or name from the TC's `versions[]`). Pass '' to accept the TC's current version. |
| when | string | – | STEP 1 — when to run. REQUIRED, ASK the user if unstated (the tool refuses when omitted). 'immediate' dispatches now; 'schedule' creates a schedule (needs scheduledFor). |
No output schema declared.
No examples provided.
tc_save Save a draft or a live recording ~647
Persist a test case to the connected product. Pass EXACTLY ONE of: • `draftId` — validate and save a draft (create, or update when the draft carries an id). • `sessionId` — save a LIVE/RECENT recording by asking the /mcp-recorder window to click its OWN Save button. This is the exact-parity path: the recorder editor saves the steps, objects, parameters, control flow, functions, API popup values and title/module/story that the user is looking at, including edits made in the window. The recorder window must be open; it stays open for review after saving. Returns the created test case id + deep link. Requires a live connection (qa_connect). EXCEPTION — API recordings: after the LAST `api_send_request`, call this ONCE with the sessionId WITHOUT asking, so the recorded API test case is persisted and searchable immediately (the user must not have to click Send and Save first). Only once per recording; never per request. ⚠️ OTHERWISE CALL ONLY ON AN EXPLICIT USER SAVE INSTRUCTION (e.g. "save it", "save this", "persist it"). RECORDING or AUTHORING a test case is NOT a save instruction; neither is the user approving the content ("looks good", "nice"). After a recording/draft finishes, SHOW the steps and ASK — do NOT auto-save. When unsure whether a reply meant save, ASK rather than saving. Never save a recording TWICE (UI Save + tc_save): if the user already clicked Save in the recorder, treat it as done.
| Name | Type | Req | Description |
|---|---|---|---|
| allowDuplicate | boolean | – | Set true ONLY after the user confirms they want a new test case with the same name as an existing one. Default: a new test case whose name already exists is saved as name_1, name_2, …. |
| copyTestdataFrom | string | – | Optional source TC id (or TC code). After the recording is saved, copy that TC's default-iteration testdata onto the new test case, matching parameters BY NAME. Use this when converting a manual TC (… |
| draftId | string | – | Draft id from tc_draft_create / tc_draft_open. Omit when saving a live recording. |
| replaceWithFunctions | – | – | Function reuse. Before saving, the steps are compared with the project's existing functions. If some already exist as a function and this is OMITTED, the tool does NOT save — it returns the matches a… |
| sessionId | string | – | Recording session id from core_activate_technology (or core_active_recordings). Saves via the recorder window's own Save button. |
No output schema declared.
No examples provided.
tc_save_as_new_version Snapshot a test case as a new version ~604
FOR TEST CASES ONLY. NOT for reusable functions: if the user names an `FN_*` key or asks to snapshot / create a new version of a function, use `fn_save_as_new_version` instead. Trigger words for THIS tool: "test case", "TC", "TC_", "scenario", "script". Freeze the CURRENT server state of a test case under a NEW version name — same TC id, a new version row with cloned steps. Mirrors the SimplifyQA UI "Save as new version" dialog (operation: SAVENEWVERSION). `tcId` accepts the numeric id or business key (`TC_*`). `versionName` must be unique for this TC — 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 TC's currently selected version. Requires a live connection.
| Name | Type | Req | Description |
|---|---|---|---|
| fromDraftId | string | – | Freeze THIS edited draft as the new version instead of the stored state — the "update + save as new version" path. Load it first with tc_draft_from_tc({tcId}) (+ tc_draft_update), then pass its draft… |
| sourceVersionId | string | – | Version to snapshot; 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 test case id or business key (e.g. TC_123). |
| 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 | – | Name for the new version. OMIT to auto-increment (v1.0 → v2.0 → v3.0 …) from the versions already on the TC — the normal path for an update. If given it must be unique for this TC. |
No output schema declared.
No examples provided.
tc_steps_to_function Extract selected steps of a test case into a new reusable function ~893
Take a subset of the steps on an EXISTING test case and save them as a new reusable function (SimplifyQA STEPSTOFN operation). Mirrors the FE "Save as function" modal. Steps are picked by their current `seq`, resequenced 1..N in the new function, and filed under `moduleId`. `tcId` accepts the numeric id or business key (TC_123). Requires a live connection (qa_connect). CALL THIS when the user says things like "save these steps as a function", "convert the first N steps to a function", "extract these steps into a function". Show the steps of the TC first (via tc_get) so the user can confirm which `seq`s to extract, and ASK the user which module to file the new function under — call `list_modules` if the module id is not known. VERSIONS: SimplifyQA TCs can have multiple versions with DIFFERENT step counts/content. When the TC has more than one version and `versionId` is omitted, this tool REFUSES and lists the available versions — ASK the user which version's steps to convert, read that version's steps with tc_get({ id, versionId }) to confirm the `seq`s, then call this tool again with the SAME `versionId`. Pass `versionId: ''` to accept the TC's currently-selected version without prompting. Single-version TCs are used directly. `executionType` forces every picked step into the AUTOMATION or MANUAL bucket; omit to split by each step's own executionType (function will be DUO if both are present). TESTDATA: iterations from the source TC version are copied to the new function by default. The backend prunes them to only the parameters the extracted steps reference (via key-based matching in tcfn.service.js `compareDatas` `isStepsToFn` mode), across every environment the source version has. Pass `copyTestData: false` if you explicitly want a bare function. REPLACE-IN-SOURCE: pass `replaceInSource: true` to also splice a FUNCTION + FUNCTION_END pair back into the source TC in place of the extracted steps (mirrors the FE "Save & Replace" button). The extracted rows are…
| Name | Type | Req | Description |
|---|---|---|---|
| copyTestData | boolean | – | Copy the source version's testdata iterations to the new function (backend prunes to only the params the extracted steps use). Default: true. |
| executionType | string | – | Force all picked steps into this bucket; omit to split by each step's own executionType. |
| moduleId | integer | yes | Module id to file the new function under. Resolve via list_modules if unknown. |
| name | string | yes | Name for the new function. |
| replaceInSource | boolean | – | Replace the extracted steps on the source TC with a FUNCTION + FUNCTION_END call to the new function. Default: false (create-only). Requires contiguous stepSeqs and refuses DUO/SYNCON/control-flow sp… |
| stepSeqs | array | yes | Current `seq` numbers of the steps to extract (e.g. [1,2,3,4] for the first four). Must be contiguous when replaceInSource is true. |
| tcId | string | yes | The source test case id or business key (e.g. TC_123). |
| versionId | string | – | Version to extract steps FROM — an id from the TC's `versions[]`, from a real tc_get read the user directed. REQUIRED whenever the TC has more than one version (this tool refuses when it's omitted OR… |
No output schema declared.
No examples provided.
tc_suggest_function_groups Suggest functions for the steps just recorded (create + replace) ~300
THE post-recording step: call this as soon as a recording finishes and BEFORE asking the user to save. It returns BOTH kinds of suggestion in one answer: `replace` — blocks of recorded steps that already exist as a reusable function (offer to swap them for a call to that function), and `create` — contiguous blocks that are good candidates for a NEW reusable function (offer to extract them). Read-only: nothing is created, replaced or saved. Show both lists and ASK the user per block: create as a new function (ask for the name) / replace with the existing FN-x / keep as recorded. Apply AFTER the test case is saved (tc_steps_to_function with replaceInSource:true, or tc_replace_with_functions). Pass EXACTLY ONE of `sessionId` (a finished recording), `draftId`, or `tcId` (already saved).
| Name | Type | Req | Description |
|---|---|---|---|
| draftId | string | – | A draft id (tc_draft_from_journal / tc_draft_from_tc / tc_draft_create). |
| groupSize | integer | – | Target steps per proposed new function. Default 6, minimum 3. |
| sessionId | string | – | Recording session id (core_activate_technology / core_active_recordings). |
| tcId | string | – | A saved test case id or business key. |
| versionId | string | – | For tcId only: which version to analyse (an id from the TC versions[]). |
No output schema declared.
No examples provided.
tc_suggest_functions Suggest existing functions for the recorded steps ~291
Call this RIGHT AFTER a recording finishes (before asking the user to save). It compares the recorded steps with the project's existing reusable functions and returns the groups of steps that already exist as a function. If it returns matches, show them to the user and ASK which function(s) to replace (all / some / none) — do not decide for them. Read-only: nothing changes. Pass EXACTLY ONE of `sessionId` (live/finished recording), `draftId`, or `tcId` (already saved).
| Name | Type | Req | Description |
|---|---|---|---|
| draftId | string | – | A draft id. |
| minConfidence | string | – | For tcId only. 'exact' (default) = same action/element AND the same parameter names; 'strong' also accepts the same action/element with a different parameter set (a re-parameterised copy of the flow). |
| sessionId | string | – | Recording session id (core_activate_technology / core_active_recordings). |
| tcId | string | – | A saved test case id or business key. Matched on step IDs (actionId/objectId/stepType/technologyType + parameter names), not on display names. |
| versionId | string | – | For tcId only: which version's steps to match (an id from the TC's versions[]). Omit for the TC's currently-selected version; on a multi-version TC ASK the user first. |
No output schema declared.
No examples provided.
tc_update_testdata Update the existing test data (default iteration) of a test case ~301
UPDATE the test data a run actually uses — the DEFAULT iteration (ITR-1) — instead of appending a new row. Use this for "change/set/fix the test data", "add a formula to the test data", or whenever a value or formula must apply to the NEXT run. (tc_generate_testdata APPENDS iterations; an appended row never becomes the default, so a formula saved there does not affect the run.) Each cell takes a literal `value` or a `formula` ({ name, args? } from tc_list_formulas, or a full `expression` — nested formulas are supported). Formulas are evaluated by the SimplifyQA desktop agent; the evaluated value AND the canonical =NAME(...) expression are stored, and the executor re-evaluates at run time. Unknown/invented names and unevaluatable formulas are rejected BEFORE anything is written. Only the named cells change — every other column keeps its value — and the row is read back.
| Name | Type | Req | Description |
|---|---|---|---|
| cells | array | yes | Cells to change. Only these are touched. |
| environmentType | string | yes | Env `key` from tc_list_environments. REQUIRED — test data is per environment. |
| tcId | string | yes | Test case id or business key (e.g. TC_123). |
| versionId | string | – | Version id from the TC's versions[]. Omit on a single-version TC; pass '' to accept the current one. |
No output schema declared.
No examples provided.
test_plan Create / change / delete a SimplifyQA test plan ~412
Manage SimplifyQA TEST PLANS (the Test Plan folders under Test Execution). Read them with sqa_query collection "testPlans". Actions: - action:"create" — needs `name`; optional `parentId` (a test plan id) makes it a sub-folder. - action:"rename" — needs `testPlanId` and `name`. - action:"add" — needs `testPlanId` and `suiteIds` and/or `tcIds`; ones already in the test plan are skipped. - action:"remove_suite" — needs `testPlanId` and `suiteId`. - action:"remove_testcase" — needs `testPlanId` and `tcId` (optional `versionId` when the folder has several versions of it). Removes ONLY that test case; the plan is re-read to confirm. Suites, other test cases and sub-folders are untouched. - action:"delete" — needs `testPlanId`. TWO-STEP: the first call only previews (it deletes every folder below it too); call again with `confirm:true` ONLY after the user explicitly says to delete.
| 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. |
| name | string | – | create / rename: the name. |
| parentId | string | – | create: parent test plan id (omit for a top-level one). |
| suiteId | string | – | remove_suite: the suite to take out. |
| suiteIds | array | – | add: suite ids or codes. |
| tcId | string | – | remove_testcase: the test case to take out (id or code). |
| tcIds | array | – | add: test case ids or codes. |
| testPlanId | string | – | Every action except create: test plan id or code. |
| versionId | string | – | remove_testcase: only when the folder holds several versions of that test case. |
No output schema declared.
No examples provided.
testdata_delete_iterations Delete test-data iteration rows (test case or suite level) ~228
Delete one or more test-data iteration rows by NAME (e.g. "ITR-2") or id. Works at TEST CASE level (`entityType:"TC"` + `tcId`) and at SUITE level (`entityType:"SU"` + `suiteId`). The DEFAULT row is refused — to replace the default, first make another row the default with testdata_set_default_iteration. Use this to remove rows created by mistake. It reads the rows back after deleting and reports what remains.
| Name | Type | Req | Description |
|---|---|---|---|
| entityType | string | – | TC = a test case's own test data; SU = suite-level test data. Default TC. |
| environmentType | string | yes | Environment key from tc_list_environments (e.g. general, general_1). |
| iterations | array | yes | Iteration names (e.g. ["ITR-2"]) or ids to delete. |
| suiteId | string | – | Suite id / SU-24 (required when entityType is SU). |
| tcId | string | – | Test case id / TC-123 (required when entityType is TC). |
No output schema declared.
No examples provided.
testdata_set_default_iteration Make a test-data iteration the default (test case or suite level) ~280
Make one iteration row the DEFAULT of an environment — the row a run uses — e.g. "make ITR-2 the default for SU-23 in General". Works at TEST CASE level (`entityType:"TC"` + `tcId`) and SUITE level (`entityType:"SU"` + `suiteId`). Pass the iteration by NAME (e.g. "ITR-2") or id. The previous default simply stops being the default (it is NOT deleted — delete it afterwards with testdata_delete_iterations if wanted); other environments' defaults are kept. It reads the test data back and reports the new default; asking for the row that already is the default changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| entityType | string | – | TC = a test case's own test data; SU = suite-level test data. Default TC. |
| environmentType | string | yes | Environment key from tc_list_environments (e.g. general, general_1) — each environment has its own default. |
| iteration | string | yes | The iteration to make the default: its name (e.g. "ITR-2") or id. |
| suiteId | string | – | Suite id / SU-23 (required when entityType is SU). |
| tcId | string | – | Test case id / TC-123 (required when entityType is TC). |
No output schema declared.
No examples provided.
update_module Update a module (rename / edit description / move parent) ~216
Edit an existing MODULE — pass `id` plus any of `name`, `description`, `parentId`. Name must remain unique within the project (duplicate rejected server-side). Works regardless of whether test cases/functions/etc. are tagged to the module — no need to delete and recreate it to rename or move it. `parentId` moves the module elsewhere in the tree (pass `""` to move it to project root); moving it under itself or under one of its own descendants is refused. SimplifyQA-only. Requires a live connection.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | New description (pass "" to clear). |
| id | string | yes | Module id (numeric or business key, e.g. MO_12). |
| name | string | – | New module name. |
| parentId | string | – | New parent module id (from list_modules). Moves this module in the hierarchy. Pass "" to move it to project root instead of under another module. |
| projectId | string | – | Project id; defaults to the connected project. |
No output schema declared.
No examples provided.
watch_list_add Add members to the Watch List of an epic, feature or user story ~138
Add people to an item's WATCH LIST — the same list the UI's email button edits. `users` takes emails, full names or numeric userIds (e.g. ["rohini.k@simplify3x.com"]). Existing watchers are kept; the item is re-read to confirm. Use it after creating an item, or for an existing one.
| Name | Type | Req | Description |
|---|---|---|---|
| entityType | string | yes | Which backlog item. |
| itemId | string | yes | Item id or business key (EP-66, FT-266, US-1326). |
| users | array | yes | Emails, full names or numeric userIds to add to the Watch List. |
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.