Integration

Tricentis qTest Manager integration

Tricentis qTest Manager is a test management platform. Browse projects and members; manage Modules (the test-design tree), Requirements, Test Cases and their steps and versions, Releases and Builds, Test Cycles, Test Suites and Test Runs; submit manual or automated execution results (Test Logs), single or in batch; submit and update internal Defects; comment on Requirements, Test Cases, Test Runs and Defects; link objects to each other; read the traceability matrix, field definitions and attachments; and query any object type with qTest's Data Query syntax. Site and project administration, custom-field and user administration, webhooks, integration settings, attachment upload and the login routes are not exposed. Authentication is the bearer token shown in qTest Manager under Download qTest Resources, API & SDK, sent in the Authorization header; it does not expire until revoked. The connection asks for the site host, such as yourcompany.qtestnet.com.

Connect Tricentis qTest Manager How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Tricentis qTest Manager.Built from the 81 Tricentis qTest Manager tools below, on the connection you add once.

What you can do with Tricentis qTest Manager

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Comment, 8 operations

add_defect_commentAdd defect commentPOSTAdds a comment to a Defect, given by ID or PID.
add_requirement_commentAdd requirement commentPOSTAdds a comment to a Requirement, given by ID or PID.
add_test_case_commentAdd test case commentPOSTAdds a comment to a Test Case, given by ID or PID.
add_test_run_commentAdd test run commentPOSTAdds a comment to a Test Run, given by ID or PID.
list_defect_commentsList defect commentsGETLists the comments of a Defect, given by ID or PID.
list_requirement_commentsList requirement commentsGETLists the comments of a Requirement, given by ID or PID.
list_test_case_commentsList test case commentsGETLists the comments of a Test Case, given by ID or PID.
list_test_run_commentsList test run commentsGETLists the comments of a Test Run, given by ID or PID.

Test case, 6 operations

approve_test_caseApprove test casePUTApproves a Test Case and returns it.
create_test_caseCreate test casePOSTCreates a Test Case with its field values, description, precondition and optional steps, in the Module given in parent_id (else in the Created via API Module).
delete_test_caseDelete test caseDELETEDeletes a Test Case from the project.
get_test_caseGet test caseGETReturns one Test Case, its latest version or the one in versionId; expand=teststep includes its steps.
list_test_casesList test casesGETLists the Test Cases of a project, or those directly under one Module (parentId), 20 per page by default; expandSteps=true includes their steps.
update_test_caseUpdate test casePUTUpdates a Test Case's name, description, precondition, field values or Module.

Test log, 6 operations

get_last_test_logGet last test logGETReturns the latest Test Log (execution result) of a Test Run.
get_test_logGet test logGETReturns one Test Log of a Test Run.
list_test_logsList test logsGETLists the Test Logs (execution results) of a Test Run.
submit_automation_test_logSubmit automation test logPOSTSubmits an automated execution result to a Test Run, or with testRunId 0 to a new Test Run: status, times, name and the automation_content that identifies the test.
submit_automation_test_logs_batchSubmit automation test logs batchPOSTSubmits many automated results at once into a Test Cycle, creating the Test Cases and Test Runs as needed. It answers with a job: follow it with get_batch_test_log_job.
submit_test_logSubmit test logPOSTSubmits a manual execution result (Test Log) for a Test Run: status, start and end time, note and optional step results.

Test run, 6 operations

create_test_runCreate test runPOSTCreates a Test Run of a Test Case (test_case) under root or the Release, Test Cycle or Test Suite given in parentId and parentType.
delete_test_runDelete test runDELETEDeletes a Test Run from the project.
get_test_runGet test runGETReturns one Test Run with its Test Case and field values.
list_requirement_test_runsList requirement test runsGETLists the Test Runs associated with a Requirement.
list_test_runsList test runsGETLists the Test Runs under root or a Release, Test Cycle or Test Suite (parentId and parentType), 100 per page by default; expand=descendants includes nested runs.
update_test_runUpdate test runPUTUpdates a Test Run, or moves it to another container with parentId and parentType.

Build, 5 operations

create_buildCreate buildPOSTCreates a Build under a parent Release.
delete_buildDelete buildDELETEDeletes a Build from the project.
get_buildGet buildGETReturns one Build with its parent Release and field values.
list_buildsList buildsGETLists the Builds of a Release (releaseId).
update_buildUpdate buildPUTUpdates a Build's name, parent Release or field values.

Defect, 5 operations

get_defectGet defectGETReturns one internal Defect with its field values.
list_recently_updated_defectsList recently updated defectsGETLists the Defects updated since startTime, 100 per page by default.
list_requirement_defectsList requirement defectsGETLists the Defects associated with a Requirement.
submit_defectSubmit defectPOSTSubmits an internal Defect with its field values (properties; field ids from list_fields with objectType defects).
update_defectUpdate defectPUTUpdates the field values of an internal Defect.

Module, 5 operations

create_moduleCreate modulePOSTCreates a Module under root, or under the Module given in parentId.
delete_moduleDelete moduleDELETEDeletes a Module. Without force=true it is deleted only when it holds no sub-Modules or Test Cases.
get_moduleGet moduleGETReturns one Module; expand=descendants includes its sub-Modules.
list_modulesList modulesGETLists the Modules (test-design folders) under root or under a parent Module; search filters by name and expand=descendants returns the whole subtree.
update_moduleUpdate modulePUTRenames or re-describes a Module, or moves it under another Module with parentId (a move ignores the name and description).

