Katalon TestOps MCP

Server Details

Katalon TestOps Model Context Protocol (MCP) server

Status: Healthy
Last Tested: 2026-01-30 14:30
Transport: Streamable HTTP
URL

Available Tools

30 tools

analyze_test_case_stabilityTry in Inspector

Analyzes stability of test cases identifying flaky tests, consistently failing tests, newly introduced failures, and slow-running tests. Returns test case stability metrics.

ParametersJSON Schema

Name	Required	Description
`to_date`	No	End date for the analysis period in ISO format: YYYY-MM-DD or YYYY-MM-DDTHH:mm:ss
`from_date`	No	Start date for the analysis period in ISO format: YYYY-MM-DD or YYYY-MM-DDTHH:mm:ss
`project_id`	Yes	ID of the TestOps project to search within.
`filter_type`	No	Type of filter to apply - 'EXECUTION' or 'ITERATION'.
`limit_tests`	No	Maximum number of test cases to return for each test category.
`execution_id`	No	ID of the execution. Required if filter_type is 'EXECUTION'.
`return_tests`	No	List of test categories to return. Allowed values: ALL, FLAKY, ALWAYS_FAIL, NEW_FAILURE, SLOW. Use None to omit returning details.
`iteration_name`	No	Name of iteration. Required if filter_type is 'ITERATION'.
`iteration_type`	No	Type of iteration - either "SPRINT" or "RELEASE". Required if filter_type is "ITERATION".

analyze_test_flakinessTry in Inspector

Analyze test executions over a lookback period and minimum number of test runs. Returns test flakiness metrics of test cases.

ParametersJSON Schema

Name	Required	Description
`min_runs`	No	Minimum number of runs required for analysis (default: 10). Minimum is 5 runs for qualified analysis.
`days_back`	No	Number of days to look back for test executions (default: 28). Minimum is 3 days for meaningful analysis.
`project_id`	Yes	ID of the TestOps project to search within.
`min_pfs_score`	No	Minimum PFS score threshold for filtering results (default: 0.2)
`test_case_ids`	No	List of test case IDs to analyze.
`pfs_flaky_threshold`	No	Threshold above which tests are considered flaky (default: 0.8)
`pfs_stable_threshold`	No	Threshold below which tests are considered stable (default: 0.2)

create_test_caseTry in Inspector

Create a manual test case with optional test steps.

ParametersJSON Schema

Name	Required	Description
`test_case`	Yes	Object containing all metadata and content required to define the new test case.When specifying test steps in 'content.steps', each step only needs 'name' and 'context' - unique step IDs are automatically generated server-side.
`project_id`	Yes	ID of the TestOps project to search within.
`repository_id`	Yes	ID of the repository where the test case/test suite/test folder is located. Must explicitly ask the user to choose the repository if there are multiple repositories available.

delete_test_caseTry in Inspector

Delete a test case.

ParametersJSON Schema

Name	Required	Description
`project_id`	Yes	ID of the TestOps project to search within.
`test_case_id`	Yes	ID of the test case to delete.
`repository_id`	Yes	ID of the repository where the test case/test suite/test folder is located. Must explicitly ask the user to choose the repository if there are multiple repositories available.

duplicate_test_caseTry in Inspector

Duplicate a test case.

ParametersJSON Schema

Name	Required	Description
`project_id`	Yes	ID of the TestOps project to search within.
`test_case_id`	Yes	ID of the test case to duplicate.
`repository_id`	Yes	ID of the repository where the test case/test suite/test folder is located. Must explicitly ask the user to choose the repository if there are multiple repositories available.

find_execution_profilesTry in Inspector

List execution profiles for the given projectId and testProjectId (repository ID). Both projectId and testProjectId are required parameters.

Returns a paginated list of execution profiles (id, name, isDefault) without making a selection. Supports page (default 0) and size (default 50). Never assume or infer a profile; only return available profiles and counts.

ParametersJSON Schema

