Skip to content
Agentmart
Submit a tool

Qtm4j MCP Server

MCP server for QMetry Test Management for Jira (QTM4J): test cases, cycles, executions, plans.

Connector by salehrifai42 · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)
Write a review

Chalk Labs

Need help deploying Qtm4j MCP Server?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/salehrifai42-qtm4j-mcp-server

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

MCP server for QMetry Test Management for Jira (QTM4J): test cases, cycles, executions, plans.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
35 read · 35 write · 17 delete
Secrets
1 (API keys, tokens or passwords)
Install scripts
Not scanned yet
Runs as
Node.js package

Tools by what they do 87

Read from the source code; the running server may list different tools.

Read 35 · Look things up without changing anything.

  • qtm4j_get_automation_audit_log
  • qtm4j_get_builds
  • qtm4j_get_components
  • qtm4j_get_custom_fields
  • qtm4j_get_cycle_defect_summary
  • qtm4j_get_environments
  • qtm4j_get_execution_defects
  • qtm4j_get_execution_results
  • qtm4j_get_execution_teststeps
  • qtm4j_get_labels
  • qtm4j_get_linked_test_cycles
  • qtm4j_get_parameters
Show 23 more tools
  • qtm4j_get_priorities
  • qtm4j_get_priority_icons
  • qtm4j_get_projects
  • qtm4j_get_statuses
  • qtm4j_get_step_execution_defects
  • qtm4j_get_test_case
  • qtm4j_get_test_case_comments
  • qtm4j_get_test_case_version
  • qtm4j_get_test_cycle
  • qtm4j_get_test_cycle_comments
  • qtm4j_get_test_cycle_executions
  • qtm4j_get_test_execution
  • qtm4j_get_test_plan
  • qtm4j_get_test_plan_comments
  • qtm4j_get_test_steps
  • qtm4j_get_user_permissions
  • qtm4j_list_execution_attachments
  • qtm4j_list_folders
  • qtm4j_search_cycle_defects
  • qtm4j_search_folders
  • qtm4j_search_test_cases
  • qtm4j_search_test_cycles
  • qtm4j_search_test_plans

Write 35 · Create, change, send or run things.

  • qtm4j_add_test_case_comment
  • qtm4j_add_test_cycle_comment
  • qtm4j_add_test_plan_comment
  • qtm4j_bulk_update_test_cases
  • qtm4j_bulk_update_test_executions
  • qtm4j_clone_test_cases
  • qtm4j_create_folder
  • qtm4j_create_test_case
  • qtm4j_create_test_case_version
  • qtm4j_create_test_cycle
  • qtm4j_create_test_plan
  • qtm4j_create_test_steps
Show 23 more tools
  • qtm4j_edit_folder
  • qtm4j_link_automation_rule
  • qtm4j_link_execution_defects
  • qtm4j_link_step_execution_defects
  • qtm4j_link_test_cases_to_cycle
  • qtm4j_link_test_cases_to_requirement
  • qtm4j_link_test_cycles_to_plan
  • qtm4j_move_test_cases
  • qtm4j_run_automation_rules
  • qtm4j_unarchive_test_case
  • qtm4j_unarchive_test_cycle
  • qtm4j_unarchive_test_plan
  • qtm4j_update_execution_custom_fields
  • qtm4j_update_test_case
  • qtm4j_update_test_case_comment
  • qtm4j_update_test_cycle
  • qtm4j_update_test_cycle_comment
  • qtm4j_update_test_execution
  • qtm4j_update_test_plan
  • qtm4j_update_test_plan_comment
  • qtm4j_update_test_step_execution
  • qtm4j_update_test_steps
  • qtm4j_upload_execution_attachment

Delete 17 · Delete, drop, revoke or wipe things.

  • qtm4j_archive_test_case
  • qtm4j_archive_test_cycle
  • qtm4j_archive_test_plan
  • qtm4j_delete_execution_attachment
  • qtm4j_delete_test_case
  • qtm4j_delete_test_case_comment
  • qtm4j_delete_test_cycle
  • qtm4j_delete_test_cycle_comment
  • qtm4j_delete_test_plan
  • qtm4j_delete_test_plan_comment
  • qtm4j_delete_test_steps
  • qtm4j_unlink_automation_rule
Show 5 more tools
  • qtm4j_unlink_execution_defects
  • qtm4j_unlink_step_execution_defects
  • qtm4j_unlink_test_cases_from_cycle
  • qtm4j_unlink_test_cases_from_requirement
  • qtm4j_unlink_test_cycles_from_plan

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • QTM4J_API_KEY

