Blog/

AI/ML

Sauce Labs Hosted MCP Connects Your AI Agent to Real Devices and AI Authoring

AI assistants write code faster than most teams can test it. Sauce Labs Hosted MCP server gives Claude, Cursor, and any MCP-compatible AI agent direct access to Sauce Labs devices and test authoring, with nothing to install.

Drew Albee

Drew Albee

Content Specialist

September 2, 2026

Your AI coding assistant can write a test in seconds. Getting that test to actually run somewhere is a different problem entirely. 

Engineering teams increasingly rely on AI assistants for the work itself, not just code generation but CI/CD orchestration and test execution too. 

Testing hasn't kept pace. An AI agent can generate a test case in an instant, but without an entry point into your testing platform, the work stops there. The agent can't discover an available device, kick off the run, or pull back results, and it may encounter issues during the process, so someone opens a browser, logs in to a separate dashboard, hunts down a device, and carries the output back by hand. 

Every context switch costs focus, and testing becomes the one workflow that still makes people leave the tools they've built everything else around.

Sauce Labs Hosted MCP helps to bridge that divide.

What is the Sauce Labs Hosted MCP?

The Sauce Labs Hosted MCP is a hosted Model Context Protocol server solution that provides any AI assistant or agent with direct, natural-language access to the Sauce Labs platform via streamable HTTP. It’s hosted, so there's nothing else to install or maintain, and new tools roll out automatically as the platform grows.

With Sauce Labs’ hosted MCP server connected, an AI agent can: 

  • Generate test cases from natural-language intent and export them as runnable source code. 
  • Run test cases and suites on the Sauce Labs platform and schedule them to run on a recurring cadence. 
  • Discover available real devices and check their status. 
  • Start, inspect, manage, and end sessions. 
  • Install, launch, and uninstall app builds from Sauce Storage. 
  • Capture screenshots. 
  • Pull device logs, read the UI, and run shell commands on a device. 
  • Configure network conditions and capture network traffic. 
  • Inspect jobs, builds, test artifacts, and more. 

Sauce Labs Hosted MCP works with Claude Code, Claude Desktop, Cursor, Windsurf, and any other MCP-compatible client, extending real device testing and AI-powered authoring directly into the tools engineering teams already use. Testing now keeps pace with how modern teams actually build software.

Why the Sauce Labs Hosted MCP is different

All in one server: Sauce Labs is the only MCP that offers AI test authoring and real device execution together. Generate, run, get results in one connection. No competitor does both.

Zero maintenance: Since the MCP is hosted by Sauce Labs, tools update automatically. Competitors ship static local servers that customers must maintain.

Full device control in plain language: Tap, read the UI, shell commands, network capture, multi-device checks, etc. The MCP is usable by PMs and support, not just engineers. 

What this looks like day to day

In mobile development, the Sauce Labs Hosted MCP changes the daily workflow for developers, SDETs, QA leads, and support teams alike. 

A mobile developer gets a crash report and asks their AI assistant, still inside the IDE, to pull the last 30 seconds of device logs, filter for the permission error, and check which shell command triggered it. No provisioning, no separate tab, no waiting on someone else's queue, no lost train of thought.

An SDET picks up a Jira ticket for a login flow, asks their agent to generate the test case, iterates on it in conversation, and pushes the finished code straight to the repo. The test never touches a manual script.

A QA lead needs sign-off across three device and OS combinations before a hotfix ships. One prompt provisions all three, installs the build, and returns side-by-side screenshots, with no additional engineers pulled in.

A support lead fields a report of a blank dashboard on a specific tablet. Instead of escalating to engineering to reproduce it, they ask their AI assistant to check it directly and hand off the screenshot with the ticket. The same connection works whether the person asking is an engineer or not. 

None of these scenarios are hypothetical. Every one of them is a prompt away once you’re connected. 

Getting connected

Point your MCP client to mcp.saucelabs.com and authenticate with your existing Sauce Labs username and access key. From there, try a prompt like "Find an available Galaxy S24 running Android 14, install the latest build, and take a screenshot," or "Generate a test case that logs into saucedemo.com, adds an item to the cart, and verifies the checkout total." Then explore what your workflow actually needs, since the tools cover the full real device and AI test authoring surface.

Setup steps, the full tools reference, and prompting guides are in the documentation.

On This Page

Free trial

Sign up Free

Start testing smarter with the world's largest continuous testing cloud — now with AI built in.

Start Testing

Keep reading.

VIEW ALL POSTS
AI/ML
VIEW ALL POSTS