MCP TOOLS

Every tool the agent can call, grouped by what it works on.

There is no second interface for test work. Everything a QA Engineer does with cases, suites, runs and defects, an agent can do through these calls, under the same rules and approvals. The agent works on test artifacts, not on the platform: managing the team and the workspace, and destructive actions on projects, stay in the web app.
  • readreads only, no changes
  • writecreates or updates data
  • destructivepermanently deletes data

Project Rules

Small project facts injected into AI agents' context before other work.

  • get_project_rulesFetch a project's rules — agents call this firstread
  • create_project_ruleSave a short project fact as a persistent rulewrite
  • update_project_ruleEdit an existing rule's textwrite
  • delete_project_rulePermanently delete a ruledestructive

Lessons Learned

Real incidents and the class of failure to watch for, injected into AI agents' context alongside rules.

  • get_project_lessonsFetch a project's lessons learned — agents call this alongside get_project_rulesread
  • create_project_lessonRecord an incident, its takeaway and impact as a persistent lessonwrite
  • update_project_lessonEdit a lesson's incident, takeaway or impactwrite
  • delete_project_lessonPermanently delete a lessondestructive

Test Cases

Create, find, and maintain individual test cases.

  • create_test_caseCreate a test case, optionally with steps and tagswrite
  • bulk_create_test_casesCreate many test cases in one callwrite
  • list_test_casesList cases with filters, field selection, and paginationread
  • get_test_caseGet one case with full detailsread
  • search_test_casesFind cases by title textread
  • update_test_caseUpdate a case; only the fields you pass change, and optionally replace its steps and tagswrite
  • edit_test_case_stepsEdit individual steps of a case — update, add, delete, or move — without resending them allwrite
  • bulk_update_test_casesApply the same update to many caseswrite
  • delete_test_caseDelete a case and its stepsdestructive
  • duplicate_test_casesCopy one or more cases into the same suitewrite

Test Suites

Organize cases into suites and keep the tree in order.

  • create_test_suiteCreate a suite (folder) to organize caseswrite
  • update_test_suiteRename, reparent, or re-describe a suitewrite
  • delete_test_suiteDelete an empty suitedestructive
  • delete_test_suite_deepDelete a suite and everything inside itdestructive
  • duplicate_test_suite_deepCopy a suite and its full subtreewrite
  • list_test_suitesList a project's suites as a treeread
  • get_suite_summaryGet a suite's case count and tag breakdownread
  • move_test_casesMove cases to another suite (or to the project root)write
  • set_test_case_orderReorder the cases within a suitewrite
  • set_test_suite_orderReorder sibling suites under one parentwrite
  • move_test_suiteRe-parent a suite under a new parentwrite

Tags

Label cases across suites and keep the vocabulary clean.

  • list_tagsList a project's tagsread
  • create_tagCreate a tag ahead of using itwrite
  • rename_tagRename a tag everywhere it's usedwrite
  • merge_tagsMerge several tags into onewrite
  • delete_tagDelete a tag and remove it from all casesdestructive

Test Runs

Plan runs, record results, and track execution.

  • create_test_runStart a run from explicit cases and/or a run templatewrite
  • update_test_runEdit a run, change its status (abort/reopen), add or remove caseswrite
  • record_test_resultRecord one case's result with an execution snapshotwrite
  • bulk_record_resultsRecord results for many cases at once (with snapshots)write
  • complete_test_runMark a run as completedwrite
  • duplicate_test_runCopy a run's case set into a fresh active runwrite
  • delete_test_runPermanently delete a run with its resultsdestructive
  • get_test_runGet a run with results, stats, snapshots, or pending casesread
  • list_test_runsList a project's runs, optionally by statusread
  • get_run_statisticsGet pass/fail/skip/pending counts for a runread

Run Templates

Named, reusable case selections that seed new runs with cases' current state.

  • list_run_templatesList a project's run templates with case countsread
  • get_run_templateGet a template's details and its current (live) case listread
  • create_run_templateCreate a reusable case selection for seeding runswrite
  • update_run_templateEdit a template's title/description and add or remove caseswrite
  • delete_run_templateDelete a template and its case links (runs are unaffected)destructive

Projects

Projects you can access and their field options.

  • list_projectsList projects you can access (active by default)read
  • create_projectCreate a project (you become its admin)write
  • update_projectUpdate a project's title or descriptionwrite
  • archive_projectHide a project from the active listwrite
  • unarchive_projectRestore an archived project to the active listwrite
  • get_field_optionsList the valid values for a fieldread

Defects

Log and manage defects found during testing.

  • create_defectLog a defect with validated project context and an optional HTTP(S) tracker linkwrite
  • get_defectGet complete defect context and activity historyread
  • list_defectsSearch and filter defects with exact active and archived countsread
  • update_defectUpdate or clear a defect's details through the validated write contractwrite
  • archive_defectReversibly hide a defect from active lists without losing its contextwrite
  • unarchive_defectRestore an archived defect to active listswrite
  • archive_defectsAtomically archive up to 100 defectswrite
  • unarchive_defectsAtomically restore up to 100 archived defectswrite