Katalon TestOps MCP Server
Overview​
Katalon TestOps integrates with modern AI tools through the Model Context Protocol (MCP).
With the TestOps MCP Server, you can use your AI assistant (for example, Claude, GitHub Copilot, or ChatGPT with MCP support) to work directly with TestOps objects such as Test Cases, Test Suites, Test Runs, Test Folders, Requirements, Defects, Iterations (Sprints/Releases), Repositories, and Projects.
This integration lets you create, update, move, duplicate, delete, and search TestOps assets, as well as query configuration and quality insights, all from within your AI tool—streamlining test management, reporting, and analysis workflows.
Availability Notice:
The TestOps MCP Server integration is available only for the current version of TestOps.
If you are using a legacy version of TestOps, please contact your Customer Success Manager (CSM) for upgrade guidance and compatibility support.
Prerequisites​
Before using the TestOps MCP Server:
- Ensure your AI tool supports MCP server connection.
- For tools that do not support remote MCP servers natively, install the required utilities such as
npx. - Confirm that your AI tools (e.g., Claude Desktop, ChatGPT) is configured to connect with an external MCP server.
Configure the MCP Server​
To connect your AI tool with TestOps, point it to the TestOps MCP endpoint:
- Use
https://<your-custom-domain>.katalon.io/mcpin any AI tool that supports configuring a remote MCP server natively. See Custom Domain for more information. - If your tool does not support remote MCP servers natively (for example, Claude Desktop), add the following JSON configuration to your MCP server setup.
- Claude Desktop
- Copilot
{
"mcpServers": {
"katalon-prod-mcp": {
"command": "npx",
"args": [
"mcp-remote",
"https://<your-custom-domain>.katalon.io/mcp",
"--transport",
"http"
]
}
}
}
{
"servers": {
"katalon-prod-mcp": {
"url": "https://<your-custom-domain>.katalon.io/mcp",
"type": "http"
}
},
"inputs": []
}
After updating the configuration:
- Restart your AI application to detect the new MCP server connection.
- Your browser will display a prompt asking you to log in to your TestOps account.
- In your AI tool, make sure to toggle on the
katalon-prod-mcptool to activate it.
Supported Operations​
⚠️ Note: Supported tools may evolve in future updates.
The TestOps MCP Server currently supports the following tools:
| Scope | Tool | Description |
|---|---|---|
| Analyze | get_defect_insights | Retrieves defect insight for a specific sprint/release iteration or time range. |
get_requirement_insights | Retrieves requirement insight for a specific sprint/release iteration. | |
get_test_case_insights | Retrieves test case insight for a specific sprint/release iteration or date range. | |
get_test_configuration_insights | Retrieves configuration insight for a specific sprint/release iteration or date range. | |
analyze_test_case_stability | Analyzes stability of test cases identifying flaky tests, consistently failing tests, newly introduced failures, and slow-running tests. | |
analyze_test_flakiness | Analyze test executions over a lookback period and minimum number of test runs. | |
| Execute | create_test_case | Create a manual test case with optional test steps. |
update_test_case | Update metadata and content of an existing test case. | |
rerun_execution | Re-run a test execution with optional job targets. | |
build_schedule | Build a schedule payload for schedule_test_run. | |
schedule_test_run | Schedule a TestOps test run. | |
build_collection_suite_entry | Build a test suite entry for Test Suite Collection runs. | |
build_private_local_testing_config | Build a private local testing configuration payload. | |
build_run_configuration | Build a configuration object suitable for schedule_test_run. | |
create_test_cloud_app | Create a TestCloud app from an uploaded app file. | |
prepare_test_cloud_tunnel_start | Gather download URLs, API keys, and commands to guide users through the TestCloud tunnel setup experience. | |
stop_test_cloud_tunnel | Stop an active TestCloud tunnel via DELETE /tc/ees/tunnels/{id}. | |
| Retrieve details | find_execution_profiles | List execution profiles for the given projectId and testProjectId (repository ID). |
find_iterations | Find the iterations (sprints or releases) of a TestOps project. | |
find_requirements | List requirements from the integration with issue tracking system (JIRA or Azure ADO) of the project. | |
find_test_cases | Find test cases within repository of project. Supports both iteration-based and common filtering. | |
find_test_cases_by_external_issue_id | Find test cases linked to a specific external requirement/issue ID. | |
find_test_folders | Find test folders within repository of project. | |
find_test_results | Public wrapper used for MCP tool registration that delegates to _find_test_results. | |
find_test_suites | Find test suites within repository of project. | |
get_upload_test_cloud_app_url | Get app upload URL to TestCloud. | |
get_user_context | Retrieve the currently authenticated user's profile information. | |
read_execution | Get detailed information about a specific test execution. | |
read_execution_test_results | Retrieve job-grouped test results for a TestOps execution. | |
read_requirement | Retrieve a specific requirement by its ID. | |
read_schedule_detail | Read the current schedule definition (Schedule/Resource) for a given id. | |
read_test_case | Get the details of a specific test case by its ID. | |
read_test_result | Get the details of a specific execution test result. | |
read_test_suite | Get details of a specific test suite by its ID, including list of test cases within test suite. | |
| List | list_execution_outputs | List execution outputs or discover recent executions. |
list_executions | List test executions with optional filtering. | |
list_projects | List TestOps projects the user has access to. | |
list_repositories | List repositories under a TestOps project. | |
list_test_cloud_agents | List available TestCloud agents scoped to the current account and project. | |
list_test_cloud_apps | List uploaded TestCloud apps with optional RSQL filters and pagination. | |
list_test_cloud_environments | Fetch environments from TestCloud API with optional RSQL filter and pagination. | |
list_test_cloud_tunnels | List active TestCloud tunnels. | |
| Manage | delete_test_case | Delete a test case. |
delete_test_cloud_app | Delete one or multiple apps from TestCloud. | |
duplicate_test_case | Duplicate a test case. | |
manage_test_cloud_dynamic_app | Manage TestCloud dynamic apps. Supports creating and updating dynamic apps. | |
manage_test_folder | Manage test folders. Supports creating, deleting, duplicating, moving, and renaming test folders. | |
manage_test_suite | Manage test suites and their relationships with test cases. | |
move_test_case | Move a test case to a new folder while keeping its existing name. | |
link_requirements_to_test_case | Link requirements to a specific test case. | |
unlink_requirements_from_test_case | Unlink requirements from a specific test case. | |
update_schedule_configuration | Update an existing schedule's configuration or timing. |
Example Use Cases​
Once your MCP server connection is active, you can use your LLM to interact directly with TestOps.
Example operations include:
- Creating and updating Test Cases and Test Suites, including metadata and descriptions.
- Duplicating or moving assets across folders for better organization.
- Deleting outdated items to maintain project cleanliness.
- Retrieving project information, such as Sprints and Releases, using project IDs.
This helps teams automate test management workflows and bridge LLM intelligence with TestOps operations, streamlining test planning and execution.
Watch how Claude Desktop connects to the TestOps MCP Server to analyze project data.