developer-toolsoauth2

Saucelabs

Sauce Labs provides a comprehensive continuous testing cloud for web and mobile app testing across browsers and devices.

Verdict

The Sauce Labs MCP lets your team query test infrastructure status, check platform support, and pull job history without leaving Switchy. @mention it to see which browser/device combos are available, confirm Appium versions still have support, or grab recent test run details for a retrospective. Developers and QA engineers use it to triage flaky tests, validate environment configs, and surface wait times before kicking off a suite. OAuth setup requires a Sauce Labs account with API access — free-tier accounts may hit rate limits on job queries.

Common use cases

  • Check service health before launching test suites
  • Validate browser and device platform availability
  • Pull recent job history for sprint reviews
  • Confirm Appium version support before upgrading
  • Surface tunnel versions for CI pipeline updates

Integration

Vendor
Saucelabs
Category
developer-tools
Auth
OAUTH2
Tools
7
Composio slug
saucelabs

Tools

  • Get API Status

    Tool to retrieve the current operational status of Sauce Labs services. Use when you need to check if Sauce Labs is up and running or to get current wait times.

  • Get Appium EOL

    Tool to retrieve end-of-life information for Appium versions. Returns Unix timestamps indicating when Sauce Labs support for each Appium version will be discontinued. Use when checking version compatibility or planning Appium upgrades.

  • Get Performance API Definition

    Tool to retrieve the OpenAPI/Swagger JSON documentation for the Sauce Labs Performance API. Use when you need to understand the API specification, endpoints, or schemas available in the Performance API.

  • Get Supported Platforms

    Tool to get supported platforms for an automation API. Use when you need to retrieve available platforms for Appium, WebDriver, or all automation APIs on Sauce Labs.

  • Get Tunnel Versions

    Tool to retrieve information about available Sauce Connect tunnel versions. Use when checking for the latest version, downloading specific platform binaries, or listing all available versions.

  • List Jobs

    Tool to retrieve all jobs for a SauceLabs user. Use when you need to list test execution jobs with optional filters for time range, job type, or owner.

  • List VDC Jobs

    Tool to list virtual device cloud (VDC) testing jobs for a Sauce Labs user. Use when you need to retrieve test execution history or job details.

Setup

Setup guide

  1. 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Find Sauce Labs under Developer Tools and click Connect. 3. You'll be redirected to Sauce Labs to authorize Switchy — log in with your Sauce Labs credentials. 4. Grant read access to jobs, platforms, and status endpoints (Switchy requests the minimum scopes needed for the seven tools). 5. After authorizing, you'll return to Switchy and see a green checkmark next to Sauce Labs. 6. Open any Space, type '@Saucelabs get API status' and send — if the MCP replies with current service health, the connection works. 7. To invoke other tools, @mention Saucelabs followed by a natural request like 'list my last 10 jobs' or 'show supported platforms for Appium'.

What teammates see: by default, memories from Saucelabs are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

Service Health Check

@Saucelabs get the current API status and let me know if there are any service disruptions or elevated wait times right now.
Open in a Space →

Platform Compatibility Lookup

@Saucelabs show me all supported platforms for WebDriver automation, including browser versions and operating systems.
Open in a Space →

Recent Job Summary

@Saucelabs list my last 20 jobs from the past week, including job names, statuses, and completion times.
Open in a Space →

Appium Version Support

@Saucelabs get the Appium end-of-life schedule and highlight any versions losing support in the next six months.
Open in a Space →

Tunnel Version Check

@Saucelabs list all available Sauce Connect tunnel versions and provide the download link for the latest stable release.
Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@saucelabs list all test jobs from the last 48 hours and show me which ones failed

Output

Found 23 test jobs in the last 48 hours. 4 jobs failed: 'checkout-flow-chrome' (timeout after 5m), 'mobile-login-ios' (assertion error on line 42), 'api-integration-suite' (network error), and 'cross-browser-nav' (element not found). The remaining 19 jobs passed. All failed jobs ran on standard VMs; no device cloud failures detected.

Notes

This example shows the MCP's ability to filter and surface job status across your test history. Requires OAuth2 scope for reading job metadata. Note that job details (logs, screenshots) aren't included in the list response — you'd need follow-up queries to drill into specific failures.

Prompt

@saucelabs check if Sauce Labs is currently operational and what the wait times look like for our region

Output

Sauce Labs services are fully operational. Current wait times: US West (0-2 seconds), US East (1-3 seconds), EU Central (0-1 seconds). No incidents reported in the last 24 hours. All automation APIs (Appium, WebDriver) are responding normally.

Notes

This read-only check is useful before kicking off large test suites or debugging flaky runs. The MCP fetches live status data, so you can confirm infrastructure issues aren't causing your test failures. No side effects; safe to run anytime.

