Sauce Labs MCP server
Sauce Labs in any MCP client, through Memtro: Sauce Labs does not publish this server. Memtro's Sauce Labs connector reads Sauce Labs through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Sauce Labs cloud testing: a user's recent test jobs (status, pass or fail, browser and platform, build, tags, timing), builds with their passed, failed and errored job counts, the jobs in a build, teams and their concurrency, and concurrency in use. Can rename, tag, re-file or mark a job passed or failed, stop a running job, delete a job, or delete a job's recorded videos, logs and screenshots, each only when asked. Jobs are named by test name and owner; tested URLs, video and log links and access keys are never returned.
Reads
saucelabs_jobsA Sauce Labs user's recent test jobs: id, test name, owner, status, browser and version, platform, command and error counts, when created, visibility.saucelabs_jobOne Sauce Labs test job: test name, owner, status, result (passed, failed, error, complete), browser, OS, framework, build, tags…saucelabs_buildsSauce Labs builds (groups of jobs) the account can see: name, status (running, error, failed, complete, success), job counts (passed, failed…saucelabs_build_jobsThe jobs in one Sauce Labs build, each with its state (running, queued, errored, failed, passed, finished) and created and modified times…saucelabs_teamsSauce Labs teams in the organisation: name, member count, virtual machine and real device concurrency allotted, whether it is the default team.saucelabs_concurrencySauce Labs concurrency: how many Windows and Mac virtual machines and real devices the organisation and the user's team are allowed…
Acts, when you ask
These change something in Sauce Labs. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
saucelabs_update_jobChange a Sauce Labs test job's name, tags, build or pass/fail result.saucelabs_stop_jobStop a running Sauce Labs test job now.saucelabs_delete_jobDelete a Sauce Labs test job and all its assets (video, logs, screenshots) from the test history.saucelabs_delete_job_assetsDelete every recorded asset of a Sauce Labs test job (video, screenshots, logs, HAR, performance data) before Sauce Labs' 30-day purge.
Connect it
First connect Sauce Labs on Dashboard → Connections, then add Memtro to your client once. The Sauce Labs tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Sauce Labs connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Which tests failed in last night's build?
- › How much concurrency is my team using right now?
- › Which builds errored this week?
- › What browser did the checkout test fail on?
- › Mark job 3f9a as passed and tag it flaky
Questions
- Is this an official Sauce Labs MCP server?
- No. It is Memtro's MCP server with Memtro's Sauce Labs connector behind it: the connector reads Sauce Labs through its API with the credentials you connect on Dashboard → Connections, and Sauce Labs publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Sauce Labs?
- Only when you ask, and only what it has been granted: change a test job's name, tags, build or pass/fail result; stop a running test job (it cannot be resumed); delete a test job and all its assets (permanent); delete a test job's videos, logs and screenshots (permanent). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.