TestMu AI (formerly LambdaTest)

Name: TestMu AI (formerly LambdaTest)
Author: LambdaTest

MCP serverMCP

Agentic testing: HyperExecute jobs, test failure triage, SmartUI visual diffs, a11y audits

by LambdaTestrepository ↗homepage ↗v1.0.1

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"testmu-ai-formerly-lambdatest","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability (some checks stopped at authentication)107/108 checks ok

Some successful checks reached the service and some stopped at an authentication response; figures combine both.

when	check	result	http	latency	detail
4 h ago	mcp initialize	ok	200	85 ms	server MCP Lambdatest 1.0.0 · protocol 2025-03-26 · 88 tools
10 h ago	mcp initialize	ok	200	88 ms	server MCP Lambdatest 1.0.0 · protocol 2025-03-26 · 88 tools
17 h ago	mcp initialize	ok	200	87 ms	server MCP Lambdatest 1.0.0 · protocol 2025-03-26 · 98 tools
24 h ago	mcp initialize	ok	200	86 ms	server MCP Lambdatest 1.0.0 · protocol 2025-03-26 · 98 tools
31 h ago	mcp initialize	ok	200	91 ms	server MCP Lambdatest 1.0.0 · protocol 2025-03-26 · 98 tools
2 d ago	mcp initialize	ok	200	340 ms	server MCP Lambdatest 1.0.0 · protocol 2025-03-26 · 98 tools
2 d ago	mcp initialize	failed	—	—	timeout
2 d ago	mcp initialize	ok	200	85 ms	server MCP Lambdatest 1.0.0 · protocol 2025-03-26 · 95 tools
3 d ago	mcp initialize	ok	200	87 ms	server MCP Lambdatest 1.0.0 · protocol 2025-03-26 · 95 tools
3 d ago	mcp initialize	ok	200	91 ms	server MCP Lambdatest 1.0.0 · protocol 2025-03-26 · 95 tools

Tools observed via MCP handshake

upload_app — Uploads an app to LambdaTest for mobile testing and displays upload status.
generateHyperExecuteYAML — Generates a HyperExecute YAML configuration for running tests on LambdaTest's HyperExecute platform. REQUIRED fields: project (language, framework) and testing
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
analyzeAppViaTunnel — Analyzes a locally running app for accessibility via LambdaTest tunnel.
buildLocalAppForAnalysis — Returns step-by-step instructions to build and serve a local web app and open a LambdaTest tunnel to it, so its accessibility can then be scanned with analyzeAp
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 X
automationQuery — Read-only query of LambdaTest automation resources: list builds, get one build, list the sessions in a build, fetch test details, and retrieve test logs (comman
updateBuild — Renames a LambdaTest web automation build. Overwrites the current build name.
stopBuild — Stops every running test in a LambdaTest web automation build. Running sessions end immediately.
deleteBuild — Permanently deletes a LambdaTest 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 LambdaTest supports, to find valid os, browser and version values for a test configuration. With no filters it ret
listTunnels — Retrieve all active LambdaTest tunnel connections for the account. Useful for checking which tunnels are running before starting a new one or debugging local te
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 LambdaTest 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 LambdaTest.
getSessionScreenshots — Retrieve command-by-command screenshots captured during a test session. Returns screenshot URLs for each step.
getSessionVideo — Retrieve the video recording URL for a completed test session.
getSessionV2CommandLogs — Retrieve v2 command execution logs for a test session. Returns structured JSON with enhanced detail compared to v1 logs.
getSessionV2SeleniumLogs — Retrieve v2 Selenium/WebDriver grid request and response logs for a test session.
postSessionExceptions — Upload exception/error logs from the client machine for a test session. Use this to attach assertion failures or unexpected errors to a session.
postTestExceptions — Upload exception logs for a specific test (by test ID) rather than by session ID.
getLiveSessionLogs — Stream live logs from an active test session in real time.
getOrgConcurrency — Retrieve the current concurrency usage and limits for the organization on web automation (Selenium/Cypress).
getAnalyticsData — Summarises automation test results in a date range: total tests, passed, failed, completed without a pass/fail mark, pass rate (over tests marked passed or fail
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. Re
getTestTrends — Daily trend of automation test results in a date range: for each day, total tests, passed, failed, completed without a pass/fail mark, pass rate (over tests mar
getAnalyticsErrors — Summarises failed and errored automation tests in a date range: counts by failure category and by status, and the failing tests themselves with build and enviro
deletePrerunFile — Delete an uploaded prerun file by stored LambdaTest file path.
deleteUserFile — Delete an uploaded user file by stored LambdaTest file path.
listUploadedApps — Retrieve all apps uploaded to LambdaTest for mobile testing. Use type=android/ios for real devices, emulator/simulator for virtual devices.
deleteUploadedApps — Delete one or more uploaded apps from LambdaTest by their app IDs.
uploadAppVirtualDevice — Upload an app (APK for emulator, IPA for simulator) to LambdaTest for virtual device (emulator/simulator) testing.
listDevicesForTesting — Retrieve all available real devices on LambdaTest for mobile app testing. Filter by region and OS.
getMobileCapabilityGenerator — Retrieve capability generation data for mobile automation test configuration.
listMobileBuilds — Retrieve all mobile automation builds from the LambdaTest mobile automation API.
listMobileSessions — Retrieve all mobile automation sessions from the LambdaTest mobile automation API.
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.
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 c
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-lev
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 pagi
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
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 r
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 / t
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;
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
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
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 unch
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 referenc
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
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 become
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
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 connecti
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 t
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 giv
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_s
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
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 basel
smartui_comparison_analyze — Analyze one SmartUI comparison through a lens: consolidated (default), pixel, or dom. Returns the comparison data (mismatch %, verdict, correctly-labelled asset
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)
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 bui
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 sourc
listHyperExecuteJobs — Retrieve a list of HyperExecute jobs for the account with optional filtering by status.
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)
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
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

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.LambdaTest/mcp

first seen 1 mo ago · fetched 3 h agoopen ↗

Field history (7 recent events)

1 mo ago · declared · summary → "Agentic testing: HyperExecute jobs, test failure triage, SmartUI visual diffs, a11y audits"
1 mo ago · declared · description → "Agentic testing: HyperExecute jobs, test failure triage, SmartUI visual diffs, a11y audits"
1 mo ago · declared · publisherName → "LambdaTest"
1 mo ago · declared · homepageUrl → "https://www.testmuai.com/mcp"
1 mo ago · declared · repoUrl → "https://github.com/LambdaTest/mcp-server-guide"
1 mo ago · declared · version → "1.0.1"
1 mo ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from