mabl local MCP tools
For the full index of agent-friendly pages, see llms.txt.
This article provides a comprehensive overview of the tools and prompts available in the mabl MCP, including their required inputs and sample prompts.
| Tool | Description | Input | Sample prompt |
|---|---|---|---|
| #analyze_failure | Get a GenAI analysis of why a test or plan execution failed. | run ID, and test or plan | “Tell me why the this test/plan failed” |
| #assign_xray_to_mabl_test | Assign an Xray test case to a mabl test. | mabl test ID, xray test case, xray project ID, and overwrite | “Assign the Xray test case 123 to the mabl test 456” |
| #create_mabl_test | Create a new browser or API test according to your provided prompt. Use isApiTest=false to create a browser test that drives a browser, web app, or native UI. Use isApiTest=true when the user explicitly requests an API test, mentions an API endpoint, an OpenAPI/Swagger spec, or a Postman collection — provide the spec via apiSpec. | application ID, environment ID, url, name, intent, issue or ticket, steps, and is api test Optional: credentials ID, without credentials, intent url, and api spec |
“Create a new mabl test based on these details. Use the application MyApplication in environment Development.” |
| #create_mabl_test_cloud | Create a new browser or API test that runs in the mabl cloud, without needing a local browser. Use isApiTest=false to create a browser test; the response includes session and instance IDs that can be polled with #get_cloud_test_gen_status. Use isApiTest=true when the user explicitly requests an API test, mentions an API endpoint, an OpenAPI/Swagger spec, or a Postman collection — provide the spec via apiSpec; the response returns the created test id and name (no polling required). | application ID, environment ID, url, name, intent, and is api test Optional: steps, credentials ID, and api spec |
|
| #create_mabl_test_from_plan | Create a mabl test from a plan artifact created by the #plan_new_test tool. | mode | “Create a mabl test from a plan artifact created by the #plan_new_test tool. This tool can only be called after calling #plan_new_test as it needs the artifact created by the #plan_new_test tool. Set mode to “cloud” to run test generation in the mabl cloud instead of locally.” |
| #export_to_playwright | Export a mabl test to Playwright, you need to provide the testId and optionally the environmentId. | test ID Optional: environment ID |
“Export mabl test “Login in mabl” to Playwright using the environment Development” |
| #get_applications | Get all mabl applications with their associated environments. | None | “Get my mabl applications” |
| #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 mabl credentials and specify if they are cloud only. | None | “Get my mabl credentials” |
| #get_environments | Get all mabl environments. | None | “Get my mabl environments” |
| #get_latest_authored_tests | Get latest tests created by the current user. | Optional: limit | “What mabl tests have I created recently?” |
| #get_latest_plan_runs | Get the latest mabl plan results for a planId. | plan ID | “Get the latest results for the mabl plan “App - Feature: Labels”.” |
| #get_latest_test_runs | Get the recent execution results for a mabl test by testId. | test ID | “Can you fetch the latest results for the test “Mabl login”?” |
| #get_mabl_deployment | Get mabl deployment result for last commit. This tools is usefull to know if the last commit broke the tests or not and what test failed. | commit hash, and deployment ID | “Get mabl deployment result for last commit” |
| #get_mabl_test_details | Get the details of a mabl test based on a testId. | test ID | “Get the details of mabl test 123” |
| #get_mabl_tests | Get an array of mabl tests based on a query. | query Optional: application ID |
“Get mabl datatable tests” |
| #get_plan_run_result | Get a mabl plan run result for a given planRunId. Useful for debugging a single plan run. | plan run ID | “Get mabl plan run result for the last run of the plan “App - Feature: Labels”” |
| #get_plans | Get all mabl plans. | None | “Get my mabl plans” |
| #get_workspaces | Get all of the workspaces that the user has access to, or get the current workspace. | Optional: limit | “What’s my current mabl workspace?” |
| #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. | Optional: xray project ID, limit, cursor, and search | |
| #plan_new_test | Plan a new test. | original intent Optional: issue or ticket, and requested changes |
“Plan a new test based on these details.” |
| #run_mabl_test_cloud | Run a mabl test in the mabl cloud. | environment ID, test ID, application ID, and browsers Optional: credentials ID |
“Run mabl test “Mabl Login” in application MyApplication in environment Development using the “Admin user” credential and the “Chrome” browser” |
| #run_mabl_test_local | Locally run a mabl test. | environment ID, and test ID Optional: credentials ID, and allow local test billing |
“Run mabl test “Mabl Login” in environment Development using the “Admin user” credential” |
| #switch_workspace | Switch to a different workspace by providing a workspace ID. | workspace ID | “Switch to workspace “Personal”” |
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.
Prompts
The mabl MCP also provides a prompt called create_mabl_test_for_current-work, which you can use to create a new test based on your current work context. To use it, enter the following in the AI client chat: /mcp.mcp-mabl.create_mabl_test_for_current-work.