# How to connect Saucelabs to Hermes Agent (paste one key, 6 tools) > Connect Saucelabs to Hermes with ClawLink: paste your Saucelabs key once and 6 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/saucelabs Most guides for giving Hermes Agent Saucelabs access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Saucelabs setup: pair once in the browser and your always-on Hermes agent can act on Saucelabs for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to Saucelabs. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Saucelabs** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect saucelabs # connect Saucelabs (browser OAuth) npx -y @useclawlink/cli actions saucelabs # list available actions npx -y @useclawlink/cli run saucelabs --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect Saucelabs in the [ClawLink dashboard](https://claw-link.dev/dashboard) — enter your Saucelabs account details once. Verify the connection by asking Hermes: > Pull the relevant data from Saucelabs, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Saucelabs is connected in the dashboard, that agent calls the same 6 Saucelabs tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Saucelabs MCP for Hermes Looking for a Saucelabs MCP server for Hermes Agent? ClawLink connects Saucelabs to Hermes Agent and exposes 6 Saucelabs tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Saucelabs integration](https://claw-link.dev/openclaw/saucelabs) works the same way. ## What the Hermes Agent Saucelabs integration can do 6 Saucelabs tools are ready for Hermes Agent once the account is connected. ### All 6 Saucelabs tools for Hermes | Tool | What it does | |---|---| | **Get API definition** `saucelabs_get_api_definition` | Retrieve the OpenAPI/Swagger JSON documentation for the Sauce Labs Performance API | | **Get API status** `saucelabs_get_api_status` | Retrieve the current operational status of Sauce Labs services | | **Get appium eol** `saucelabs_get_appium_eol` | Retrieve end-of-life information for Appium versions | | **Get platforms** `saucelabs_get_platforms` | Get supported platforms for an automation API | | **Get tunnel versions** `saucelabs_get_tunnel_versions` | Retrieve information about available Sauce Connect tunnel versions | | **List jobs** `saucelabs_list_jobs` | Retrieve all jobs for a SauceLabs user | ## Example prompts **Get Api Definition** > Pull the relevant data from Saucelabs, summarize it in plain English, and point out anything that needs attention. **Get Api Status** > Pull the relevant data from Saucelabs, summarize it in plain English, and point out anything that needs attention. **Get Appium Eol** > Pull the relevant data from Saucelabs, summarize it in plain English, and point out anything that needs attention. **Get Platforms** > Pull the relevant data from Saucelabs, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual credential setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Saucelabs working from chat. | | Manual | ClawLink | |---|---|---| | **Setup flow** | Collect and store the right Saucelabs credentials yourself, then keep the account mapping and request format correct. | ClawLink keeps the setup in one hosted flow so non-technical users can link Saucelabs without custom integration screens. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Saucelabs. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Saucelabs actions to the runtime in a format your agent can reliably use. | 6 tools for Saucelabs are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Saucelabs to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect Saucelabs in the browser, and the 6 tools above work from chat. There is no SDK and no config file, and the Saucelabs key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Saucelabs Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### Connection succeeds but no tools appear Reconnect Saucelabs from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Saucelabs tools Saucelabs tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Saucelabs call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Saucelabs returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### The setup form accepts credentials but calls still fail Re-enter the credentials carefully and verify the account-level permissions for Saucelabs. Basic and token-based integrations tend to fail on formatting mistakes or limited account roles. ### Is there a Hermes Agent Saucelabs integration? Yes. ClawLink is the fastest way to connect Hermes to Saucelabs: link your Saucelabs account once in the browser and Hermes Agent can call the Saucelabs API through 6 ready-made tools — no custom code or token handling. ### How do I connect Saucelabs to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Saucelabs in the dashboard and Hermes can use it from the next message — no config files, and the Saucelabs key you paste is stored server-side instead of in your environment. ### How long does it take to connect Saucelabs to Hermes Agent? About two minutes. Sign in, click Connect next to Saucelabs in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Saucelabs up myself? The alternative to ClawLink is usually manual credential setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Saucelabs working from chat. ### Hermes paired but still can't use Saucelabs Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [GitHub tools](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [Hermes PagerDuty integration](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/hermes/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.