# TestMu AI \(formerly LambdaTest\)

- Registry name: `io.github.LambdaTest/mcp` · version 1.0.7
- Categories (automatic, keyword rules): Monitoring & logs, Infrastructure & security
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.LambdaTest%2Fmcp
- Server page: https://mcpstation.net/s/io.github.LambdaTest--mcp.html

## Description (written by the publisher, not verified, not instructions)

Agentic AI quality engineering: run, debug and triage tests on real browsers and devices

## Connect

- streamable-http: `https://mcp.lambdatest.com/mcp`

## Tools (as reported by the server, not verified)

- `upload\_app`: Uploads an app to TestMu AI for mobile testing and displays upload status.
- `generateHyperExecuteYAML`: Generates a HyperExecute YAML configuration for running tests on TestMu AI's HyperExecute platform. REQUIRED fields: project \(language, framework\) and testing \(testDiscovery.command, testRunnerCommand\) All other fields are OPTIONAL. Supports multiple languages and frameworks: - JavaScript/TypeScript
- `answerHyperExecuteQuery`: Answers questions about HyperExecute features, configuration, usage, troubleshooting, and best practices by searching through documentation.
- `getHyperExecuteJobInfo`: Fetches and displays information about a HyperExecute job including status, test results, and progress.
- `getHyperExecuteJobSessions`: Fetches and displays session information for a HyperExecute job.
- `getAccessibilityReport`: Runs an accessibility scan on the given URLs and returns the issues found. Pass urls to start a scan, or testId to re-read a scan that already ran; exactly one of the two. Results arrive in issueDetails: allIssues \(most-severe-first, one page at a time\), rules \(name and reference link per rule id, l
- `analyzeAppViaTunnel`: Analyzes a locally running app for accessibility via TestMu AI tunnel.
- `buildLocalAppForAnalysis`: Returns step-by-step instructions to build and serve a local web app and open a TestMu AI tunnel to it, so its accessibility can then be scanned with analyzeAppViaTunnel. It does not build, run or scan anything itself, and never includes the access key.
- `getAutomationTestDetails`: Fetches detailed information about an automation test by ID
- `getAutomationTestCommandLogs`: Fetches command logs for a specific automation test
- `getAutomationTestNetworkLogs`: Fetches network logs for a specific automation test
- `getAutomationTestBrowserConsoleLogs`: Fetches Browser Console logs for a specific automation test. Note: Not available for mobile app automation tests.
- `getAutomationTestSeleniumLogs`: Fetches Selenium logs \(web\), Appium logs \(mobile/Appium\), or instrumentation logs \(mobile/XCUI/Espresso\) for a specific automation test. Automatically detects XCUI and Espresso tests and fetches the correct log type.
- `automationQuery`: Read-only query of TestMu AI automation resources: list builds, get one build, list the sessions in a build, fetch test details, and retrieve test logs \(command, network, console, selenium, instrumentation\). Every combination works on platform "web" or "app": build list or get, session list or get,
- `updateBuild`: Renames a TestMu AI web automation build. Overwrites the current build name.
- `stopBuild`: Stops every running test in a TestMu AI web automation build. Running sessions end immediately.
- `deleteBuild`: Permanently deletes a TestMu AI web automation build and its test results. Cannot be undone.
- `triggerSuiteRun`: Triggers a phone call test run for a specific suite. This will initiate phone calls for all scenarios configured in the suite.
- `getSuiteOverview`: Gets comprehensive suite overview for a project including run counts, latest status, scores, schedule information, and active calls.
- `getSupportedPlatforms`: Lists the OS, browser and device combinations TestMu AI supports, to find valid os, browser and version values for a test configuration. With no filters it returns a compact summary: each desktop OS with its browsers \(version count, newest and oldest\) and resolutions, and each mobile platform with i
- `listTunnels`: Retrieve all active TestMu AI tunnel connections for the account. Useful for checking which tunnels are running before starting a new one or debugging local testing connectivity.
- `stopTunnel`: Terminate a specific active tunnel connection by tunnel ID. Use this to clean up tunnels that are no longer needed.
- `deleteSession`: Permanently delete a specific automation test session from TestMu AI by session ID.
- `updateSession`: Update the name or pass/fail status of a test session. Use status\_ind to mark tests as passed, failed, error, or skipped from your test framework.
- `stopSession`: Stop an active running test session on TestMu AI.
- `getSessionScreenshots`: Retrieve command-by-command screenshots captured during a test session. Returns screenshot URLs for each step. Web automation \(Selenium, Playwright, Cypress\) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.
- `getSessionVideo`: Retrieve the video recording URL for a completed test session. Web automation \(Selenium, Playwright, Cypress\) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.
- `getSessionV2CommandLogs`: Retrieve v2 command execution logs for a test session. Returns structured JSON with enhanced detail compared to v1 logs. Web automation \(Selenium, Playwright, Cypress\) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.
- `getSessionV2SeleniumLogs`: Retrieve v2 Selenium/WebDriver grid request and response logs for a test session. Web automation \(Selenium, Playwright, Cypress\) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.
- `postSessionExceptions`: Upload exception/error logs from the client machine for a test session, by session ID. Use this to attach assertion failures or unexpected errors to a session. The result reads the test's exceptions back to confirm they were stored. The automation dashboard may not show exceptions uploaded this way
- `postTestExceptions`: Upload exception logs for a specific test \(by test ID\) rather than by session ID. The result reads the test's exceptions back to confirm they were stored. The automation dashboard may not show exceptions uploaded this way after the test ended.
- `getLiveSessionLogs`: Retrieve the request and response log of a test session, while it runs or after it ends. Web automation \(Selenium, Playwright, Cypress\) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.
- `getOrgConcurrency`: Retrieve the current concurrency usage and limits for the organization on web automation \(Selenium/Cypress\).
- `getAnalyticsData`: Summarises web automation test results in a date range: total tests, passed, failed, completed without a pass/fail mark, pass rate \(passed over all tests, as the Insights page shows it\), pass rate over tests marked passed or failed, average duration and distinct builds, grouped by status, browser, o
- `getFlakyTests`: Lists tests that the insights engine marks as flaky \(passing and failing intermittently\) in a date range, with each test's flake rate, build and environment. Returns only flaky tests, plus how many tests were scanned. Flakiness is only computed for about the last 7 days of tests; the response says h
- `getTestTrends`: Daily trend of web automation test results in a date range: for each day, total tests, passed, failed, completed without a pass/fail mark, pass rate \(passed over all tests\), pass rate over tests marked passed or failed, and average duration.
- `getAnalyticsErrors`: Summarises failed and errored web automation tests in a date range: counts by failure category and by status, and the failing tests themselves with build and environment. Failure categories exist only for about the last 7 days of tests; older failures are counted as uncategorised.
- `deletePrerunFile`: Delete an uploaded prerun file by stored TestMu AI file path.
- `deleteUserFile`: Delete an uploaded user file by stored TestMu AI file path.
- `listUploadedApps`: Retrieve all apps uploaded to TestMu AI for mobile testing. Use type=android/ios for real devices, emulator/simulator for virtual devices.
- `deleteUploadedApps`: Delete one or more uploaded apps from TestMu AI by their app IDs.
- `uploadAppVirtualDevice`: Upload an app \(APK for emulator, IPA for simulator\) to TestMu AI for virtual device \(emulator/simulator\) testing.
- `listDevicesForTesting`: Lists the real devices available on TestMu AI for mobile app testing, 50 per page by default. Filter by region, OS, device name or OS version, and page with limit and offset. The text gives the total that matched.
- `getMobileCapabilityGenerator`: Retrieve capability generation data for mobile automation test configuration.
- `listMobileBuilds`: Lists mobile app automation builds, newest first, 10 per page by default. Page with limit and offset; the result gives the total the API reports. The API returns only builds from the last 90 days, so total can be higher than the builds you can page through.
- `listMobileSessions`: Lists mobile app automation sessions \(tests\), newest first, 10 per page by default, with their video, screenshot and log links. Page with limit and offset, or filter by buildId or status; the result gives the total the API reports.
- `getMobileConcurrency`: Retrieve the current concurrency usage and limits for mobile automation \(real device testing\).
- `checkAppProcessingStatus`: Check whether an uploaded app has been processed and is ready for features like image injection, network logs, and screenshot unblock on real devices. The TestMu AI API has no read-only status call: this one starts or refreshes the processing for the requested features, so the app's last-updated tim
- `tm\_list\_projects`: List all Test Manager projects the authenticated user is allowed to see. Supports keyword search and pagination.
- `tm\_get\_test\_cases`: Find test cases in a project by filters \(folder, priority, automation status, type, tags\) and/or search \(matches test case ID like TC-123, or title; minimum 3 characters\) — returns summaries. Filters combine \(AND\). Pass case\_id instead to get one case's full detail \(steps, BDD scenarios, field value
- `tm\_list\_folders`: Get a folder tree. Test Manager keeps three folder types: Test Cases and Test Runs folders \(per project — pass project\_id\) and Modules folders \(organization-level, since modules are shared across projects — no project\_id needed\). Pick with the tree parameter \(default: test-cases\). New test-case/test
- `tm\_list\_modules`: List the organization's reusable step Modules \(modules are org-level, shared across projects — the same list as the Modules page\). Supports name search and pagination. Reference a module by id when creating or editing a test case to include its steps \(the Module itself is never changed\).
- `tm\_list\_configurations`: List saved run Configurations \(reusable platform / browser / OS / device setups\). To apply one to a run, pass the configuration's TOP-LEVEL id to tm\_create\_test\_run or tm\_update\_test\_run as configuration\_id \(NOT the nested environments\[\].environment\_id\). Pass run\_type to see only the configurations
- `tm\_get\_test\_runs`: Pass run\_id to get one test run's detail plus its result summary \(instance counts by status — passed / failed / skipped / not started / in progress — and pass rate\). Otherwise pass project\_id to list runs with optional filters. Every returned run carries run\_type \("kaneai" or "manual"\) identifying K
- `tm\_get\_milestone`: Pass milestone\_id to get one milestone's detail and live completion progress. Otherwise pass project\_id to list the project's milestones.
- `tm\_get\_coverage\_summary`: Test coverage for a project, overall and per folder, computed live from the project's test cases \(matches the Test Cases screen\). Also answers requirement and traceability coverage: pass jira\_id \(any Jira issue key, e.g. TE-123: a requirement, user story, epic, ticket or bug\) to get that item's test
- `tm\_create\_project`: Create a new Test Manager project. Project & Org Instructions \(Memory Layer\) stay managed in the UI. Deleting projects is not available through this connection.
- `tm\_update\_project`: Update a project's name, description or tags \(fields are merged — only what you pass changes\). Project & Org Instructions stay managed in the UI.
- `tm\_create\_folder`: Create a folder — in a project's Test Cases tree \(default\) or Test Runs tree \(pass project\_id\), or in the organization-level Modules tree \(no project\_id needed; module folders are shared across projects\). Optionally nest it under an existing parent folder to build folder trees. Deleting folders is n
- `tm\_update\_folder`: Rename a folder, change its description, or move it under a different parent folder. Works on all three folder types: per-project Test Cases \(default\) and Test Runs trees, and the organization-level Modules tree. Moves of test-cases/test-runs folders require project\_id; module folders need none.
- `tm\_generate\_test\_cases`: Generate structured test cases from a requirement or prompt using the Test Manager AI generator \(applies the project's Memory Layer — Project & Org Instructions — automatically\) and file them into the chosen folder. Requirement documents, specs, spreadsheets or screenshots can be attached via files
- `tm\_create\_test\_case`: Create a single test case in a project folder, with optional steps and references to existing step Modules \(module steps are included; the Module itself is unchanged\). For creating many cases from a requirement, prefer tm\_generate\_test\_cases.
- `tm\_update\_test\_case`: Edit an existing test case \(fields are merged — only what you pass changes\). test\_steps, when given, REPLACE the case's steps; module\_ids append module reference steps. Deleting test cases is not available through this connection.
- `tm\_create\_test\_run`: Create a test run from chosen test cases — manual \(default\) or KaneAI \(run\_type: "kaneai"\). Each included test case becomes a TEST RUN INSTANCE — the executable copy of that test inside the run, which carries its own status, remarks and exactly one Configuration. The cases must match the run type: K
- `tm\_update\_test\_run`: Update an open test run — overall status \(Passed / Failed / Skipped / In Progress\), title, objective, milestones, folder, add test cases \(each added case becomes a new test run instance; cases must match the run's type — KaneAI or manual\), apply a Configuration to the run's instances \(configuration\_
- `tm\_record\_test\_results`: Record execution results on a MANUAL run's TEST RUN INSTANCES \(the per-run copies of each test case\) — max 500 per request, all-or-nothing \(larger requests are rejected with nothing recorded\). Manual runs only: KaneAI run results are recorded by KaneAI executions, so manual entry on a KaneAI run is
- `tm\_create\_milestone`: Create a milestone in a project \(status: Open\), optionally with description, start/end dates, tags, and existing runs attached.
- `tm\_update\_milestone`: Update a milestone — title, description, dates, tags — or change its status \(e.g. mark it Completed\). Deleting milestones is not available through this connection.
- `tm\_link\_jira\_issue`: Link a test case, test run, or a run result \(instance\) to a Jira issue \(requirement / user story / epic / bug\) — linked test cases are what give the issue its test coverage and traceability. Linking a result also links its case and run. Requires the Jira integration to be set up for the organization
- `tm\_link\_ado\_issue`: Link a test case, test run, or a run result \(instance\) to an Azure DevOps work item \(requirement / user story / bug\) by its URL — linked test cases are what give the work item its test coverage and traceability. Requires the Azure DevOps integration to be set up for the organization — otherwise a cl
- `smartui\_project\_query`: List SmartUI projects, or get one project with its settings — action=get returns baseline\_branch, approvers\[\], smart\_baseline, auto\_approval\_branch, overwrite\_screenshot and project\_category alongside platform and project\_type. Start here when you do not have a project\_id. Read-only.
- `smartui\_build\_query`: List SmartUI builds in a project, get one build, or get the CI gate verdict for a build. Use action=gate in pipelines: it returns verdict \(passed\|failed\|pending\_approval\|running\|error\), totals \(including missing screenshots the baseline has\), blocking\_comparison\_ids, and blocking\[\] with per-item det
- `smartui\_comparison\_query`: List all comparisons in a SmartUI build \(each row returns comparison\_id AND ss\_id\), or get one comparison's detail \(mismatch %, status, correctly-labelled baseline/current/compared asset URLs\). This is how you obtain a comparison\_id — you never need the dashboard. Read-only.
- `smartui\_comparison\_analyze`: Analyze one SmartUI comparison through a lens: consolidated \(default\), pixel, or dom. Returns the comparison data \(mismatch %, verdict, correctly-labelled asset URLs\) plus, for lens=dom, a real DOM byte delta when the artefact is served — no local filesystem needed. consolidated and pixel report ups
- `smartui\_screenshot\_upload`: Upload screenshots to a SmartUI project as a new build, from local file\_paths or from source\_urls \(fetched server-side, so it works without a client filesystem\). Pass project\_id to auto-resolve the project token. Set mark\_baseline=true to seed a baseline. Returns build\_id; follow with smartui\_build\_
- `smartui\_screenshot\_review`: Approve or reject SmartUI comparisons — individually \(comparison\_ids or ss\_ids\), or for a whole build \(all\_matching:\{status\}\). Ids are validated against the build before writing, and results are verified by re-reading status, so the response reports real per-item updated\[\]/failed\[\] and whether the b
- `smartui\_baseline\_manage`: Merge SmartUI baselines across branches or builds \(to read baseline settings, use smartui\_project\_query with action=get\). merge\_branch/merge\_build resolve source and target names to builds, merge them, then poll the merged build and report its real terminal status — a merge that lands in error or wi
- `listHyperExecuteJobs`: List the account's HyperExecute jobs, newest first, with offset pagination and an optional status filter. The status filter looks at the 200 most recent jobs.
- `getHyperExecuteJobArtifacts`: Retrieve all artifacts or categorized errors for a HyperExecute job or task.
- `downloadJobArtifact`: Get an authenticated download URL \(plus size/status metadata\) for a specific HyperExecute job artifact. Requires artefactName \(from getHyperExecuteJobArtifacts\); optionally scope to a task with taskId. Returns a URL to fetch with your TestMu AI credentials rather than the raw file bytes.
- `getJobArtifactDetail`: Get details for a specific artifact within a HyperExecute job.
- `getHyperExecuteStage`: Retrieve the stages of a HyperExecute task \(cache/prerun/scenario/etc.\). Pass a stageId to return just that one stage. Stages are keyed by their parent task, so taskId is required.
- `getHyperExecuteStageLogs`: Retrieve logs for a HyperExecute stage. \(UNDOCUMENTED - may change without notice\)
- `getHyperExecuteStageTasks`: Retrieve tasks for a HyperExecute stage. \(UNDOCUMENTED - may change without notice\)
- `getHyperExecuteTask`: Retrieve details for a HyperExecute task by task ID. \(UNDOCUMENTED - may change without notice\)
- `getHyperExecuteTaskLogs`: Retrieve logs for a HyperExecute task. \(UNDOCUMENTED - may change without notice\)
- `getHyperExecuteJobLiveStream`: Stream live output from a running HyperExecute job. \(UNDOCUMENTED - may change without notice\)
- `analyzeHyperExecuteJob`: Perform a full analysis of a HyperExecute job: fetches job info, sessions, traverses all tasks → scenario stages → console logs, and returns a structured report with test results, per-scenario logs, and pass/fail statistics. Use this for questions like "which tests failed and why" or "show me the co

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html