Can my AI agent stop a runaway test job automatically?

Yes. If you notice a particular build is stuck, you can tell your agent: 'Check the currently running jobs in Sauce Labs and stop any that have been running for more than 40 minutes.' The agent will use `list_jobs` and conditionally call `stop_job` on the offending ones to free up your concurrency limit.

How do I securely inspect the exact failure from an automation script?

If a CI action fails, ask the agent to 'List the latest builds.' Note the failing Build ID, request 'Get details for the failing jobs in this build'. The agent can return the exact error message, browser specs, and direct URL to the video session inside Sauce Labs.

Can the agent tell me why my cloud jobs are in a 'queued' status?

Yes. This is a common DevOps question. You can prompt: 'Check our concurrency limits and active tunnels.' The agent will use `get_concurrency` to see if your team maxed out available nodes and `list_tunnels` to ensure Sauce Connect hasn’t dropped the connection.

Sauce Labs MCP Server for VS Code Copilot 11 tools — connect in under 2 minutes

Name: Sauce Labs
Availability: InStock
Author: Vinkius

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

Built by Vinkius GDPR 11 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 Sauce Labs and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "sauce-labs": {
      "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 Sauce Labs MCP Server

Connect your Sauce Labs account to any AI agent to bring your entire test execution landscape directly into your chat workflow. Say goodbye to jumping between CI/CD tools and the Sauce Labs dashboard to investigate failures.

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

What you can do

Jobs & Builds — Check the status of recent test builds, drill down into specific job results, and monitor pass/fail ratios
Incident Management — Programmatically stop hung or failing jobs to free up test concurrency limits instantly
Infrastructure Metrics — Check your active Sauce Connect tunnels, current account activity, and real-time concurrency metrics
Platform Support — Browse supported OS and browser combinations (Appium, WebDriver) directly through the agent

The Sauce Labs MCP Server exposes 11 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 Sauce Labs to VS Code Copilot via MCP

Follow these steps to integrate the Sauce Labs 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 Sauce Labs

Ask Copilot: "Using Sauce Labs, help me...". 11 tools available

Why Use VS Code Copilot with the Sauce Labs MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Sauce Labs 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

Sauce Labs + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Sauce Labs 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

Sauce Labs MCP Tools for VS Code Copilot (11)

These 11 tools become available when you connect Sauce Labs to VS Code Copilot via MCP:

get_activity

Retrieves current account activity levels

get_build

Retrieves details for a specific build

get_build_jobs

Lists all individual jobs within a specific build

get_concurrency

Retrieves account concurrency limits

get_job

Retrieves details for a specific test job

get_status

Checks current Sauce Labs platform availability

list_builds

Lists recent automation builds

list_jobs

). Lists recent test jobs on Sauce Labs

list_platforms

Specify all, appium, or webdriver. Lists all supported OS and browser combinations

list_tunnels

Lists active Sauce Connect tunnels

stop_job

Stops a running test job

Example Prompts for Sauce Labs in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Sauce Labs immediately.

"What is our current concurrency usage vs limit in Sauce Labs?"

"Show me the jobs that failed in my last automation build."

"Stop the test job ID 4f4f391e0 because it's stuck."

Troubleshooting Sauce Labs MCP Server with VS Code Copilot

Common issues when connecting Sauce Labs 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.

Sauce Labs + VS Code Copilot FAQ

Common questions about integrating Sauce Labs 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.