TestMu AI (formerly LambdaTest)
Agentic AI quality engineering: run, debug and triage tests on real browsers and devices
What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: triage support tickets.Similar tools
Listed for the same task: triage support ticketsReviews
No review yet. Used TestMu AI (formerly LambdaTest)? Be the first to help others choose.What it does
TestMu AI (formerly LambdaTest) is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to one capability: ticket triage. That makes it a candidate for tasks such as triage support tickets or automate customer support.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 12h ago (live check)Hosted endpoint
https://mcp.lambdatest.com/mcpstreamable-http
In Claude Code: claude mcp add --transport http testmu-ai-formerly-lambdatest https://mcp.lambdatest.com/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"testmu-ai-formerly-lambdatest": {
"url": "https://mcp.lambdatest.com/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 12h agoONLINE TestMu AI (formerly LambdaTest) answered an MCP connection on 17 Nov 2026 and introduced itself as TestMu AI MCP 1.0.7 (MCP protocol 2025-03-26).
88 tools offered to AI assistants
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. SupportanswerHyperExecuteQuery· 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 paanalyzeAppViaTunnel· 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 thgetAutomationTestDetails· Fetches detailed information about an automation test by IDgetAutomationTestCommandLogs· Fetches command logs for a specific automation testgetAutomationTestNetworkLogs· Fetches network logs for a specific automation testgetAutomationTestBrowserConsoleLogs· Fetches Browser Console logs for a specific automation test. Note: Not available for mobile app automation tests.
Show 76 more
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 platfupdateBuild· 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, newestlistTunnels· 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 thegetSessionVideo· 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 cagetSessionV2SeleniumLogs· 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 ofpostSessionExceptions· 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 autpostTestExceptions· 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 endgetLiveSessionLogs· 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 lgetOrgConcurrency· 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, averagegetFlakyTests· 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 compgetTestTrends· 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 durationgetAnalyticsErrors· 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; olddeletePrerunFile· 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 youlistMobileSessions· 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 processitm_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 gtm_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 withtm_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 includetm_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[].entm_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 returntm_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 requiremetm_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 existintm_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-rutm_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, stm_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_casetm_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 exatm_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),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 recordtm_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. Reqtm_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 insmartui_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 wsmartui_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 hassmartui_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 nsmartui_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 — nsmartui_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 ssmartui_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 responssmartui_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 reportlistHyperExecuteJobs· 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 TestMgetJobArtifactDetail· 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 qu
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Version | 1.0.7 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Hosted endpoint | https://mcp.lambdatest.com/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Website | https://www.testmuai.com/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Repository | https://github.com/LambdaTest/mcp-server-guide | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
- VERSION21 Oct 20261.0.1 → 1.0.7
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is TestMu AI (formerly LambdaTest) still online?
Free alerts · no account▲ 0Do you run TestMu AI (formerly LambdaTest)? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about TestMu AI (formerly LambdaTest)
How do I connect TestMu AI (formerly LambdaTest)?
Use the hosted endpoint https://mcp.lambdatest.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does TestMu AI (formerly LambdaTest) offer?
When Electra Index connected on 17 Nov 2026, it listed 88 tools: upload_app, generateHyperExecuteYAML, answerHyperExecuteQuery, getHyperExecuteJobInfo, getHyperExecuteJobSessions, getAccessibilityReport, analyzeAppViaTunnel, buildLocalAppForAnalysis and more. The full list is in "Live check" above.
Is TestMu AI (formerly LambdaTest) online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 12h ago.
What can I use TestMu AI (formerly LambdaTest) for?
Based on its description, it is most relevant to: triage support tickets, automate customer support.