Prompt

@saucelabs we're planning to upgrade our test suite — which Appium versions are being deprecated soon, and what platforms are supported for WebDriver?

Output

Appium EOL timeline: version 1.22.x support ends March 2025 (4 months), version 2.0.x supported through December 2026. For WebDriver, Sauce Labs currently supports 847 platform combinations including Chrome 120-131, Firefox 115-133, Safari 16-18, Edge 120-131 across Windows 10/11, macOS 13-15, and various mobile OS versions. Recommend migrating to Appium 2.x before Q1 2025.

Notes

This synthesis example shows the MCP combining version lifecycle data with platform availability to inform upgrade planning. The AI interprets Unix timestamps and cross-references them with current dates. Useful for roadmap discussions, but always verify deprecation dates in Sauce Labs docs before committing to timelines.

Use-case deep-dives

Mobile release testing coordination

When Sauce Labs MCP speeds up pre-release QA handoffs

A 6-person mobile team shipping bi-weekly releases uses this MCP to pull VDC job lists and platform support data directly into their Slack standup thread. The QA lead asks Switchy "show me failed iOS tests from yesterday's build" and gets a filtered job list without opening the Sauce dashboard. The MCP's List VDC Jobs and Get Supported Platforms tools handle the common case: checking test coverage across device matrices and triaging failures before the release cut. This works well for teams running 50-200 tests per sprint. If you're running thousands of parallel jobs or need deep performance metrics, you'll still open the full Sauce UI for drill-down. For teams where the QA lead is the bottleneck on release-go decisions, this MCP cuts 15 minutes off every triage session.

Support ticket device compatibility lookup

Why this MCP fits customer-facing engineering teams

A 3-person support engineering team at a B2C app uses this MCP when customers report "it doesn't work on my phone." The support engineer asks Switchy "what Android versions does Sauce support for Appium 2.5" and gets the platform matrix in-thread, then checks if the customer's device is in the test grid. The Get Supported Platforms and Get Appium EOL tools answer 80% of compatibility questions without switching contexts. The limitation: this MCP doesn't access your actual test results or logs, so it's a reference tool, not a diagnostic one. If your support flow requires pulling crash logs or session videos, you'll need the full Sauce dashboard. For teams fielding 10-30 device-specific tickets per week, this MCP turns a 5-minute Sauce login into a 30-second Switchy query.

CI pipeline health monitoring

When the MCP helps DevOps spot infrastructure issues early

A platform team managing CI for 12 product squads uses this MCP to monitor Sauce Labs uptime and tunnel versions during incident response. When builds start failing, the on-call engineer asks Switchy "is Sauce Labs down" and gets the API status without opening a browser. The Get API Status and Get Tunnel Versions tools surface the two most common culprits: service outages and stale Sauce Connect binaries. This MCP shines for teams where Sauce is one of 8-10 third-party services in the CI chain and the on-call rotation needs fast yes/no answers. It doesn't replace your observability stack—no job logs, no performance traces. If your CI runs 500+ Sauce jobs per day, pair this MCP with a real monitoring tool. For smaller teams where Sauce failures happen once a month, this MCP is the right amount of visibility.

Frequently asked

What does the Sauce Labs MCP do in Switchy?

It pulls test execution data, platform support info, and service status from your Sauce Labs account. Your AI can check which Appium versions are still supported, list recent test jobs, verify API availability, or look up Sauce Connect tunnel versions — without leaving the conversation. Useful for debugging test failures or planning infrastructure upgrades.

Do I need admin access to connect Sauce Labs via OAuth?

No. Any Sauce Labs user can authorize the MCP through OAuth2. The connection inherits your existing account permissions, so if you can view jobs and platform metadata in the Sauce Labs UI, the MCP will surface the same data. Team admins don't need to grant special roles.

Can the Sauce Labs MCP trigger new test runs?

No. It only reads data — job history, platform lists, API status, Appium EOL dates. To start a test, you still use your CI pipeline or the Sauce Labs REST API directly. Think of this MCP as a read-only dashboard for your test infrastructure, not a test runner.

Why use this instead of the Sauce Labs web dashboard?

Speed and context. Your AI can answer "which Appium version expires next month?" or "how many jobs ran yesterday?" inline, without you switching tabs or parsing JSON. The dashboard is better for deep-dive debugging; the MCP is better for quick checks during planning or triage conversations.

Who on the team should connect the Sauce Labs MCP?

Whoever runs or monitors your automated tests — usually a QA engineer or DevOps lead. Since it's read-only, you don't risk accidental config changes. If multiple people need access, each can connect their own Sauce Labs account to their Switchy workspace.

Data last verified 607 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.