Name	Required	Description
`page_size`	No	Number of items per page.
`project_id`	Yes	ID of the TestOps project to search within.
`page_number`	No	Page number for pagination.
`repository_id`	Yes	ID of the repository where the test case/test suite/test folder is located. Must explicitly ask the user to choose the repository if there are multiple repositories available.

find_iterationsTry in Inspector

Find the iterations (sprints or releases) of a TestOps project.

The filter parameter determines what type of iterations to fetch:

SprintFilter with type='Sprint': Fetch only sprints
ReleaseFilter with type='Release': Fetch only releases
IterationFilter with type='All': Fetch both sprints and releases

Returns a structured response with separate 'sprints' and 'releases' arrays. Each item has a 'type' field indicating whether it's a 'Sprint' or 'Release'.

ParametersJSON Schema

Name	Required	Description
`filter`	No	Optional query to filter iterations. Use SprintFilter for sprints, ReleaseFilter for releases, or IterationFilter for both. The 'type' field in the query determines what to fetch: 'Sprint', 'Release', or 'All'.
`page_size`	No	Number of items per page.
`project_id`	Yes	ID of the TestOps project to search within.
`page_number`	No	Page number for pagination.

find_requirementsTry in Inspector

List requirements from the integration with issue tracking system (JIRA or Azure ADO) of the project.

ParametersJSON Schema

Name	Required	Description
`query`	No	Query to find requirements.
`page_size`	No	Number of items per page.
`project_id`	Yes	ID of the TestOps project to search within.
`page_number`	No	Page number for pagination.

find_test_casesTry in Inspector

Find test cases within repository of project.

ParametersJSON Schema

Name	Required	Description
`query`	No	Query to find test cases. Query by path should start with 'Test Cases' or 'Test Cases/'.
`page_size`	No	Number of items per page.
`project_id`	Yes	ID of the TestOps project to search within.
`page_number`	No	Page number for pagination.
`repository_id`	Yes	ID of the repository where the test case/test suite/test folder is located. Must explicitly ask the user to choose the repository if there are multiple repositories available.

find_test_cases_by_external_issue_idTry in Inspector

Find test cases linked to a specific external requirement/issue ID.

ParametersJSON Schema

Name	Required	Description	Default
`project_id`	Yes	ID of the TestOps project to search within.
`external_issue_id`	Yes	External issue ID to search for linked test cases.

find_test_foldersTry in Inspector

Find test folders within repository of project.

ParametersJSON Schema

Name	Required	Description
`query`	No	Query to find test folders.
`page_size`	No	Number of items per page.
`project_id`	Yes	ID of the TestOps project to search within.
`page_number`	No	Page number for pagination.
`repository_id`	Yes	ID of the repository where the test case/test suite/test folder is located. Must explicitly ask the user to choose the repository if there are multiple repositories available.

find_test_resultsTry in Inspector

Public wrapper used for MCP tool registration that delegates to _find_test_results.

ParametersJSON Schema

Name	Required	Description
`query`	No	RSQL query to find test results.
`page_size`	No	Number of items per page.
`project_id`	Yes	ID of the TestOps project to search within.
`page_number`	No	Page number for pagination.

find_test_suitesTry in Inspector

Find test suites within repository of project.

ParametersJSON Schema

Name	Required	Description
`query`	No	Query to find test suites. Query by path should start with 'Test Suites' or 'Test Suites/'.
`page_size`	No	Number of items per page.
`project_id`	Yes	ID of the TestOps project to search within.
`page_number`	No	Page number for pagination.
`repository_id`	Yes	ID of the repository where the test case/test suite/test folder is located. Must explicitly ask the user to choose the repository if there are multiple repositories available.

get_defect_insightsTry in Inspector

Retrieves defect insight for a specific sprint/release iteration or time range. Returns defect distributions by priority and severity.

ParametersJSON Schema

