Can I see the exact console errors from a failed browser test through my agent?

Yes. Use the `get_session_details` tool with a specific Session ID. Your agent will retrieve full metadata including console logs, network configurations, and execution artifacts, helping you identify the root cause of the failure instantly.

How do I retrieve the video recording of a specific test execution?

Ask your agent to `get_session_video` for a targeted Session ID. Your agent will return the absolute MP4 URL to stream or download the complete browser session recording, which is essential for debugging flakey UI bugs.

Can my agent check if our secure localhost tunnel is active?

Absolutely. Use the `list_active_tunnels` tool to identify dedicated private connection endpoints. Your agent will report which TestMu AI tunnels are currently running, ensuring you can test local environments from the cloud.

TestMu AI (formerly LambdaTest) MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: TestMu AI (formerly LambdaTest)
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install TestMu AI (formerly LambdaTest) and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "testmu-ai-formerly-lambdatest": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About TestMu AI (formerly LambdaTest) MCP Server

Connect your TestMu AI (formerly LambdaTest) account to any AI agent and take full control of your cross-browser testing and automation orchestration through natural conversation.

GitHub Copilot Agent mode brings TestMu AI (formerly LambdaTest) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Build Orchestration — List all test automation builds and retrieve high-level aggregated telemetry for Selenium, Playwright, or Cypress suites directly from your agent
Session Inspection — Deep-dive into individual browser test sessions to extract console errors, network configurations, and exact metadata required for rapid debugging
Visual Artifacts — Fetch absolute URLs for bug screenshots and full video recordings of browser executions to reproduce flakey UI issues instantly
Precision Logging — Extract command-level logs including W3C WebDriver protocols or Playwright RPC calls with precise execution timestamps
Tunnel & Platform Audit — Monitor active secure tunnels for localhost testing and query the grid for supported macOS, Windows, iOS, and Android capabilities
Environment Mapping — Filter and retrieve all child test sessions nested under specific CI/CD builds to isolate and analyze deployment regressions

The TestMu AI (formerly LambdaTest) MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect TestMu AI (formerly LambdaTest) to VS Code Copilot via MCP

Follow these steps to integrate the TestMu AI (formerly LambdaTest) MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using TestMu AI (formerly LambdaTest)

Ask Copilot: "Using TestMu AI (formerly LambdaTest), help me...". 10 tools available

Why Use VS Code Copilot with the TestMu AI (formerly LambdaTest) MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with TestMu AI (formerly LambdaTest) through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

TestMu AI (formerly LambdaTest) + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the TestMu AI (formerly LambdaTest) MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

TestMu AI (formerly LambdaTest) MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect TestMu AI (formerly LambdaTest) to VS Code Copilot via MCP:

get_build

Get exact telemetry for a specific LambdaTest build

get_build_sessions

Extract all explicit test sessions associated with a Build

get_screenshots

saveScreenshot()` or failure-hook logic within the LambdaTest grid. Fetch visual bug screenshots captured during a test session

get_session

Identifies explicit console errors, network configuration, and URL artifacts necessary to debug why a specific UI interaction failed. Get deep context for a specific automated test session

get_session_logs

Extract precise Selenium/Appium command logs for a test

get_video

Retrieve the full video recording URL for a test execution

list_builds

Groups thousands of executed Selenium, Cypress, Playwright, or Appium browser tests into their respective parent CI/CD builds. List all test automation builds on LambdaTest Cloud

list_platforms

Returns exactly which combinations of macOS, Windows, iOS, and Android versions are actively available in the testing grid. List all supported OS/browser capabilities available

list_sessions

Provides OS, Browser version, execution duration, and final completion status of the Selenium/Playwright scripts. List recent automated test sessions executed on LambdaTest

list_tunnels

List all active secure Tunnels (UnderTest tunnels)

Example Prompts for TestMu AI (formerly LambdaTest) in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with TestMu AI (formerly LambdaTest) immediately.

"List the last 5 automation builds in my TestMu AI account"

"Show me the logs and screenshots for session ID 'abc-123-xyz'"

"Which OS and browser versions are currently supported in the grid?"

Troubleshooting TestMu AI (formerly LambdaTest) MCP Server with VS Code Copilot

Common issues when connecting TestMu AI (formerly LambdaTest) to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

TestMu AI (formerly LambdaTest) + VS Code Copilot FAQ

Common questions about integrating TestMu AI (formerly LambdaTest) MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.