Connect Claude Code to Sauce Labs
Set up in minutes
Choose where it runs
On your computer through your own Claude Code, or hosted in the cloud. The rest of setup adapts to your choice:
Pick what it can do in Sauce Labs
A preset of real Sauce Labs operations. Each one becomes a tool the agent can call, and it can't touch anything outside the list.
Connect Sauce Labs
One sign-in. The agent acts through your account, scoped to the operations you picked.
Add your personal MCP link
The last step mints a private MCP URL for this agent and walks you through exactly this, with your real link filled in. The page flips to Connected the moment your Claude Code first calls in. Claude Code connects when a session starts — run claude, or restart a running one.
Run this in your terminal
<your-link> is your personal server URL — setup mints it for you.
Tools Claude Code gets
Sauce Labs
15 toolsList device descriptors available to your account.
Read live device availability; public devices have aggregated states.
Allocate a device; poll Get Session until ACTIVE before interacting. Uses your device quota.
Read pending, active and recently closed sessions for the authenticated account.
Release a device session; CLOSING is an acknowledgement, not completed cleanup.
Execute a short Android adb shell command without the adb shell prefix.
Open a URL or iOS deep link on an ACTIVE device; Android uses Chrome.
Start a background app installation; poll List App Installations for completion.
Uninstall the specified iOS bundle or Android package from this device.
Change orientation and optional Android locale/animations during an ACTIVE session.
Start the hosted Appium server for this device session.
About Claude Code
Frequently asked questions
More ways to connect
More tools for Claude Code
Use Sauce Labs with other agents
Open your Claude Code agent in one click.
NoClick runs Claude Code for you with Sauce Labs wired in as tools. Connect your account and run.