Name	Required	Description	Default
`filter`	No	Aggregation scope can be iteration-based, time-ranged based, combined between time-range and iteration, or default (last 28 days). MUST include "filter_type" field. Examples: {"filter_type": "iteration", "iteration_type": "Sprint", "iteration_name": "Sprint 1"} OR {"filter_type": "date_range", "from_date": "2024-01-01", "to_date": "2024-01-31"} OR {"filter_type": "default"}.'
`project_id`	Yes	ID of the TestOps project to search within.
`resolution_state`	No	Filter by defect resolution state - "RESOLVED" or "UNRESOLVED".	UNRESOLVED

get_requirement_insightsTry in Inspector

Retrieves requirement insight for a specific sprint/release iteration. Returns requirement coverage statistics and detailed requirement information.

ParametersJSON Schema

Name	Required	Description
`project_id`	Yes	ID of the TestOps project to search within.
`iteration_name`	No	Name of the sprint or release. Must check if the sprint or release exists in the project.
`iteration_type`	No	Type of iteration - either "Sprint" or "Release".

get_test_case_insightsTry in Inspector

Retrieves test case insight for a specific sprint/release iteration or date range. Returns execution statistics, automation status, and detailed test case information.

ParametersJSON Schema

Name	Required	Description	Default
`filter`	No	Aggregation scope can be iteration-based, time-ranged based, combined between time-range and iteration, or default (last 28 days). MUST include "filter_type" field. Examples: {"filter_type": "iteration", "iteration_type": "Sprint", "iteration_name": "Sprint 1"} OR {"filter_type": "date_range", "from_date": "2024-01-01", "to_date": "2024-01-31"} OR {"filter_type": "default"}.'
`project_id`	Yes	ID of the TestOps project to search within.

get_test_configuration_insightsTry in Inspector

Retrieves configuration insight for a specific sprint/release iteration or date range. Returns platform statistics, overall health indicator, and test execution details. Status is determined based on coverage threshold and pass threshold values.

ParametersJSON Schema

Name	Required	Description
`filter`	No	Aggregation scope can be iteration-based, time-ranged based, combined between time-range and iteration, or default (last 28 days). MUST include "filter_type" field. Examples: {"filter_type": "iteration", "iteration_type": "Sprint", "iteration_name": "Sprint 1"} OR {"filter_type": "date_range", "from_date": "2024-01-01", "to_date": "2024-01-31"} OR {"filter_type": "default"}.'
`project_id`	Yes	ID of the TestOps project to search within.
`pass_threshold`	No	Threshold for pass rate. Platforms with pass rate below this will be flagged.
`configuration_type`	No	Type of configuration to analyze - "OS" or "BROWSER".
`coverage_threshold`	No	Threshold for coverage rate. Platforms with coverage below this will be flagged.
`max_tests_per_platform`	No	Maximum number of test details to return per platform (to limit response size). Set to 0 for all tests.

get_user_contextTry in Inspector

Retrieve the currently authenticated user's profile information.

ParametersJSON Schema

Name	Required	Description	Default
`project_id`	Yes	ID of the TestOps project to search within.

link_requirements_to_test_caseTry in Inspector

Link requirements to a specific test case.

ParametersJSON Schema

Name	Required	Description
`project_id`	Yes	ID of the TestOps project to search within.
`test_case_id`	Yes	ID of the test case to link requirements to.
`requirement_ids`	Yes	List of requirement IDs to link to the test case.

list_projectsTry in Inspector

List TestOps projects the user has access to.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

list_repositoriesTry in Inspector

List repositories under a TestOps project.

ParametersJSON Schema

Name	Required	Description	Default
`project_id`	Yes	ID of the TestOps project to search within.

manage_test_folderTry in Inspector

Manage test folders. Supports creating, deleting, duplicating, moving, and renaming test folders.

ParametersJSON Schema

Name	Required	Description
`payload`	Yes	Object-based payload containing the test folder operation to perform. Each operation is discriminated by its 'action' field. Example: { "action": "CREATE", "path": "Test Cases/New Test Folder", "testFolderType": "TEST_CASE" } { "action": "RENAME", "id": 456, "name": "Renamed Test Folder" } { "action": "MOVE", "id": 456, "path": "Test Cases/Moved Test Folder" } { "action": "DUPLICATE", "id": 456 } { "action": "DELETE", "id": 456 }
`project_id`	Yes	ID of the TestOps project to search within.
`repository_id`	Yes	ID of the repository where the test case/test suite/test folder is located. Must explicitly ask the user to choose the repository if there are multiple repositories available.