Other settings (environment variables or headers).

  • QTM4J_REGION

Tools (87)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • qtm4j_add_test_case_commentAdd Test Case Comment

    Add one or more comments to a specific version of a test case. Provide either `comment` (single string) or `comments` (array of strings). versionNo is required — use qtm4j_get_test_case (versionNo field) to find the current version.

  • qtm4j_add_test_cycle_commentAdd Test Cycle Comment

    Add one or more comments to a test cycle. Provide either `comment` (single string) or `comments` (array of strings).

  • qtm4j_add_test_plan_commentAdd Test Plan Comment

    Add one or more comments to a test plan. Provide either `comment` (single string) or `comments` (array of strings).

  • qtm4j_archive_test_caseArchive Test Casecan change or delete data

    Archive a test case so it can be deleted (or hidden from active views). Uses the dedicated `PUT /testcases/{id}/archive` endpoint — DO NOT try to flip `archived:true` via bulk_update or update_test_case; those return 200 but the flag does not persist in some tenants. After this call, the case is read-only; use qtm4j_delete_test_case to permanently remove it.

  • qtm4j_archive_test_cycleArchive Test Cyclecan change or delete data

    Archive a test cycle via PUT /testcycles/{id}/archive so it can be deleted or hidden from active views. Active cycles must be archived before qtm4j_delete_test_cycle will succeed.

  • qtm4j_archive_test_planArchive Test Plancan change or delete data

    Archive a test plan via PUT /testplans/{id}/archive so it can be deleted or hidden from active views. Active plans must be archived before qtm4j_delete_test_plan will succeed.

  • qtm4j_bulk_update_test_casesBulk Update Test Cases

    Apply a set of field changes to many test cases at once. `fields` is the same shape as update_test_case (priority, status, assignee, labels {mode:'append'|'replace', values:[]}, components, fixVersions, customFields, isAutomated, summary, description, precondition, etc.). Provide testCaseIds or a filter. NOTE: archiving via `fields:{archived:true}` is a silent no-op in some tenants (returns 'Completed' but the flag doesn't flip) — use qtm4j_archive_test_case which hits the dedicated /archive endpoint.

  • qtm4j_bulk_update_test_executionsBulk Update Test Executions

    Apply the same execution result, environment, or build to multiple test case executions at once. Use testCycleTestCaseMapIds from qtm4j_get_test_cycle_executions (the 'testCycleTestCaseMapId' field).

  • qtm4j_clone_test_casesClone Test Cases

    Bulk clone one or more test cases into a target project and optional folder. Each clone gets a fresh key; original test cases keep their existing folder memberships and linkages. Returns a background task with taskId and progressUrl — poll the progressUrl until status is 'Completed' (Title case, not COMPLETED).

  • qtm4j_create_folderCreate Folder

    Create a new folder under an existing parent folder. Use parentId=-1 for root-level (0 returns 404). Use qtm4j_list_folders first to find valid parentId values.

  • qtm4j_create_test_caseCreate Test Case

    Create a new test case in QMetry. Returns the created test case object including its internal id and key (e.g. PROJ-TC-123). Priority, status, labels, and components use integer IDs.

  • qtm4j_create_test_case_versionCreate Test Case Version

    Branch a new version of a test case (optionally cloning from an existing version). Returns { id, key, versionNo }. Use this before making large edits so the previous version stays intact for prior cycles.

  • qtm4j_create_test_cycleCreate Test Cycle

    Create a new test cycle. Returns the created cycle with its internal id and key (e.g. PROJ-TR-123). Use qtm4j_list_folders with folderType=TESTCYCLE to find valid folderId values.

  • qtm4j_create_test_planCreate Test Plan

    Create a new test plan. Returns the created plan with internal id and key (e.g. PROJ-TP-44). Use qtm4j_list_folders with folderType=TESTPLAN to find valid folderId values.

  • qtm4j_create_test_stepsCreate Test Steps

    Add one or more test steps to a specific version of a test case. Each step has stepDetails (required), expectedResult, and testData. Returns the created step objects with their IDs.

Show 72 more tools
  • qtm4j_delete_execution_attachmentDelete Test-Execution Attachmentscan change or delete data

    Delete one or more attachments from a test-case execution. DELETE `/testcycles/{cycleId}/testcase-executions/{testcaseExecutionId}/attachments` with JSON body `{"attachmentIds":[…]}` (or `{"deleteAll":true}`) → 204. GOTCHAS — all of these are WRONG and return 404/400: (a) appending `/{attachmentId}` to the attachments path; (b) the path `…/testcase-executions/attachments/{id}` (no executionId in front); (c) sending a bare array body. It MUST be the collection path plus an `attachmentIds` (or `deleteAll`) JSON body.

  • qtm4j_delete_test_caseDelete Test Casecan change or delete data

    Permanently delete a test case. Irreversible. NOTE: Active (non-archived) test cases cannot be deleted — the API returns `400 You can not delete active Test Case(s)`. Archive first via qtm4j_archive_test_case, then call this. The recommended path uses `DELETE /testcases/{id}` (no version suffix); the legacy `DELETE /testcases/{id}/versions/{n}` returns 404 once the case is archived. Pass `versionNo` only if you need to delete a specific non-latest version of a multi-version test case.

  • qtm4j_delete_test_case_commentDelete Test Case Commentcan change or delete data

    Delete a comment from a test case version. Use the comment id from qtm4j_get_test_case_comments.

  • qtm4j_delete_test_cycleDelete Test Cyclecan change or delete data

    Permanently delete a test cycle and all its execution records. Irreversible. NOTE: Active cycles cannot be deleted (API returns 400). Archive first via qtm4j_archive_test_cycle, then call this.

  • qtm4j_delete_test_cycle_commentDelete Test Cycle Commentcan change or delete data

    Delete a comment from a test cycle. Use the comment id from qtm4j_get_test_cycle_comments.

  • qtm4j_delete_test_planDelete Test Plancan change or delete data

    Permanently delete a test plan. Does not delete the linked test cycles. NOTE: Active plans cannot be deleted (API returns 400). Archive first via qtm4j_archive_test_plan, then call this.

  • qtm4j_delete_test_plan_commentDelete Test Plan Commentcan change or delete data

    Delete a comment from a test plan. Use the comment id from qtm4j_get_test_plan_comments.

  • qtm4j_delete_test_stepsDelete Test Stepscan change or delete data

    Delete steps from a test case version. Provide either stepIds (array) or a filter, or set deleteAll=true to wipe all steps.

  • qtm4j_edit_folderEdit Folder

    Rename a folder or update its description in any module.

  • qtm4j_get_automation_audit_logGet Automation Audit Logread-only

    Read QMetry's automation-rule audit log — the only audit trail QTM4J exposes via API. Returns who ran what and when (entityType, action, detailMessage, created.{createdBy, createdOn}), e.g. automation-rule Execute events that may have reset/repopulated a test cycle. issueId is the automation rule's numeric id (NOT a cycle/case id). Filter by action (e.g. "Execute"), createdBy (array of Jira account ids), or createdOn (ISO 8601). NOTE: QTM4J has no general test-case/cycle/folder deletion history endpoint — for who deleted/unlinked test cases from a cycle or folder, use the QMetry UI history or …

  • qtm4j_get_buildsGet Buildsread-only

    List builds (id, name, description) for a project.

  • qtm4j_get_componentsGet Componentsread-only

    List components (id, name, description) for a project.

  • qtm4j_get_custom_fieldsGet Custom Fieldsread-only

    List custom field definitions for a module. fieldType integers: 1=text, 3=radio, 4=checkbox, 5=single-dropdown, 6=multi-dropdown, 7=date, 8=datetime, 9=number, 10=user, 11=label, 12=cascade.

  • qtm4j_get_cycle_defect_summaryGet Test Cycle Defect Summaryread-only

    Get an aggregated summary of defects for a test cycle. POST-based read with an optional filter object (e.g. { environment: 'Chrome' }).

  • qtm4j_get_environmentsGet Environmentsread-only

    List execution environments (id, name, description, isDefault) for a project.

  • qtm4j_get_execution_defectsGet Test Case Execution Defectsread-only

    List Jira defects linked to a single test case execution. POST-based read: requires the internal cycle id and the testCaseExecutionId (from qtm4j_get_test_cycle_executions). Optionally pass a filter object.

  • qtm4j_get_execution_resultsGet Execution Resultsread-only

    List execution result definitions (id, name, color, isDefault) for a project.

  • qtm4j_get_execution_teststepsGet Test Case Execution Stepsread-only

    List the per-step execution records for a single test case execution (step result, actual result, defects). Requires the cycle id and the testCaseExecutionId from qtm4j_get_test_cycle_executions.

  • qtm4j_get_labelsGet Labelsread-only

    List labels for a project. Use paginated=true with search/sort for large projects (returns startAt/maxResults/total/data).

  • qtm4j_get_linked_test_cyclesList Linked Test Cyclesread-only

    List all test cycles currently linked to a test plan. Use the plan's internal id (not key).

  • qtm4j_get_parametersGet Parametersread-only

    List data-grid parameters (id, name, description) for a project. Paginated.

  • qtm4j_get_prioritiesGet Prioritiesread-only

    List priorities (id, name, iconUrl, isDefault, isArchive) for a project.

  • qtm4j_get_priority_iconsGet Priority Iconsread-only

    List built-in priority icons (id, iconUrl) usable when creating priorities.

  • qtm4j_get_projectsGet QMetry-Enabled Projectsread-only

    List Jira projects with QMetry enabled. Returns id, key, name, and avatarUrl. Use returned numeric id as projectId for other tools.

  • qtm4j_get_statusesGet Statusesread-only

    List statuses for a module (testcase / testcycle / testplan). Returns id, name, color, isDefault, isArchive.

  • qtm4j_get_step_execution_defectsGet Test Step Execution Defectsread-only

    List Jira defects linked to a single test step execution. POST-based read: requires the cycle id and the testStepExecutionId.

  • qtm4j_get_test_caseGet Test Caseread-only

    Get a test case by its internal ID or key (e.g. PROJ-TC-31950). Returns an array of versions with versionNo, isLatestVersion, aiGenerated flag, and any test steps.

  • qtm4j_get_test_case_commentsGet Test Case Commentsread-only

    List comments on a test case. Pass versionNo to read comments for a specific version (defaults to the latest version when omitted). Returns paginated { data: [{ id, comment, created, updated, isEdited }] }.

  • qtm4j_get_test_case_versionGet Test Case Version Detailsread-only

    Get full details of a specific test case version: summary, description, precondition, priority, status, assignee, labels, components, fixVersions, sprint, custom fields, flakyScore, passRateScore. Pass 'latest' as versionNo to skip a get_test_case lookup.

  • qtm4j_get_test_cycleGet Test Cycleread-only

    Get a test cycle by its key (e.g. PROJ-TR-747) or internal id. The internal 'id' returned here is required by qtm4j_get_test_cycle_executions and qtm4j_update_test_execution.

  • qtm4j_get_test_cycle_commentsGet Test Cycle Commentsread-only

    List comments on a test cycle. Returns paginated { data: [{ id, comment, created, updated, isEdited }] }.

  • qtm4j_get_test_cycle_executionsList Test Cycle Executionsread-only

    List test case executions linked to a test cycle. Requires the internal cycle id (from qtm4j_get_test_cycle). Returns testCycleTestCaseMapId (for bulk_update), testCaseExecutionId (for update_test_execution), key, status, priority per test case. Supports server-side filtering by `query` (free-text on key/summary) and `components` (component names). Pass groupBy='component' to get a compact { total, counts } tally across the WHOLE cycle (auto-paginates internally) instead of listing rows. Responses are slimmed by default (empty objects/arrays/nulls dropped); set slim=false for the raw payload.

  • qtm4j_get_test_executionGet Test Executionread-only

    Read back a test case execution's result, comment, and assignee from a test cycle — the only path that surfaces the saved execution comment (search/GET-execution endpoints drop it). Requires the cycle's internal id and testCycleTestCaseMapId (both from qtm4j_get_test_cycle_executions). Returns { executions: { data: [...] } }; each record carries one comment, executionResult, assignee, environment, build, and timestamps. The data array is execution history (one entry per re-execution). Pass testCaseExecutionId to filter to a single record. Use this to verify a write made by qtm4j_update_test_ex…

  • qtm4j_get_test_planGet Test Planread-only

    Get a test plan by its key (e.g. PROJ-TP-43) or internal id. Use the internal 'id' for link/unlink/get_linked_test_cycles operations.

  • qtm4j_get_test_plan_commentsGet Test Plan Commentsread-only

    List comments on a test plan. Returns paginated { data: [{ id, comment, created, updated, isEdited }] }.

  • qtm4j_get_test_stepsGet Test Stepsread-only

    List the steps of a test case version. Optional filter narrows by step details / test data / expected result substring.

  • qtm4j_get_user_permissionsGet Current User Permissionsread-only

    Return permission flags for the current user on a project (e.g. TEST_CASE_EDIT, TEST_CYCLE_EXECUTE). Useful for pre-flight checks before mutations.

  • qtm4j_link_automation_ruleLink Automation Rule to Cycle

    Associate an automation rule with a test cycle so it can be triggered for that cycle. automationRuleKey is the rule's string key from your QMetry automation config.

  • qtm4j_link_execution_defectsLink Defects to Test Case Execution

    Link one or more existing Jira defects to a test case execution. defectIDs are the numeric Jira defect IDs (not issue keys).

  • qtm4j_link_step_execution_defectsLink Defects to Test Step Execution

    Link one or more existing Jira defects to a test step execution. defectIDs are the numeric Jira defect IDs.

  • qtm4j_link_test_cases_to_cycleLink Test Cases to Test Cycle

    Link one or more test cases to a test cycle so they appear in its execution list. Pass the cycle's internal id and an array of { id, versionNo } pairs (id is the test case internal UID; versionNo is usually 1).

  • qtm4j_link_test_cases_to_requirementLink Test Cases to Requirement

    Associate test cases with a Jira requirement (story/issue) so traceability reports pick them up. testcases is an array of { id, versionNo }.

  • qtm4j_link_test_cycles_to_planLink Test Cycles to Plan

    Link existing test cycles to a test plan. Use the plan's internal id. testcycleIds are the cycle UID strings (e.g. 'xWmIdW1sgYd' from qtm4j_search_test_cycles), NOT numeric ids or keys.

  • qtm4j_list_execution_attachmentsList Test-Execution Attachmentsread-only

    List all attachments on a test-case execution. GET `/testcycles/{cycleId}/testcase-executions/{testcaseExecutionId}/attachments` → `{ data: [{ name, id, fileSize, ... }] }`. Note: after qtm4j_upload_execution_attachment succeeds, registration of the new entry can lag a few seconds.

  • qtm4j_list_foldersList Foldersread-only

    List folders of a given type as a nested tree with id, name, parentId, and children. STRONGLY RECOMMENDED to pass folderId for large projects to return only that subtree — full project trees can exceed response size limits.

  • qtm4j_move_test_casesMove Test Cases to Folder

    Move test cases into a different folder (same project). Pass either testcaseIds or a filter. IMPORTANT: QMetry test cases support multi-folder membership. `selectedFolderId=-1` *adds* the case to targetFolderId without removing it from any current folder (so the case ends up in BOTH places). To actually relocate, pass the real source folder id as selectedFolderId — that removes the case from that folder. If a case is in multiple folders, you must run one move per source-folder to fully relocate it.

  • qtm4j_run_automation_rulesRun Automation Rule

    Trigger an automation rule to run against a specific test cycle. testCycleId is the internal id string (from qtm4j_get_test_cycle). Returns a background task object with taskId and progressUrl.

  • qtm4j_search_cycle_defectsSearch Test Cycle Defectsread-only

    Search all Jira defects linked across a test cycle's executions. POST-based read with an optional filter object (searchText, status, priority, testCaseKey, environment, etc.) and pagination.

  • qtm4j_search_foldersSearch Folders by Nameread-only

    Find folders in a module (testcase / testcycle / testplan) by name substring. Pass mode='STRICT' for exact match, omit for partial match.

  • qtm4j_search_test_casesSearch Test Casesread-only

    Search test cases in a project with optional filters. Returns total count and paginated data. Use status/priority name strings (e.g. 'To Do', 'High'). projectId must be numeric (e.g. 10000). Set recursive=true with folderId to count across all subfolders (returns total only, no data).

  • qtm4j_search_test_cyclesSearch Test Cyclesread-only

    Search test cycles in a project. Returns total count and paginated list. The 'id' field in results is the internal ID needed for execution tools.

  • qtm4j_search_test_plansSearch Test Plansread-only

    Search test plans in a project. The 'id' field in results is the internal ID needed for linking cycles.

  • qtm4j_unarchive_test_caseUnarchive Test Case

    Restore an archived test case to active/editable state via PUT /testcases/{id}/unarchive.

  • qtm4j_unarchive_test_cycleUnarchive Test Cycle

    Restore an archived test cycle to active state via PUT /testcycles/{id}/unarchive.

  • qtm4j_unarchive_test_planUnarchive Test Plan

    Restore an archived test plan to active state via PUT /testplans/{id}/unarchive.

  • qtm4j_unlink_automation_ruleUnlink Automation Rule from Cycle

    Remove the association between an automation rule and a test cycle.

  • qtm4j_unlink_execution_defectsUnlink Defects from Test Case Executioncan change or delete data

    Remove the link between one or more Jira defects and a test case execution. Does not delete the defects.

  • qtm4j_unlink_step_execution_defectsUnlink Defects from Test Step Executioncan change or delete data

    Remove the link between one or more Jira defects and a test step execution.

  • qtm4j_unlink_test_cases_from_cycleUnlink Test Cases from Test Cyclecan change or delete data

    Remove one or more linked test cases from a test cycle. Pass the cycle's internal id and an array of test cases as { id, versionNo } (get both from qtm4j_get_test_cycle_executions — its 'id' field is the test case id).

  • qtm4j_unlink_test_cases_from_requirementUnlink Test Cases from Requirementcan change or delete data

    Remove the link between a Jira requirement and one or more test case versions.

  • qtm4j_unlink_test_cycles_from_planUnlink Test Cycles from Plan

    Remove the link between one or more test cycles and a test plan. Does not delete the cycles themselves.

  • qtm4j_update_execution_custom_fieldsUpdate Test Case Execution Custom Fields

    Set custom field values on a test case execution. customFields use string IDs (e.g. 'qcf_1337') with value and optional cascadeValue. Requires the cycle id and testCaseExecutionId.

  • qtm4j_update_test_caseUpdate Test Case

    Update fields on a specific version of a test case. Requires the test case id and versionNo (usually 1 for latest). Priority and status take integer IDs.

  • qtm4j_update_test_case_commentUpdate Test Case Comment

    Edit an existing comment on a test case version. Use the comment id from qtm4j_get_test_case_comments.

  • qtm4j_update_test_cycleUpdate Test Cycle

    Update a test cycle's metadata (summary, description, priority, status, dates, custom fields).

  • qtm4j_update_test_cycle_commentUpdate Test Cycle Comment

    Edit an existing comment on a test cycle. Use the comment id from qtm4j_get_test_cycle_comments.

  • qtm4j_update_test_executionUpdate Test Execution

    Update a single test case execution result inside a test cycle. Use testCaseExecutionId from qtm4j_get_test_cycle_executions. executionResultId is an instance-specific integer ID — call qtm4j_get_execution_results to resolve names (Pass/Fail/Blocked/etc.) to IDs. Pass testCycleTestCaseMapId to enable read-after-write verification: the tool re-reads the execution and returns the saved comment/result/assignee so you can confirm the write landed.

  • qtm4j_update_test_planUpdate Test Plan

    Update a test plan's priority or custom fields.

  • qtm4j_update_test_plan_commentUpdate Test Plan Comment

    Edit an existing comment on a test plan. Use the comment id from qtm4j_get_test_plan_comments.

  • qtm4j_update_test_step_executionUpdate Test Step Execution

    Update a single step-level execution result within a test case execution. testStepExecutionId comes from qtm4j_get_test_cycle_executions step data.

  • qtm4j_update_test_stepsUpdate Test Steps

    Update existing test steps on a test case version. Each step must include its step id (from qtm4j_create_test_steps or qtm4j_get_test_case).

  • qtm4j_upload_execution_attachmentUpload Attachment to Test Execution

    Upload a local file as an attachment on an existing test-case execution inside a test cycle. This is a TWO-STEP presigned-S3 POST flow — NOT a direct multipart upload to QMetry. Step 1: GET `/testcycles/{cycleId}/testcase-executions/attachments/url/?fileName=…&projectId=…&testcaseExecutionId=…` returns `{ endpoint_url, params }` where `params` is a full AWS S3 browser-POST policy (`key`, `policy`, `success_action_status:201`, `x-amz-*`, `Content-Type`, …). Step 2: this tool POSTs `multipart/form-data` to `endpoint_url` with every `params` entry as a form field FIRST (order matters), then the `…

Signals

Stars
0
Forks
0
Open issues
0
Last commit
Jun 11, 2026 (5 months ago)
Last release
Apr 29, 2026 (6 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name
io.github.salehrifai42/qtm4j-mcp-server
Version
0.1.1
Auth
API key
Packages
npm qtm4j-mcp-server
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get Qtm4j MCP Server running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying Qtm4j MCP Server?

CallGet help
Cite this page

Qtm4j MCP Server. Agent Mart. https://agentmart.dev/connectors/salehrifai42-qtm4j-mcp-server (last updated 2026-10-24)