Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Sauce API MCP

by saucelabsversion 1.0.0i★ –iRuns on your computer
Registry nameio.github.saucelabs-sample-test-frameworks/sauce-api-mcp

Install

Overview

Description from the maker (original English)

An open-source MCP server that provides LLM access to the Sauce Labs API

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 0 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: SAUCE_USERNAME, SAUCE_ACCESS_KEY

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "sauce-api": {
      "command": "uvx",
      "args": [
        "sauce-api-mcp"
      ],
      "env": {
        "SAUCE_USERNAME": "your-value",
        "SAUCE_ACCESS_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add sauce-api --env SAUCE_USERNAME=your-value --env SAUCE_ACCESS_KEY=your-value -- uvx sauce-api-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "sauce-api": {
      "command": "uvx",
      "args": [
        "sauce-api-mcp"
      ],
      "env": {
        "SAUCE_USERNAME": "your-value",
        "SAUCE_ACCESS_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "sauce-api": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "sauce-api-mcp"
      ],
      "env": {
        "SAUCE_USERNAME": "your-value",
        "SAUCE_ACCESS_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • SAUCE_USERNAME env
  • SAUCE_ACCESS_KEY env

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ! Caution

    Maker matches the repo

    The publisher (saucelabs-sample-test-frameworks) is not the repo owner (saucelabs); someone else may have listed it

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 7249 servers in this category
  • Published to the registry more recently than 0% of the other 7249 servers in this category
  • Basic checks equal to or better than 33% of the other 7249 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Sauce API MCP safe?

It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 14 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated today
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago
Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Sauce Labs MCP Server

A Model Context Protocol (MCP) server that provides comprehensive integration with the Sauce Labs testing platform. This package includes two complementary MCP servers enabling AI assistants to interact with Sauce Labs' device cloud, manage test jobs, analyze builds, and monitor testing infrastructure through natural language conversations.

[!TIP]

Prefer a hosted, more feature-rich option? Sauce MCP is the

official MCP server hosted by Sauce Labs at https://mcp.saucelabs.com. There is nothing to install or update, and it

offers a broader tool set than this package, including live real-device control (tap, type, screenshot, app

install/launch), network capture, and AI-powered test case authoring, execution, and scheduling. See

Connect your AI client for setup instructions.

Servers

This package provides two separate MCP servers optimized for different use cases:

sauce-api-mcp (Core Server) — Full Sauce Labs API integration for account management, device discovery, job analysis, builds, storage, and tunnels.

sauce-api-mcp-rdc (RDC Server) — Real Device Cloud (RDC) focused server. Dynamically generates MCP tools at startup from the official Sauce Labs OpenAPI spec using FastMCP with an OpenAPIProvider, so the tool set is always up-to-date without code changes. Includes a small set of handwritten tools for endpoints that need special handling (binary payloads, session lifecycle, app installation polling).

Both servers can be configured simultaneously in your LLM client for full Sauce Labs coverage.

Features

🚀 Core Capabilities
  • Account Management: View account details, team information, and user permissions
  • Device Cloud Access: Browse 300+ real devices (iOS, Android) and virtual machines
  • Test Job Management: Retrieve recent jobs, analyze test results, and debug failures
  • Build Monitoring: Track build status, view job collections, and analyze test suites
  • Storage Management: Manage uploaded apps and test artifacts
  • Tunnel Monitoring: Check Sauce Connect tunnel status and configuration
🔧 Advanced Features
  • Real-time Device Status: Monitor device availability and usage across data centres
  • Cross-platform Testing: Support for both Virtual Device Cloud (VDC) and Real Device Cloud (RDC)
  • Test Analytics: Detailed job information including logs, videos, and performance metrics
  • Team Collaboration: Multi-team support with proper access controls
  • Dynamic RDC API: sauce-api-mcp-rdc auto-discovers the latest RDC v2 endpoints from the OpenAPI spec at startup; the cached spec is used as a fallback when the network is unavailable
  • Response shaping: Large API list responses are automatically truncated to keep LLM context budget under control ( configurable via SAUCE_MCP_MAX_RESPONSE_ITEMS)
  • File safety: File push/pull operations on devices are restricted to ~/.sauce-mcp/files/ to prevent path traversal

Prerequisites

  • Python 3.10+
  • pip
  • Sauce Labs account with API access
  • Claude Desktop, Gemini CLI, Goose, or another MCP-compatible LLM client

Installation

Install the package from PyPI:

pip install sauce-api-mcp

This installs both servers and registers their command-line entry points:

  • sauce-api-mcp — core server
  • sauce-api-mcp-rdc — RDC OpenAPI server

Verify installation:

which sauce-api-mcp

which sauce-api-mcp-rdc

Configuration for LLM Clients

Claude Desktop (Mac / Linux / Windows)
  1. Locate your Claude Desktop config file:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json
  1. Find your Python installation's bin directory:
   python3 -c "import sys; print(sys.prefix + '/bin')"
  1. Add both servers to your config:
   {

"mcpServers": { "sauce-api-mcp-core": { "command": "/path/to/bin/sauce-api-mcp", "env": { "SAUCE_USERNAME": "your-sauce-username", "SAUCE_ACCESS_KEY": "your-sauce-access-key" } }, "sauce-api-mcp-rdc": { "command": "/path/to/bin/sauce-api-mcp-rdc", "env": { "SAUCE_USERNAME": "your-sauce-username", "SAUCE_ACCESS_KEY": "your-sauce-access-key" } } } }

  1. Restart Claude Desktop to load the servers.
Gemini CLI

Add to ~/.gemini/settings.json:

{

"mcpServers": { "sauce-api-mcp-core": { "command": "/path/to/bin/sauce-api-mcp", "env": { "SAUCE_USERNAME": "your-sauce-username", "SAUCE_ACCESS_KEY": "your-sauce-access-key" } }, "sauce-api-mcp-rdc": { "command": "/path/to/bin/sauce-api-mcp-rdc", "env": { "SAUCE_USERNAME": "your-sauce-username", "SAUCE_ACCESS_KEY": "your-sauce-access-key" } } } }

Goose

Add to ~/.config/goose/config.yaml:

sauce-api-mcp-core:

cmd: /path/to/bin/sauce-api-mcp description: Sauce Labs MCP (Core) enabled: true envs: SAUCE_USERNAME: your-sauce-username SAUCE_ACCESS_KEY: your-sauce-access-key type: stdio

sauce-api-mcp-rdc: cmd: /path/to/bin/sauce-api-mcp-rdc description: Sauce Labs MCP (RDC) enabled: true envs: SAUCE_USERNAME: your-sauce-username SAUCE_ACCESS_KEY: your-sauce-access-key type: stdio

Environment Variables (Alternative)

Instead of adding credentials to config files, you can export them as environment variables:

export SAUCE_USERNAME="your-sauce-username"

export SAUCE_ACCESS_KEY="your-sauce-access-key"

Then omit the env block from your config. Both servers will automatically pick them up.

Configuration

Required Environment Variables
VariableDescription
SAUCE_USERNAMEYour Sauce Labs username
SAUCE_ACCESS_KEYYour Sauce Labs access key (found in Account Settings)
Optional Environment Variables
VariableDefaultDescription
SAUCE_REGIONUS_WESTData centre region: US_WEST, US_EAST, EU_CENTRAL
SAUCE_MCP_MAX_RESPONSE_ITEMS100Maximum list items returned before truncation (RDC server)
Getting Your Sauce Labs Credentials
  1. Log into your Sauce Labs account
  2. Navigate to Account → User Settings
  3. Copy your Username and Access Key

Troubleshooting Installation

"Command not found: sauce-api-mcp"

The entry point script isn't in your PATH. Use the full path approach:

python3 -m pip list | grep sauce-api-mcp

python3 -c "import sys; print(sys.prefix + '/bin/sauce-api-mcp')"

"ENOENT: no such file or directory" in MCP client

The MCP client is using a different Python environment. Solutions:

  1. Use the full absolute path (recommended) — update your config with the path printed by python3 -c "import sys; print(sys.prefix + '/bin/sauce-api-mcp')", not just which sauce-api-mcp
  2. Module invocation (fallback):
   "command": "python3",

"args": ["-m", "sauce_api_mcp.main"]

Example Prompts

  • *"Show me my recent test failures"*
  • *"Find available iPhone 16 devices"*
  • *"Analyse the performance of my latest build"*
  • *"Open a session on a Samsung device and install my app"*
  • *"What tunnels do I have running right now?"*

Available Tools

Core Server (sauce-api-mcp)
Account & Organisation
ToolDescription
get_account_infoRetrieve current user account information
lookup_usersFind users in your organisation
get_userGet detailed user information
lookup_teamsFind teams in your organisation
get_teamGet team details
list_team_membersList all members of a specific team
lookup_service_accountsList service accounts
get_service_accountGet service account details
get_my_active_teamGet the active team for the authenticated user
Device Management
ToolDescription
get_devices_statusList all devices and their current status
get_specific_deviceGet detailed information about a specific device
get_private_devicesList private devices available to your account
Test Jobs
ToolDescription
get_recent_jobsRetrieve your most recent test jobs
get_job_detailsGet comprehensive details about a specific job
get_real_device_jobsList active jobs on real devices
get_specific_real_device_jobGet details about a specific real device job
get_specific_real_device_job_assetDownload job assets (logs, videos, screenshots)
Builds
ToolDescription
lookup_buildsSearch for builds with filters
get_buildGet detailed information about a specific build
get_build_for_jobGet the build associated with a job
lookup_jobs_in_buildList all jobs within a build
Storage
ToolDescription
get_storage_filesList uploaded application files
get_storage_groupsList app storage groups
get_storage_groups_settingsGet settings for a storage group
upload_file_to_storageUpload an app file to Sauce Storage
update_storage_group_settingsUpdate app group settings (resigning, instrumentation, etc.)
Tunnels
ToolDescription
get_tunnels_for_userList active Sauce Connect tunnels
get_tunnel_informationGet details about a specific tunnel
get_current_jobs_for_tunnelSee how many jobs are using a tunnel
get_tunnel_version_downloadsGet download URLs for Sauce Connect versions
Test Assets & Logs
ToolDescription

| get_test_assets | Retrieve test artifacts for a VDC job

Only the beginning is shown; read the rest in the repo

Ask PopNx