manage_test_suiteTry in Inspector

Manage test suites and their relationships with test cases. Supports creating,deleting, duplicating, moving, renaming, and adding test cases to test suites.

ParametersJSON Schema

Name	Required	Description
`payload`	Yes	Object-based payload containing the test suite management operations. Each operation is discriminated by its 'action' field. Example: { "action": "ADD_TEST_CASES", "id": 123, "testCaseIds": [456, 789] } { "action": "RENAME", "id": 123, "name": "New Test Suite Name" } { "action": "MOVE", "id": 123, "path": "Test Suites/Regression" } { "action": "DUPLICATE", "id": 123 } { "action": "DELETE", "id": 123 }
`project_id`	Yes	ID of the TestOps project to search within.
`repository_id`	Yes	ID of the repository where the test case/test suite/test folder is located. Must explicitly ask the user to choose the repository if there are multiple repositories available.

move_test_caseTry in Inspector

Move a test case to a new folder while keeping its existing name.

ParametersJSON Schema

Name	Required	Description
`project_id`	Yes	ID of the TestOps project to search within.
`test_case_id`	Yes	ID of the test case to move.
`repository_id`	Yes	ID of the repository where the test case/test suite/test folder is located. Must explicitly ask the user to choose the repository if there are multiple repositories available.
`new_folder_path`	Yes	Folder path (excluding the test case name). Must always start with 'Test Cases' or 'Test Cases/'. Example: 'Test Cases/Report_Analytics/Manual Test Cases'

read_requirementTry in Inspector

Retrieve a specific requirement by its ID.

ParametersJSON Schema

Name	Required	Description	Default
`project_id`	Yes	ID of the TestOps project to search within.
`requirement_id`	Yes	ID of the requirement to retrieve.

read_test_caseTry in Inspector

Get the details of a specific test case by its ID.

ParametersJSON Schema

Name	Required	Description	Default
`project_id`	Yes	ID of the TestOps project to search within.
`test_case_id`	Yes	ID of the test case to retrieve.

read_test_resultTry in Inspector

Get the details of a specific execution test result.

ParametersJSON Schema

Name	Required	Description
`project_id`	Yes	ID of the TestOps project to search within.
`include_details`	No	Whether to include details (profile, configuration, logs, etc.) in the test result.
`execution_test_result_id`	Yes	ID of the test result to retrieve.

read_test_suiteTry in Inspector

Get details of a specific test suite by its ID, including list of test cases within test suite.

ParametersJSON Schema

Name	Required	Description	Default
`project_id`	Yes	ID of the TestOps project to search within.
`test_suite_id`	Yes	ID of the test suite to retrieve.

unlink_requirements_from_test_caseTry in Inspector

Unlink requirements from a specific test case.

ParametersJSON Schema

Name	Required	Description
`project_id`	Yes	ID of the TestOps project to search within.
`test_case_id`	Yes	ID of the test case to unlink requirements from.
`requirement_ids`	Yes	List of requirement IDs to unlink from the test case.

update_test_caseTry in Inspector

Update metadata and content of an existing test case.

ParametersJSON Schema

Name	Required	Description
`action`	Yes	Action to perform.
`project_id`	Yes	ID of the TestOps project to search within.
`repository_id`	Yes	ID of the repository where the test case/test suite/test folder is located. Must explicitly ask the user to choose the repository if there are multiple repositories available.
`test_case_data`	Yes	Data object specifying the update action to perform and its associated parameters.

FAQ

How do I claim this server?

To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:

{ "$schema": "https://glama.ai/mcp/schemas/connector.json", "maintainers": [ { "email": "your-email@example.com" } ] }

The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.

What are the benefits of claiming a server?

Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server

Try in Browser

Server Details

Available Tools

FAQ

Your Connectors

Resources