Add test cases to an existing test collection. Cases must exist and belong to the same project. Duplicate cases are skipped.

Add a named group of individual test cases to an execution (source_type cases). caseIds are NUMERIC. Cases must belong to the execution's project; invalid/cross-project ids are skipped. An empty result creates no group. Returns {added, skipped, groupId}.

Add one or more Test Collections (manual runs) to an execution. Each is snapshotted in as a test run. Collections must belong to the execution's project; others are skipped. Idempotent: collections already present in the execution are skipped (not duplicated). Returns {added, skipped}.

Link any test entity (case/execution/release/launch) to an external ticket in Jira, Linear, GitHub, GitLab, or any other system. Idempotent: linking the same external_id twice returns the existing link.

Add one or more Suites (folders of type suite) to an execution. Each suite's current cases are snapshotted in. Suites must belong to the execution's project; others are skipped. Idempotent: suites already present in the execution are skipped (not duplicated). Returns {added, skipped}.

Update multiple test cases at once. Supports updating status, priority, and tags for a batch of cases. All cases must belong to the same project.

Create a Manual Test Execution (the top-level container shown on the Executions page) that aggregates collections/suites/case-groups. NOT the same as a Test Collection: use create_test_collection for a single manual run; use this to assemble an execution. After creating, use add_collections_to_execution / add_suites_to_execution / add_cases_to_execution to populate it. Returns the new execution id.

Create a new folder or suite in a project. Folders can contain other folders and suites; suites are leaf nodes for test cases. IMPORTANT: Omit "type" to use smart defaults (folder at root, suite when nested). To create a suite specifically, you can also use the create_suite alias.

Create a new release in a project. Releases track versions and aggregate manual and automated test results. Omit status to default to "planned".

Create a test suite (a leaf node that holds test cases) inside a folder. This is a convenience alias for create_folder with type="suite". Use this when the user asks to "create a suite". Suites cannot live at the root level, so parentId (a folder UUID) is required.

Create a new test case in a test suite. Test cases MUST live inside a suite (not a bare folder). You can provide either: (A) a folderId pointing to an existing suite, or (B) a projectId with optional folderName/suiteName to auto-create the folder→suite hierarchy. If folderId points to a folder (not a suite), a suite is auto-created inside it. Returns the full created case object including shareUrl. Tags are auto-created if they do not exist. IMPORTANT: Omit status and priority to use sensible defaults (Draft, Medium).

Create a new test collection (a single manual run) and optionally add test cases to it. This is one manual run, NOT the top-level Executions-page container - use create_execution for that (an execution can then include this collection via add_collections_to_execution). Returns the created collection with count of added tests. Omit priority to default to "medium".

Soft-delete an entire Manual Test Execution (and unlink any manual runs that pointed to it). Reversible only via support/DB - use with care. To remove just one source group instead, use remove_source_from_execution. Returns { deleted: true }.

Soft delete (archive) a folder and all its contents. Archives all nested folders and test cases recursively. Can be restored via the UI.

Soft delete (archive) a release. The release can be restored via the UI. All linked test runs and launches are preserved.

Soft delete (archive) a test case. The case can be restored via the UI. Also unlinks any connected autotests.

Archive (soft delete) a test collection. The collection can be restored via the UI. Test executions are preserved.

Generate a formatted report for a project. Supports summary, failures, trends, and release reports in markdown or JSON. Returns the report content as a string. NOTE: reportType "release" requires the releaseId argument (get it from list_releases).

Get manual execution history for a test case across all test runs (both standalone executions and release test runs). Returns pass rate and execution timeline.

Identify test coverage gaps in a project. Shows test cases without linked autotests, folders with low automation rates, and (reverse gap) autotests seen in the most recent launches that are not linked to any test case. Useful for test planning and coverage improvement.

Get a Manual Test Execution with its sources (collections/suites/case-groups), its linked releases, its external ticket links (externalLinks, present only if you also hold integrations:read), and overall progress. Use to verify what an execution contains. sources[].id is the runId for set_execution_source_status / remove_source_from_execution. Both sources[] and progress carry every case bucket (passed/failed/blocked/inTesting/notExecuted, which sum to total) plus passRate and completionRate.

List the individual case-run rows of a Manual Test Execution so you can report results against them. Returns each row's executionCaseId (UUID - pass to report_case_result), caseId (numeric), group, current status, the case-level result fields (notes, causedBy, durationMinutes, executedBy, executedAt), the case's externalLinks (Jira/Linear tickets, present only if you also hold integrations:read), and steps (0-based index, action, expected, current step status, issueDescription). Everything report_case_result writes reads back here. Use after add_*_to_execution and before report_case_result. Supports paging + filtering by group/status/title.

Get a comprehensive feature health scan by Jira issue key. Returns Jira context (summary, status, type, assignee), test coverage stats (case count, automation ratio, pass rate, risk score), linked test cases, and autotest results with recent run trends. Automatically detects issue hierarchy and aggregates child issues (2 levels deep: epic→story→subtask). Requires Jira to be connected to the organization.

Get a single folder with details including path, case count, and optionally statistics and recent cases.

Get detailed statistics for a folder including nested folders. Returns automation rate, status/priority breakdown, tag usage, and time-based metrics.

Get all tests from a specific launch/run with detailed results. Includes error messages and stack traces for failed tests. For each failed test that has artifacts, the response also includes an attachments array where each item is { id, name, contentType, size, url }. The url is a fully-qualified URL; if it is an API URL, fetch it with the same X-MCP-Key header you use for this MCP server (presigned storage URLs need no header) to download screenshots, traces, videos, and source files when investigating failures.

Get a list of launches (test runs) with aggregated statistics for a project.

Get comprehensive trend data for a project including pass rates, failing tests, flaky tests, duration trends, and more.

