All servers · Monitoring & logs

TestMu AI (formerly LambdaTest)

io.github.LambdaTest/mcp · v1.0.7

Measured by MCP Station

Description written by the publisher, not verified

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

Connect

claude mcp add --transport http mcp https://mcp.lambdatest.com/mcp

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.lambdatest.com/mcp"
    }
  }
}

Tools as reported by the server

• 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 write/delete
  Renames a TestMu AI web automation build. Overwrites the current build name.
• stopBuild write/delete
  Stops every running test in a TestMu AI web automation build. Running sessions end immediately.
• deleteBuild write/delete
  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 write/delete
  Terminate a specific active tunnel connection by tunnel ID. Use this to clean up tunnels that are no longer needed.
• deleteSession write/delete
  Permanently delete a specific automation test session from TestMu AI by session ID.
• updateSession write/delete
  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 write/delete
  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 write/delete
  Delete an uploaded prerun file by stored TestMu AI file path.
• deleteUserFile write/delete
  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 write/delete
  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 write/delete
  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 write/delete
  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 write/delete
  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 write/delete
  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 write/delete
  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 write/delete
  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 write/delete
  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 write/delete
  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 write/delete
  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

Tool changes

• 2026-10-24: upload_app, generateHyperExecuteYAML, answerHyperExecuteQuery, getHyperExecuteJobInfo, getHyperExecuteJobSessions, getAccessibilityReport, analyzeAppViaTunnel, buildLocalAppForAnalysis, getAutomationTestDetails, getAutomationTestCommandLogs, getAutomationTestNetworkLogs, getAutomationTestBrowserConsoleLogs
• 2026-10-17: upload_app, generateHyperExecuteYAML, answerHyperExecuteQuery, getHyperExecuteJobInfo, getHyperExecuteJobSessions, getAccessibilityReport, analyzeAppViaTunnel, buildLocalAppForAnalysis, getAutomationTestDetails, getAutomationTestCommandLogs, getAutomationTestNetworkLogs, getAutomationTestBrowserConsoleLogs
• 2026-10-16: upload_app, generateHyperExecuteYAML, answerHyperExecuteQuery, getHyperExecuteJobInfo, getHyperExecuteJobSessions, getAccessibilityReport, analyzeAppViaTunnel, buildLocalAppForAnalysis, getAutomationTestDetails, getAutomationTestCommandLogs, getAutomationTestNetworkLogs, getAutomationTestBrowserConsoleLogs

Repository · Website · JSON · Text for agents · Registry updated 2026-10-21