This article provides a reference for all tools available in the mabl cloud MCP server. All tools require authentication, which is handled automatically through the OAuth login flow.
| Tool | Description | Input | Sample prompt |
|---|---|---|---|
analyze_failure |
Get an AI-generated analysis of why a test run or plan run failed. Requires a run ID (ending in -jr or -pr), not a test/plan ID. If analysis does not exist yet, triggers generation (may take 10-30 seconds). Requires the generative_ai feature to be enabled on the workspace. | run ID, test or plan, and workspace ID | — |
assign_xray_to_mabl_test |
Assign an Xray test case to a mabl test. | mabl test ID, xray test case, xray project ID, and workspace ID Optional: overwrite |
Assign the Xray test case 123 to the mabl test 456 |
create_mabl_test_cloud |
Create a new browser or API test that runs entirely in the mabl cloud, without needing a local browser. Returns session and instance IDs for polling status with get_cloud_test_gen_status. | workspace ID, application ID, environment ID, url, name, intent, and is api test Optional: steps and api spec |
— |
get_applications |
Get all applications in a workspace with their associated environments and URLs. Returns application IDs, names, and environment details (IDs, names, URLs). Application and environment IDs are required by run_mabl_test_cloud. | workspace ID | — |
get_cloud_test_gen_status |
Check the status of a cloud test generation initiated by create_mabl_test_cloud. Returns the current status, created test ID (if complete), and the latest model message. | session ID Optional: instance ID |
— |
get_credentials |
Get all credentials available in a workspace. Returns credential IDs, names, types, and a cloud_only flag. Cloud-only credentials cannot be used in local test runs. Credential IDs are optional for run_mabl_test_cloud. | workspace ID | — |
get_current_user_info |
Get information about the currently authenticated user, including their userId and default workspace. Call this tool early after authentication to obtain the userId and defaultWorkspaceId, which are required by many other tools. | none | — |
get_environments |
Get all environments in a workspace (e.g., staging, production). Returns environment IDs and names. Environment IDs are required by run_mabl_test_cloud. | workspace ID | — |
get_latest_authored_tests |
Get the most recent tests authored by the current user in a workspace. Returns test details including names, types, and steps. Results are paginated (default 10, max 100). | workspace ID and user ID Optional: limit |
— |
get_latest_plan_runs |
Get recent execution results for a plan by plan ID. Returns plan run IDs, statuses, completion times, and AI failure analysis for failed runs. Use get_plan_run_result to inspect individual test runs within a plan run. | plan ID and workspace ID | — |
get_latest_test_runs |
Get recent execution results for a mabl test by test ID. Returns test run IDs, statuses, completion times, and AI failure analysis for failed runs. Use analyze_failure for deeper analysis of a specific failed run. | test ID and workspace ID | — |
get_mabl_deployment |
Get mabl deployment results by commit hash or deployment ID. Provide exactly one of commitHash or deploymentId, not both. Returns deployment events, plan runs, and individual test runs with pass/fail status. Failed test runs include failure summaries and categorizations. Test runs include environment, application, and credential IDs needed to re-run tests locally. | workspace ID Optional: commit hash and deployment ID |
— |
get_mabl_test_details |
Get full details of a single mabl test by its test ID. Returns test name, description, type, tags, steps, and configuration. Use this after get_mabl_tests to inspect a specific test. | test ID | — |
get_mabl_tests |
Search for mabl tests using a natural language query. Returns test names, descriptions, types, and step summaries. Use this to find tests by what they do (e.g., "login tests", "checkout flow"). For full details on a specific test, use get_mabl_test_details instead. | query and workspace ID Optional: application ID |
— |
get_plan_run_result |
Get detailed results for a specific plan run by plan run ID. Returns the plan run status and all individual test runs with pass/fail outcomes, failure summaries, and credential context. Use this to drill into a specific plan run from get_latest_plan_runs. | plan run ID and workspace ID | — |
get_plans |
Get test plans in a workspace. Returns plan IDs, names, descriptions, types, tags, and enabled status. Plan IDs are required by get_latest_plan_runs. Results are paginated. Use the returned cursor to fetch the next page. | workspace ID Optional: limit and cursor |
— |
get_workspace_test_run_summaries |
Fetch the latest test run results across an entire workspace. Use this tool when the user wants a broad overview of recent test activity, such as "show me the latest results" or "are there any failures in my workspace?". Supports pagination via limit and cursor. By default, mabl-created default tests are excluded. | workspace ID Optional: status, test type, exclude default tests, limit, and cursor |
— |
get_workspaces |
Get all workspaces the current user has access to. Returns workspace IDs and names. A workspaceId is required by most other tools. If the user does not specify a workspace, use the defaultWorkspaceId from get_current_user_info. | user ID | — |
get_xray_test_cases |
Get Xray test cases for a specific Xray project. Returns test cases that are not already assigned to a mabl test. Results are paginated: if nextCursor is present in the response, pass it as the cursor parameter in a follow-up call to retrieve the next page. | workspace ID Optional: xray project ID, limit, cursor, and search |
— |
run_mabl_test_cloud |
Trigger a cloud execution of a mabl test (browser, API, or performance). The test type is determined by the test itself — the same parameters apply to all supported types. Mobile tests are not yet supported. Returns a list of individual test run links. | test ID, workspace ID, environment ID, application ID, and browsers Optional: credentials ID |
— |
Obtaining IDs
In many cases, you can obtain the IDs directly from the AI agent by including it in a prompt. For example: "Get recent plan runs for the plan 'App - a11y tests' and include the plan run IDs, please."
If you can't get a specific ID directly from the mabl MCP, check out our article on obtaining mabl resource IDs from the mabl app, CLI, and API.