Lambdatest MCP server
Yes. Lambdatest publishes an official MCP server at https://mcp.lambdatest.com/mcp. It's hosted and lets you sign in with your Lambdatest account. It offers 88 tools. We last checked it on 22 Nov 2026.
Official: answers MCP requests at mcp.lambdatest.com, on Lambdatest's own domain lambdatest.com. Checked 22 Nov 2026. Maintained by Stuart Brameld.
Key facts
As of 22 Nov 2026, Lambdatest's official MCP server scores 90/100 on MartechDB's Agent Readiness Index (v1.1), joint 10th of 38 in Testing & personalisation. It answered 55 of our 55 checks in the last 90 days and lists 88 tools.
How the Agent Readiness Index works · Wrong? Suggest a correction
Lambdatest MCP server review
90/100
Lambdatest's TestMu AI (formerly LambdaTest) scores 90/100 on MartechDB's Agent Readiness Index: one of the easiest marketing tools to connect an AI agent to. That ranks it joint 10th of 38 in Testing & personalisation.
The good
Hosted by Lambdatest: connect by URL, with nothing to install
Sign in with your Lambdatest account: your AI client sets up the sign-in itself, with no API key
Documented, with 88 tools known
Published to the official MCP Registry
Answered 100% of our checks in the last 90 days
No card needed to start
The bad
Nothing we've found.
Official MCP server
TestMu AI (formerly LambdaTest)
Agentic testing: HyperExecute jobs, test failure triage, SmartUI visual diffs, a11y audits
- Address
- https://mcp.lambdatest.com/mcp
- Runs
- Hosted
- Sign-in
- Cost to use
- Plan: Every TestMu AI account · No card neededFrom Lambdatest's own page, pricing from this page
- Official MCP Registry
-
Listed as
io.github.LambdaTest/mcp· published 3 Aug 2026 - How we know it's official
-
- Answers MCP requests at mcp.lambdatest.com, on Lambdatest's own domain lambdatest.com.
- Published in the official MCP Registry as io.github.LambdaTest/mcp, from the LambdaTest GitHub account.
- Documentation
- www.testmuai.com/mcp
- Source code
- github.com/LambdaTest/mcp-server-guide
- Tools
- 88 tools · listed 22 Nov 2026
- First seen
- 3 Aug 2026
- Last checked
-
Reachable ·
16 Nov 2026: reachable17 Nov 2026: reachable18 Nov 2026: reachable19 Nov 2026: reachable20 Nov 2026: reachable21 Nov 2026: reachable22 Nov 2026: reachable
- Uptime
- 100% · 55 of 55 checks reachable since 1 Oct 2026
TestMu AI (formerly LambdaTest) tools (88)
As the server lists them. Names and descriptions are the vendor's own.
-
upload_appUpload App to LambdaTestUploads an app to TestMu AI for mobile testing and displays upload status.
-
generateHyperExecuteYAMLGenerate HyperExecute YAMLGenerates 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: Playwright, Cypress, WebDriverIO, Puppeteer, Taiko - Python: Pytest, Behave, Robot Framework - Java: TestNG, JUnit, Cucumber - Ruby: RSpec, Capybara - C#: NUnit, xUnit, MSTest - Mobile (ONLY use appTesting for these): XCUI (iOS), Espresso (Android), Appium Features: - Smart framework defaults for common configurations - Input validation with security checks - Caching and artifact upload configuration - Git integration via sourcePayload - Mobile app testing support (via optional appTesting field) The appTesting field applies to mobile app testing only; web automation (Selenium, Playwright, Cypress, etc.) leaves it out.
-
answerHyperExecuteQueryAnswer HyperExecute QuestionAnswers questions about HyperExecute features, configuration, usage, troubleshooting, and best practices by searching through documentation.
-
getHyperExecuteJobInfoShow HyperExecute JobFetches and displays information about a HyperExecute job including status, test results, and progress.
-
getHyperExecuteJobSessionsShow HyperExecute Job SessionsFetches and displays session information for a HyperExecute job.
-
getAccessibilityReportGet Accessibility ReportRuns 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, listed once), pages (every scanned page with its score and issue count), failedRules (per-rule totals for the whole scan) and pagination. Each issue carries its own howToFix and criteria, measured for that element - two issues sharing a rule can have different causes and fixes. While pagination.nextOffset is not null the results are incomplete: call again with the testId from the response plus that offset, keeping the same filters, until it is null. Page with testId, never by passing urls again - that starts a new scan, costs another run, and can return a different set of issues whose offsets do not line up. a11yReportLink is the dashboard URL and needs a login; shareableLink is public and i…
-
analyzeAppViaTunnelAnalyze App via TunnelAnalyzes a locally running app for accessibility via TestMu AI tunnel.
-
buildLocalAppForAnalysisBuild and Analyze AppReturns 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.
-
getAutomationTestDetailsGet Automation Test DetailsFetches detailed information about an automation test by ID
-
getAutomationTestCommandLogsGet Automation Test Command LogsFetches command logs for a specific automation test
-
getAutomationTestNetworkLogsGet Automation Test Network LogsFetches network logs for a specific automation test
-
getAutomationTestBrowserConsoleLogsGet Automation Test Browser Console LogsFetches Browser Console logs for a specific automation test. Note: Not available for mobile app automation tests.
-
getAutomationTestSeleniumLogsGet Automation Test Selenium LogsFetches 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.
-
automationQueryAutomation QueryRead-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, test get, and logs get with a logType. List results carry a pagination object; trust it, not result_set.total, which also counts older builds the list no longer returns. logType "instrumentation" returns XCUI and Espresso test logs. Renaming, stopping and deleting builds are separate tools: updateBuild, stopBuild and deleteBuild.
-
updateBuildRename Automation BuildRenames a TestMu AI web automation build. Overwrites the current build name.
-
stopBuildStop Automation BuildStops every running test in a TestMu AI web automation build. Running sessions end immediately.
-
deleteBuildDelete Automation BuildPermanently deletes a TestMu AI web automation build and its test results. Cannot be undone.
-
triggerSuiteRunTrigger Suite RunTriggers a phone call test run for a specific suite. This will initiate phone calls for all scenarios configured in the suite.
-
getSuiteOverviewGet Suite OverviewGets comprehensive suite overview for a project including run counts, latest status, scores, schedule information, and active calls.
-
getSupportedPlatformsGet Supported PlatformsLists 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 its device count and OS versions. Set os (and optionally browser) for the full version list, or os=ios / os=android for device names.
-
listTunnelsList TunnelsRetrieve 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.
-
stopTunnelStop TunnelTerminate a specific active tunnel connection by tunnel ID. Use this to clean up tunnels that are no longer needed.
-
deleteSessionDelete SessionPermanently delete a specific automation test session from TestMu AI by session ID.
-
updateSessionUpdate SessionUpdate 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.
-
stopSessionStop SessionStop an active running test session on TestMu AI.
-
getSessionScreenshotsGet Session ScreenshotsRetrieve 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.
-
getSessionVideoGet Session VideoRetrieve 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.
-
getSessionV2CommandLogsGet Session V2 Command LogsRetrieve 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.
-
getSessionV2SeleniumLogsGet Session V2 Selenium LogsRetrieve 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.
-
postSessionExceptionsPost Session ExceptionsUpload 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 after the test ended.
-
postTestExceptionsPost Test ExceptionsUpload 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.
-
getLiveSessionLogsGet Live Session LogsRetrieve 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.
-
getOrgConcurrencyGet Org ConcurrencyRetrieve the current concurrency usage and limits for the organization on web automation (Selenium/Cypress).
-
getAnalyticsDataGet Analytics DataSummarises 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, os, build, device or day. Computed from the automation test list (up to 5000 tests per call; the total is always exact).
-
getFlakyTestsGet Flaky TestsLists 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 how many tests in the range had it.
-
getTestTrendsGet Test TrendsDaily 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.
-
getAnalyticsErrorsGet Analytics ErrorsSummarises 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.
-
deletePrerunFileDelete Prerun FileDelete an uploaded prerun file by stored TestMu AI file path.
-
deleteUserFileDelete User FileDelete an uploaded user file by stored TestMu AI file path.
-
listUploadedAppsList Uploaded AppsRetrieve all apps uploaded to TestMu AI for mobile testing. Use type=android/ios for real devices, emulator/simulator for virtual devices.
-
deleteUploadedAppsDelete Uploaded AppsDelete one or more uploaded apps from TestMu AI by their app IDs.
-
uploadAppVirtualDeviceUpload App for Virtual DeviceUpload an app (APK for emulator, IPA for simulator) to TestMu AI for virtual device (emulator/simulator) testing.
-
listDevicesForTestingList Devices for TestingLists 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.
-
getMobileCapabilityGeneratorGet Mobile Capability GeneratorRetrieve capability generation data for mobile automation test configuration.
-
listMobileBuildsList Mobile BuildsLists 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.
-
listMobileSessionsList Mobile SessionsLists 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.
-
getMobileConcurrencyGet Mobile ConcurrencyRetrieve the current concurrency usage and limits for mobile automation (real device testing).
-
checkAppProcessingStatusCheck App Processing Status (Real Device)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 time changes. An app id that is not among your uploaded apps returns an error.
-
tm_list_projectsList Test Manager ProjectsList all Test Manager projects the authenticated user is allowed to see. Supports keyword search and pagination.
-
tm_get_test_casesFind / Get Test CasesFind 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 values).
-
tm_list_foldersList FoldersGet 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-run folders can be created with tm_create_folder.
-
tm_list_modulesList Step ModulesList 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_configurationsList Run ConfigurationsList 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 usable for that run type (kaneai vs manual). Each test instance carries exactly one configuration. Configurations are created by humans in the Test Manager UI. They are organization-level (shared by every project), so there is no project filter. Results are paged: the response says how many exist in total; page through them or raise limit to see all.
-
tm_get_test_runsGet Test RunsPass 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 KaneAI runs — the backend stores KaneAI runs with type "Manual" (result-entry mode), so use run_type, not type, to tell them apart.
-
tm_get_milestoneGet MilestonesPass 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_summaryGet Coverage SummaryTest 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 coverage (the test cases linked to it and how many are automated; zero linked cases means uncovered). For a set of requirements, call once per Jira key. A scope with no test cases returns all zeros; a Jira key that does not exist in the connected Jira returns an error.
-
tm_create_projectCreate ProjectCreate 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_projectUpdate ProjectUpdate 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_folderCreate FolderCreate 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 not available through this connection.
-
tm_update_folderUpdate FolderRename 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_casesGenerate Test Cases with AIGenerate 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 to ground the generation. Volume = test_scenario_limit × per_scenario_test_cases_limit, capped at 50 per call. By default all generated cases are saved into the folder (one sub-folder per scenario); pass auto_save=false to review before saving. The call returns FAST with a request_id (and a browser progress URL) — generation takes ~30-90s in the background; call this tool again with just request_id to check progress, fetch results, or save. Note: consumes AI generation credits.
-
tm_create_test_caseCreate Test CaseCreate 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_caseUpdate Test CaseEdit 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_runCreate Test RunCreate 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: KaneAI runs only take KaneAI-authored cases with completed code generation; manual runs only take manual cases. Optionally attach existing milestones, file into a run folder, and apply a Configuration to all instances (KaneAI configurations must be compatible with each case's platform — web/mobile-app/mobile-browser and iOS/Android).
-
tm_update_test_runUpdate Test RunUpdate 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_id; on KaneAI runs it must be kane-supported and platform-compatible with the targeted cases), toggle sequential execution (KaneAI runs), or archive it. Only open (active) runs can be updated; a closed/archived run returns a clear message. Adding cases/milestones appends, never replaces.
-
tm_record_test_resultsRecord Test Results (Bulk)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 rejected. Target an instance by instance_id, or just pass test_case_id and the instance is resolved automatically. Valid statuses: Passed, Failed, Skipped, Not Started (terminal — run-level "In Progress" is set via tm_update_test_run). Re-recording a step status replaces its result: an omitted step remark is cleared; response echoes per-step outcomes. Optional remarks and assignee per result, and per-step results via steps[] (mark individual test steps / BDD scenario rows Passed/Failed/Skipped with remarks, like the UI's per-step Mark Status). Note: this sets INSTANCE statuses; the run's overall status is set separately via tm_update_test_run.
-
tm_create_milestoneCreate MilestoneCreate a milestone in a project (status: Open), optionally with description, start/end dates, tags, and existing runs attached.
-
tm_update_milestoneUpdate MilestoneUpdate 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_issueLink Jira IssueLink 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 — otherwise a clear "set up Jira first" message is returned.
-
tm_link_ado_issueLink Azure DevOps Work ItemLink 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 clear "set up Azure DevOps first" message is returned.
-
smartui_project_querySmartUI Project QueryList 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_querySmartUI Build QueryList 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 detail. verdict=failed covers rejections AND builds that dropped baseline screenshots. Read-only.
-
smartui_comparison_querySmartUI Comparison QueryList 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_analyzeSmartUI Comparison AnalyzeAnalyze 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 upstream numbers and point at the assets; they do not run their own image analysis. lens=dom degrades to a structured error when DOM artefacts are not served. Read-only.
-
smartui_screenshot_uploadSmartUI Screenshot UploadUpload 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_query(action=gate).
-
smartui_screenshot_reviewSmartUI Screenshot ReviewApprove 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 baseline was promoted. Approving comparisons on the baseline branch can promote the build to baseline.
-
smartui_baseline_manageSmartUI Baseline ManageMerge 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 with zero screenshots is returned as a tool error, not as success. Merging permanently changes baseline state: the merged build takes the baseline flag, so a failed merge leaves the baseline on an empty build.
-
listHyperExecuteJobsList HyperExecute JobsList 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.
-
getHyperExecuteJobArtifactsGet HyperExecute Job ArtifactsRetrieve all artifacts or categorized errors for a HyperExecute job or task.
-
downloadJobArtifactDownload Job ArtifactGet 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.
-
getJobArtifactDetailGet Job Artifact DetailGet details for a specific artifact within a HyperExecute job.
-
getHyperExecuteStageGet HyperExecute StageRetrieve 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.
-
getHyperExecuteStageLogsGet HyperExecute Stage LogsRetrieve logs for a HyperExecute stage. (UNDOCUMENTED - may change without notice)
-
getHyperExecuteStageTasksGet HyperExecute Stage TasksRetrieve tasks for a HyperExecute stage. (UNDOCUMENTED - may change without notice)
-
getHyperExecuteTaskGet HyperExecute TaskRetrieve details for a HyperExecute task by task ID. (UNDOCUMENTED - may change without notice)
-
getHyperExecuteTaskLogsGet HyperExecute Task LogsRetrieve logs for a HyperExecute task. (UNDOCUMENTED - may change without notice)
-
getHyperExecuteJobLiveStreamGet HyperExecute Job Live StreamStream live output from a running HyperExecute job. (UNDOCUMENTED - may change without notice)
-
analyzeHyperExecuteJobAnalyze HyperExecute JobPerform 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 console logs for job X".
Connect your AI to Lambdatest
Add the official Lambdatest MCP server to Claude, ChatGPT or your editor.
Connect Lambdatest MCP to Claude
Claude.ai and Claude Desktop
Open Customize, then Connectors.
Click +, then Add custom connector.
Name it Lambdatest, paste the address below and click Add.
Connect Lambdatest MCP to ChatGPT
Open Settings, then Apps, then Advanced settings.
Turn on Developer mode, then click Create.
Name it Lambdatest and paste the address below.
Connect Lambdatest MCP to Cursor
Opens Cursor if it's installed. If nothing happens, use the JSON below.
Connect Lambdatest MCP to VS Code
Opens VS Code if it's installed. Otherwise add the JSON settings from the Cursor tab to your .vscode/mcp.json.
Lambdatest MCP server questions
Does Lambdatest have an official MCP server?
Yes. Lambdatest publishes its MCP server itself. Its address is on Lambdatest's own domain (mcp.lambdatest.com). MartechDB only lists servers a vendor publishes, never community copies.
What is the Lambdatest MCP server URL?
The address is https://mcp.lambdatest.com/mcp.
Does the Lambdatest MCP server need an API key?
No. You sign in with your Lambdatest account (OAuth), and your AI client handles the rest.
How do I connect Lambdatest MCP to Claude, ChatGPT or Cursor?
In Claude, add https://mcp.lambdatest.com/mcp as a custom connector (Customize, Connectors, Add custom connector). In ChatGPT, turn on developer mode (Settings, Apps, Advanced settings) and create an app with the same address. In Cursor, use the Add to Cursor link on MartechDB's page, or paste the JSON settings into your mcp.json. In Claude Code, run: claude mcp add --transport http lambdatest https://mcp.lambdatest.com/mcp
What can the Lambdatest MCP server do?
It offers 88 tools, including upload_app, generateHyperExecuteYAML, answerHyperExecuteQuery, getHyperExecuteJobInfo and getHyperExecuteJobSessions (as listed on 22 Nov 2026). 53 are marked read-only and 19 can delete or overwrite data.
Is the Lambdatest MCP server in the official MCP Registry?
Yes, as io.github.LambdaTest/mcp.
Is the Lambdatest MCP server working?
Yes. It answered our most recent check. We last checked it on 22 Nov 2026.
What are the alternatives to Lambdatest's MCP server?
In Testing & personalisation, the most agent-friendly alternatives with an official MCP server are Unbounce (100/100), Userbrain (97/100), LaunchDarkly (97/100), PostHog (97/100) and Leadpages (95/100). Lambdatest scores 90/100 on the same index.
Alternatives to Lambdatest's MCP server
Vendors in Testing & personalisation with an official MCP server, the most agent-friendly first. Lambdatest scores 90/100.
Unbounce
unbounce.com
Userbrain
userbrain.com
LaunchDarkly
launchdarkly.com
PostHog
posthog.com
Leadpages
leadpages.com
Change history
What we've seen change for Lambdatest, newest first.
-
Lambdatest: TestMu AI (formerly LambdaTest): 10 tools removed (now 88)
-
Lambdatest: TestMu AI (formerly LambdaTest): 3 tools added (now 98)
Use with AI
Connect your AI to MartechDB
Then ask it about Lambdatest, or any of the 1,850 marketing tools with an official MCP server. Free, no sign-in.
Claude.ai and Claude Desktop
Open Customize, then Connectors.
Click +, then Add custom connector.
Name it MartechDB, paste the address below and click Add. There's no sign-in.
The free plan allows one custom connector. On Team and Enterprise plans, an owner adds the connector first.
Claude Code
Run this in your terminal:
ChatGPT
Open Settings, then Apps, then Advanced settings.
Turn on Developer mode, then click Create.
Name it MartechDB, paste the address below and choose No authentication.
Developer mode is on Plus and Pro plans, and on Business, Enterprise and Edu if an admin allows it.
API
The same data as JSON, with no sign-in. See the OpenAPI description for every endpoint and field.
CLI
Search the directory and print the command to connect a vendor's server, from your terminal. Needs Node 18 or later. View on npm
Show that your MCP server is verified
If you work at Lambdatest, add this badge to your MCP docs or README. It's free, it's the same for every vendor, and it updates from our daily checks: it shows uptime while the server responds, and says so if it stops.
Something wrong or out of date? Suggest a correction or email us, and we'll check it against the evidence. Every correction we make is listed on Corrections.