LambdaTest MCP server
88 tools · Last check that passed 27 Oct 2026, 01:50 UTC
TestMu AI's own remote MCP server, formerly LambdaTest's, gives an agent the test jobs, builds, sessions, logs, visual comparisons, accessibility scans and test management projects of the TestMu AI account it signs in to. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 88 tools
| Tool | Counted as |
|---|---|
deleteBuild | Deletes |
deletePrerunFile | Deletes |
deleteSession | Deletes |
deleteUploadedApps | Deletes |
deleteUserFile | Deletes |
smartui_baseline_manage | Deletes |
smartui_screenshot_review | Deletes |
smartui_screenshot_upload | Deletes |
stopBuild | Deletes |
stopSession | Deletes |
stopTunnel | Deletes |
tm_record_test_results | Deletes |
tm_update_folder | Deletes |
tm_update_milestone | Deletes |
tm_update_project | Deletes |
tm_update_test_case | Deletes |
tm_update_test_run | Deletes |
updateBuild | Deletes |
updateSession | Deletes |
analyzeAppViaTunnel | Changes things |
analyzeHyperExecuteJob | Changes things |
answerHyperExecuteQuery | Changes things |
buildLocalAppForAnalysis | Changes things |
checkAppProcessingStatus | Changes things |
generateHyperExecuteYAML | Changes things |
getAccessibilityReport | Changes things |
getHyperExecuteJobArtifacts | Changes things |
getHyperExecuteJobInfo | Changes things |
getHyperExecuteJobLiveStream | Changes things |
getHyperExecuteJobSessions | Changes things |
getHyperExecuteStage | Changes things |
getHyperExecuteStageLogs | Changes things |
getHyperExecuteStageTasks | Changes things |
getHyperExecuteTask | Changes things |
getHyperExecuteTaskLogs | Changes things |
getTestTrends | Changes things |
listHyperExecuteJobs | Changes things |
postSessionExceptions | Changes things |
postTestExceptions | Changes things |
smartui_project_query | Changes things |
tm_create_folder | Changes things |
tm_create_milestone | Changes things |
tm_create_project | Changes things |
tm_create_test_case | Changes things |
tm_create_test_run | Changes things |
tm_generate_test_cases | Changes things |
tm_link_ado_issue | Changes things |
tm_link_jira_issue | Changes things |
triggerSuiteRun | Changes things |
upload_app | Changes things |
uploadAppVirtualDevice | Changes things |
automationQuery | Said to only read |
downloadJobArtifact | Said to only read |
getAnalyticsData | Said to only read |
getAnalyticsErrors | Said to only read |
getAutomationTestBrowserConsoleLogs | Said to only read |
getAutomationTestCommandLogs | Said to only read |
getAutomationTestDetails | Said to only read |
getAutomationTestNetworkLogs | Said to only read |
getAutomationTestSeleniumLogs | Said to only read |
getFlakyTests | Said to only read |
getJobArtifactDetail | Said to only read |
getLiveSessionLogs | Said to only read |
getMobileCapabilityGenerator | Said to only read |
getMobileConcurrency | Said to only read |
getOrgConcurrency | Said to only read |
getSessionScreenshots | Said to only read |
getSessionV2CommandLogs | Said to only read |
getSessionV2SeleniumLogs | Said to only read |
getSessionVideo | Said to only read |
getSuiteOverview | Said to only read |
getSupportedPlatforms | Said to only read |
listDevicesForTesting | Said to only read |
listMobileBuilds | Said to only read |
listMobileSessions | Said to only read |
listTunnels | Said to only read |
listUploadedApps | Said to only read |
smartui_build_query | Said to only read |
smartui_comparison_analyze | Said to only read |
smartui_comparison_query | Said to only read |
tm_get_coverage_summary | Said to only read |
tm_get_milestone | Said to only read |
tm_get_test_cases | Said to only read |
tm_get_test_runs | Said to only read |
tm_list_configurations | Said to only read |
tm_list_folders | Said to only read |
tm_list_modules | Said to only read |
tm_list_projects | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
12 of the last 12 checks passed
A check passes when the server lists its tools. Checked at https://mcp.lambdatest.com/mcp.
Recent changes
24 Oct 2026, 06:11 UTC, after a check on 23 Oct 2026, 09:54 UTC
Can do more Description rewritten on analyzeAppViaTunnel, automationQuery, buildLocalAppForAnalysis, checkAppProcessingStatus, deleteBuild and 15 more. The server's own labels changed on analyzeAppViaTunnel. Counted as able to do more: analyzeAppViaTunnel (create or change things).
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when LambdaTest's tools change.
One email when LambdaTest's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- Its HyperExecute tools generate test configurations, trigger jobs and report their status. TestMu AI's MCP server setup guide
- Its Test Manager tools create test runs and record results in bulk, and other tools upload mobile apps for testing. TestMu AI's MCP overview
- Test logs, console output and network logs from the apps under test come back to the agent, and text an agent reads can carry instructions for it. OWASP, prompt injection
How to limit it
With LambdaTest's own settings, as its documentation describes them. Stackduke has not tested them.
- What the agent can reach follows the permissions of the TestMu AI account that signs in, so we recommend an account with no more than the agent needs. TestMu AI's MCP server documentation
- End a connection with the disconnect or clear authentication option in the client's MCP settings, as TestMu AI describes. TestMu AI's MCP server documentation
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.