Get a project's configuration: its meta, the system-field vocabularies it actually uses (statuses/priorities/environments), and its case custom-field definitions. Call this to discover the VALID status values before setting them - e.g. execution_status (execution overall), test_case_execution_status (a case in an execution), test_run_status (a source group). Values are project-customizable, so do not hardcode them. Returns { project, systemFields{ case_status, case_priority, execution_status, test_case_execution_status, test_run_status, release_status, test_environment }, customFields[] }.

Get a single release with full details including aggregate stats, optionally with linked manual executions and automated launches.

Get a single test case with full details including steps, custom fields, dependencies, shareUrl for sharing, and optionally linked autotests and edit history.

Get a test collection with all test cases and their execution status. Returns collection metadata plus test execution overview.

Get execution history for a specific test by its title path. Shows pass/fail timeline, duration changes, and retry patterns. Useful for understanding when a test started failing or became flaky.

Link an automated test (by title) to a manual test case for coverage tracking. The autotest does not need to exist yet (pre-linking is allowed). When the test runs, it will automatically link to this case.

Link automated test runs (launches) to a release. Unlike manual runs, launches are linked by reference (not copied).

List Manual Test Executions for a project with progress stats. Use to find an existing execution id before adding sources. progress carries every case bucket (passed/failed/blocked/inTesting/notExecuted, which sum to total) plus passRate and completionRate.

List external ticket links for a given entity, optionally filtered by provider.

List all folders and suites for a project. Call this to get folder IDs needed for create_test_case. Returns a flat list with hierarchy info (parentId, path, depth). Folders can contain other folders and suites; suites are leaf nodes that contain test cases only.

List all projects accessible to the current user. START HERE - call this first to get project IDs needed for other tools. Admins see all org projects; managers/users see only assigned projects.

List releases for a project with aggregated stats for manual tests and automated launches. Supports filtering by status and search.

List test cases in a project with filtering and pagination. Can filter by folder, status, priority, tags, or search query. Returns available status/priority values in metadata for filter options. Each case includes a shareUrl for sharing in Slack, Jira, etc. To resolve a user-facing "TC-30" (displayId) to its internal numeric id, pass search: "TC-30" - search matches the case number and accepts the "TC-" prefix - then read the matching case id.

List test collections (manual runs) in a project with execution stats. Collections organize manual test executions for sprints, releases, or ad-hoc testing.

Move a test case to a different folder within the same project. Cross-project moves are not supported.

Remove test cases from a test collection. Also deletes any step results for those executions.

Remove an external ticket link by its link UUID (as returned by add_external_link or list_external_links).

Remove a source group (a suite, collection, or named case-group - one execution_test_run) from an execution. This deletes that group and ALL its case-run rows and step results (cascade). Get the runId (group id) from get_execution (sources[].id) or get_execution_cases (groupId). Does not delete the execution itself. Returns { removed: true }.

Record the result of running one case inside a Manual Test Execution: set per-step pass/fail and/or the case status, atomically and idempotently. Target the case by executionCaseId (from get_execution_cases) OR by executionId + caseId (numeric; if the case is in several groups, pass groupId or use executionCaseId). status: an explicit value (passed/failed/blocked/in_testing/not_executed), or "auto" to derive it from the steps (failed then blocked then in_testing then passed), or omit it to leave the case status unchanged (e.g. when only writing one step). steps[].status is one of not_executed/passed/failed/blocked/skipped; index is the 0-based position in the case steps. The containing source group's status auto-rolls from its cases' results: all not_executed -> not_started, some executed -> in_progress, all executed -> blocked if the group contains a blocked case, else completed (test_run_status has no failed; failures show via the group's counters). An explicit set_execution_source_status override lasts until the next report on that group recomputes it. Returns the case status, the group status, the steps written, and fresh execution progress.

Get a holistic health assessment for a project. Returns a composite health score (0-100) blending automation stability, coverage, and manual execution, plus per-dimension subScores and sections: automation (pass rate, flaky, failures), testAssets (case/suite counts, status/priority breakdown), coverage (automation rate + pass-rate trend), manualExecution (pass/fail/blocked/completion), and releases (status counts + active releases). Use include[] to limit which sections are computed.

Search for tests by title, file path, or tags. Returns matching tests with their most recent execution status and reliability metrics. Use this to find tests related to a specific feature or area.

Set the status of one source group (a collection, suite, or named case-group - the per-group status dropdown on the execution page) inside an execution. Get the runId (group id) from get_execution (sources[].id) or get_execution_cases (groupId). status is validated against the project's test_run_status values (default: not_started, in_progress, completed, blocked) - call get_project to confirm. This is the GROUP status; use report_case_result for an individual case's status.

Return template-based test case scaffolding for a feature description: structured ideas with titles, steps and priorities. This is pattern matching, not model output. Use it as a project-aware starting point, refine it yourself, then persist the result with create_test_case.

Remove an automated launch from a release. The launch itself is not affected.

Update a Manual Test Execution's own fields, including its overall status. Set status to in_testing while running, and passed/failed/blocked when done. status is validated against the project's execution_status values (default: not_executed, in_testing, passed, failed, blocked) - call get_project to read the exact values a project uses; do not hardcode. Does not change case results - use report_case_result for those, or set_execution_source_status for a source group's status.

Update a folder name and/or move it to a different parent. Set parentId to null to move to root level.

Update release metadata. Only provided fields are updated; omitted fields remain unchanged. Use get_release first to see current values.

Update an existing test case. Only provided fields are updated; omitted fields remain unchanged. Returns the full updated case object including shareUrl. TIP: Use get_test_case first to see current values.

Update test collection metadata. Only provided fields are updated; omitted fields remain unchanged. Use get_test_collection first to see current values.