Release, 5 operations

create_releaseCreate releasePOSTCreates a Release with its name, dates, description and field values.
delete_releaseDelete releaseDELETEDeletes a Release from the project.
get_releaseGet releaseGETReturns one Release with its dates, description and field values.
list_releasesList releasesGETLists the project's Releases; closed Releases are included only with includeClosed=true.
update_releaseUpdate releasePUTUpdates a Release's name, dates, description or field values.

Requirement, 5 operations

create_requirementCreate requirementPOSTCreates a Requirement under root or under the Module given in parentId, with its field values (properties).
delete_requirementDelete requirementDELETEDeletes a Requirement from the project.
get_requirementGet requirementGETReturns one Requirement with its field values.
list_requirementsList requirementsGETLists the Requirements of a project, or only those directly under one Module (parentId), 20 per page by default.
update_requirementUpdate requirementPUTUpdates a Requirement's name and field values, or moves it under another Module with parentId.

Test cycle, 5 operations

create_test_cycleCreate test cyclePOSTCreates a Test Cycle under root, a Release or another Test Cycle (parentId and parentType).
delete_test_cycleDelete test cycleDELETEDeletes a Test Cycle. Without force=true it is deleted only when it has no children.
get_test_cycleGet test cycleGETReturns one Test Cycle; expand=descendants includes its sub-cycles and Test Suites.
list_test_cyclesList test cyclesGETLists the Test Cycles directly under root, a Release or a Test Cycle (parentId and parentType); expand=descendants adds sub-cycles and suites.
update_test_cycleUpdate test cyclePUTUpdates a Test Cycle, or moves it to another container with parentId and parentType.

Test suite, 5 operations

create_test_suiteCreate test suitePOSTCreates a Test Suite under root, a Release or a Test Cycle (parentId and parentType).
delete_test_suiteDelete test suiteDELETEDeletes a Test Suite from the project.
get_test_suiteGet test suiteGETReturns one Test Suite with its field values.
list_test_suitesList test suitesGETLists the Test Suites under a Release, a Test Cycle or root (parentId and parentType).
update_test_suiteUpdate test suitePUTUpdates a Test Suite, or moves it when parentId and parentType are given; a move ignores the other fields.

Test step, 4 operations

add_test_stepAdd test stepPOSTAdds a Test Step (description and expected result) to a Test Case's latest version.
delete_test_stepDelete test stepDELETEDeletes a Test Step from a Test Case; with updateVersion=true (the default) the Test Case version is updated.
list_test_stepsList test stepsGETLists the Test Steps of a Test Case's latest version.
update_test_stepUpdate test stepPUTUpdates a Test Step of a Test Case's latest version.

Link, 3 operations

link_objectsLink objectsPOSTLinks objects of one type (type, items) to a source object, for example Test Cases to a Requirement.
list_linked_objectsList linked objectsGETReturns the objects linked to the given objects of one type (ids; for Defects, external ids in pids).
unlink_objectsUnlink objectsDELETERemoves links between a source object and objects of one type (type, items).

User, 3 operations

get_current_userGet current userGETReturns the account the token belongs to: user id, username, first and last name, site and time zone.
list_project_usersList project usersGETLists the members of a project. Inactive users are left out unless inactive is true.
search_usersSearch usersGETFinds users by login name (username), 100 per page by default.

Project, 2 operations

get_projectGet projectGETReturns one project: name, description, status, start and end dates and administrators.
list_projectsList projectsGETLists the qTest Manager projects the token's account can access.

Attachment, 1 operation

list_attachmentsList attachmentsGETLists the attachments of a Release, Build, Requirement, Test Case, Test Log, Test Step, Test Step Log or Defect.

Execution status, 1 operation

list_execution_statusesList execution statusesGETLists the project's Test Run execution statuses (id, name, color, default), the values a Test Log's status takes.

Field, 1 operation

list_fieldsList fieldsGETLists the fields of an object type with their ids, types and allowed values: the field ids that properties takes.

History, 1 operation

query_historiesQuery historiesPOSTReturns the change history of Requirements, Test Cases, Test Runs or Defects matched by object_query, filtered by date or author.

Object, 1 operation

search_objectsSearch objectsPOSTQueries Releases, Requirements, Test Cases, Test Runs, Test Suites, Test Cycles, Test Logs, Builds or Defects with qTest's Data Query syntax, 100 per page by default.

Test case version, 1 operation

list_test_case_versionsList test case versionsGETLists the versions of a Test Case: every approved major version, plus the last unapproved minor version if there is one.

Test log job, 1 operation

get_batch_test_log_jobGet batch test log jobGETReturns the state of a batch test-result submission job started by submit_automation_test_logs_batch.

Traceability report, 1 operation

get_traceability_matrix_reportGet traceability matrix reportGETReturns the traceability matrix: Requirements with the Test Cases that cover them, 20 Requirements per page by default.

Use Tricentis qTest Manager from Claude Code, Cursor or Codex

Connect Tricentis qTest Manager in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Tricentis qTest Manager operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Tricentis qTest Manager

Create your workspace
Sign up free. Nothing to install.
Connect Tricentis qTest Manager once
Add your Tricentis qTest Manager connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.