Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
An open-source MCP server that provides LLM access to the Sauce Labs API
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
SAUCE_USERNAME, SAUCE_ACCESS_KEYYou need
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-mcpFill in the empty values before running it.
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.
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.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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
The publisher (saucelabs-sample-test-frameworks) is not the repo owner (saucelabs); someone else may have listed it
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 14 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Context7, Codebase Memory, Exa
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
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
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.
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.
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.
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 unavailableSAUCE_MCP_MAX_RESPONSE_ITEMS)~/.sauce-mcp/files/ to prevent path traversalpipInstall the package from PyPI:
pip install sauce-api-mcp
This installs both servers and registers their command-line entry points:
sauce-api-mcp — core serversauce-api-mcp-rdc — RDC OpenAPI serverVerify installation:
which sauce-api-mcp
which sauce-api-mcp-rdc
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.jsonbin directory: python3 -c "import sys; print(sys.prefix + '/bin')"
{
"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" } } } }
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" } } } }
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
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.
| Variable | Description |
|---|---|
SAUCE_USERNAME | Your Sauce Labs username |
SAUCE_ACCESS_KEY | Your Sauce Labs access key (found in Account Settings) |
| Variable | Default | Description |
|---|---|---|
SAUCE_REGION | US_WEST | Data centre region: US_WEST, US_EAST, EU_CENTRAL |
SAUCE_MCP_MAX_RESPONSE_ITEMS | 100 | Maximum list items returned before truncation (RDC server) |
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')"
The MCP client is using a different Python environment. Solutions:
python3 -c "import sys; print(sys.prefix + '/bin/sauce-api-mcp')", not just which sauce-api-mcp "command": "python3",
"args": ["-m", "sauce_api_mcp.main"]
sauce-api-mcp)| Tool | Description |
|---|---|
get_account_info | Retrieve current user account information |
lookup_users | Find users in your organisation |
get_user | Get detailed user information |
lookup_teams | Find teams in your organisation |
get_team | Get team details |
list_team_members | List all members of a specific team |
lookup_service_accounts | List service accounts |
get_service_account | Get service account details |
get_my_active_team | Get the active team for the authenticated user |
| Tool | Description |
|---|---|
get_devices_status | List all devices and their current status |
get_specific_device | Get detailed information about a specific device |
get_private_devices | List private devices available to your account |
| Tool | Description |
|---|---|
get_recent_jobs | Retrieve your most recent test jobs |
get_job_details | Get comprehensive details about a specific job |
get_real_device_jobs | List active jobs on real devices |
get_specific_real_device_job | Get details about a specific real device job |
get_specific_real_device_job_asset | Download job assets (logs, videos, screenshots) |
| Tool | Description |
|---|---|
lookup_builds | Search for builds with filters |
get_build | Get detailed information about a specific build |
get_build_for_job | Get the build associated with a job |
lookup_jobs_in_build | List all jobs within a build |
| Tool | Description |
|---|---|
get_storage_files | List uploaded application files |
get_storage_groups | List app storage groups |
get_storage_groups_settings | Get settings for a storage group |
upload_file_to_storage | Upload an app file to Sauce Storage |
update_storage_group_settings | Update app group settings (resigning, instrumentation, etc.) |
| Tool | Description |
|---|---|
get_tunnels_for_user | List active Sauce Connect tunnels |
get_tunnel_information | Get details about a specific tunnel |
get_current_jobs_for_tunnel | See how many jobs are using a tunnel |
get_tunnel_version_downloads | Get download URLs for Sauce Connect versions |
| Tool | Description |
|---|
| get_test_assets | Retrieve test artifacts for a VDC job
Only the beginning is shown; read the rest in the repo