Sauce API MCP Server
Sauce Labs testing platform integration for job management and device cloud access.
Data last scanned today · Reviewed today
Overview
This repository provides two distinct MCP servers, sauce-api-mcp and sauce-api-mcp-rdc, to bridge AI assistants with Sauce Labs infrastructure. The core server facilitates account management, tunnel monitoring, and artifact handling, while the RDC server focuses specifically on real device interactions by dynamically generating tools from the official Sauce Labs OpenAPI specification. Designed for testing workflows, the suite allows for browsing device availability, tracking build statuses, and retrieving detailed job logs or performance metrics. It includes response shaping to manage context limits and file operation restrictions to maintain local security during device interactions.
Our verdict
With a security score of 40/100, this tool is categorized as high risk. The rating reflects that it is community-maintained rather than official and lacks an independent editorial review, meaning users should exercise caution regarding its authentication handling and internal API usage. It is best suited for developers building test automation assistants who can monitor its source code and recent updates.
- Uses zero direct dependencies to reduce supply-chain surface
- Auto-updates tool definitions from official OpenAPI specs
- Restricts file operations to specific local directories
- Supports both virtual and real device cloud platforms
- Lacks authentication method and read-only mode security reviews
- Community-maintained project rather than an official vendor release
- No publicly available homepage for configuration guidance
Tools
| Tool | Description | Risk |
|---|---|---|
| get_account_info | Retrieve current user account information | low |
| lookup_users | Find users in your organisation | low |
| get_user | Get detailed user information | low |
| lookup_teams | Find teams in your organisation | low |
| get_team | Get team details | low |
| list_team_members | List all members of a specific team | low |
| lookup_service_accounts | List service accounts | low |
| get_service_account | Get service account details | low |
| get_my_active_team | Get the active team for the authenticated user | low |
| get_devices_status | List all devices and their current status | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›What is the difference between the two included servers?
The core server provides full Sauce Labs API integration for account, build, and tunnel management, while the RDC server focuses specifically on Real Device Cloud capabilities and uses dynamic OpenAPI discovery to stay updated.
›How can I prevent the server from returning too many results and exceeding my LLM's context window?
You can configure the truncation of large API list responses by adjusting the SAUCE_MCP_MAX_RESPONSE_ITEMS environment variable.
›Are there any restrictions on file operations performed through the server?
Yes, file push and pull operations on devices are strictly restricted to the ~/.sauce-mcp/files/ directory to prevent path traversal vulnerabilities.
›What happens if the RDC server cannot connect to the internet during startup?
The RDC server will automatically fall back to using a cached version of the OpenAPI specification if the network is unavailable.
›Do I need to store my Sauce Labs credentials inside the configuration files?
No, while you can add credentials to configuration files, you may alternatively export SAUCE_USERNAME and SAUCE_ACCESS_KEY as environment variables for the servers to automatically detect.
Alternatives
Changelog
Badge
Maintain this server? Add the live badge to your README.