# LambdaTest MCP

> LambdaTest MCP manages cross-browser and device testing for web apps. Your agent runs automated or manual tests across thousands of real browsers (Chrome, Safari, Edge) and operating systems in the cloud. It gives you full visibility into build status, session logs, and pass/fail metrics without needing to navigate a complex dashboard.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Tags:** cross-browser-testing, automated-testing, test-automation, session-recording, build-monitoring, qa-testing

## Description

Need to know if your app works on Safari 17 or Windows 10? This MCP connects your agent directly to LambdaTest, letting you manage cross-browser testing through simple conversation. You stop clicking through endless dashboards. Instead, your AI client handles the complexity. It lets you list recent automation builds and check their pass/fail rates instantly. Curious why a test failed? Your agent can pull detailed execution logs or retrieve specific session details, complete with screenshots and video recordings. When you connect this MCP via Vinkius, your agent gets access to all these controls—from checking available platforms to updating the final outcome of a run. This means QA teams get immediate status reports on everything from build metadata to individual test outcomes.

## Tools

### get_build_details
Retrieves specific metadata about a finished test build.

### get_test_logs
Fetches the full, detailed execution logs for debugging purposes.

### get_session_details
Gets specific information about a single test run instance.

### list_automation_builds
Provides a list of all recent automated test builds, with options to filter by status.

### list_supported_platforms
Lists every combination of operating systems and browsers available for testing.

### list_test_sessions
Generates a list of individual test runs, filterable by the specific build ID.

### update_session_status
Allows you to manually set the final pass/fail status for a completed test session.

## Prompt Examples

**Prompt:** 
```
Show all builds and the latest test results.
```

**Response:** 
```
Builds: 12 total. Latest: Build #45 — 'Regression Suite' (42 tests, 38 passed ✅, 3 failed ❌, 1 error ⚠️). Build #44 — 'Smoke Tests' (15 tests, 15 passed ✅). Build #43 — 'Cross-browser' (28 tests, 26 passed, 2 failed). Pass rate (7 days): 91%. Failed tests in Build #45: 'Login Page — Firefox 120', 'Checkout — Safari 17', 'Search — Edge 121'.
```

**Prompt:** 
```
Show the session details and screenshots for the failed login test.
```

**Response:** 
```
Session: 'Login Page — Firefox 120'. Status: ❌ Failed. Duration: 45s. Browser: Firefox 120.0 / Windows 11. Error: Element not found '#submit-btn' (timeout after 10s). Screenshots: 3 captured. Step 1: Page loaded ✅. Step 2: Email entered ✅. Step 3: Submit click ❌ (element missing). Video recording: available (45s). Console errors: 1 — 'Uncaught TypeError: Cannot read property of null'.
```

**Prompt:** 
```
List available browsers and recent automation run statistics.
```

**Response:** 
```
Browsers: Chrome (118-124), Firefox (115-121), Safari (16-17), Edge (118-124), Opera (104-108). OS: Windows 11/10/8, macOS Sonoma/Ventura/Monterey, Ubuntu 22/20. Stats (30 days): 456 sessions, 38 builds, 91.2% pass rate. Average duration: 2.3 min. Most tested: Chrome 124/Win11 (180 sessions). Flaky tests: 4 identified.
```

## Capabilities

### List and analyze automation builds
Your agent lists all recent test runs, allowing you to filter results by their current success or failure status.

### Track individual test sessions
You can view specific test runs, accessing logs, screenshots, and video recordings for deep debugging.

### Check platform compatibility
The MCP lists every OS/Browser combination currently supported by LambdaTest so you know exactly where your app is being tested.

### Get build status and metadata
Your agent provides background information on specific test builds, including high-level success metrics.

### Update test results
You can manually set the final outcome or status for a completed test session.

## Use Cases

### Debugging an intermittent failure on Safari
A developer notices the login button fails only in older versions of Safari. They tell their agent to list_test_sessions, filtering by build ID and 'Safari'. The agent retrieves specific session details (get_session_details) for the failed runs, providing screenshots showing exactly which element is missing.

### Pre-release signoff review
A Test Lead needs to confirm if a new feature works across all major platforms. They ask their agent to list_supported_platforms and then check the pass rate using list_automation_builds, quickly confirming 95% coverage before authorizing deployment.

### Immediate post-deployment triage
A QA Engineer detects a critical bug in production. They tell their agent to retrieve execution logs (get_test_logs) for the last build, focusing on 'Checkout' failures. The agent pulls the detailed log instantly, saving hours of manual investigation.

### Updating status after manual QA
The team manually verifies a fix for Build #45. Instead of logging into the web portal to change the result, they use update_session_status via their agent to mark the session as 'Passed'.

## Benefits

- Quickly assess build health. Instead of diving into a dashboard, you ask your agent to list_automation_builds and instantly know the pass/fail rates across all recent test builds.
- Deep failure analysis is fast. If something breaks, your agent retrieves full execution logs via get_test_logs, letting developers jump straight to the error without manual searching.
- Full visibility into compatibility. Use list_supported_platforms to confirm that every target browser and OS combination—from Safari 17 to Edge 124—is covered before launch.
- Pinpoint failure sources. You can use list_test_sessions to narrow down the issue, then get_session_details to pull screenshots or video recordings for immediate context.
- Control test outcomes. Need to manually verify a fix? update_session_status lets you set the final outcome of a session without logging into the web portal.

## How It Works

The bottom line is that you talk to your agent like talking to a teammate and get structured test data back immediately.

1. Subscribe to this MCP and provide your LambdaTest Username and Access Key credentials.
2. Connect your preferred AI client (like Cursor or Claude) through the Vinkius Marketplace.
3. Start asking questions about builds, sessions, or available platforms using natural language conversation.

## Frequently Asked Questions

**How do I check if my app works on multiple browsers using LambdaTest MCP?**
You can list_supported_platforms to see every combination available, and then run list_automation_builds to see the pass rates across all those platforms.

**What is the difference between get_test_logs and get_session_details?**
get_test_logs gives you a long stream of raw execution data for debugging. get_session_details provides structured metadata, including screenshots and video links, about one specific test run.

**Can I force the status update using LambdaTest MCP?**
Yes. If manual testing confirms a bug fix or verifies a result, you can use update_session_status to set the final outcome of that session directly through your agent.

**Does this MCP help me find out which platforms are available?**
Absolutely. Running list_supported_platforms immediately gives you a comprehensive breakdown of every browser and OS combination LambdaTest supports for testing.