# How to connect Seqera to Hermes Agent (paste one key, 14 tools) > Connect Seqera to Hermes with ClawLink: paste your Seqera key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/seqera Most guides for giving Hermes Agent Seqera 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 Seqera setup: pair once in the browser and your always-on Hermes agent can act on Seqera 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 Seqera. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Seqera** — 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 seqera # connect Seqera (browser OAuth) npx -y @useclawlink/cli actions seqera # list available actions npx -y @useclawlink/cli run seqera --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 Seqera in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Seqera API key once. Verify the connection by asking Hermes: > Pull the relevant data from Seqera, 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 Seqera is connected in the dashboard, that agent calls the same 14 Seqera 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). ## Seqera MCP for Hermes Looking for a Seqera MCP server for Hermes Agent? ClawLink connects Seqera to Hermes Agent and exposes 14 Seqera 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 Seqera integration](https://claw-link.dev/openclaw/seqera) works the same way. ## What the Hermes Agent Seqera integration can do 14 Seqera tools are ready for Hermes Agent once the account is connected. ### All 14 Seqera tools for Hermes | Tool | What it does | |---|---| | **Get organization details** `seqera_get_organization_details` | Retrieve detailed information about a specific organization | | **Get service info** `seqera_get_service_info` | Retrieve information about the Seqera API service | | **Get user info** `seqera_get_user_info` | Retrieve information about the authenticated user | | **Get wave build logs** `seqera_get_wave_build_logs` | Get logs for a container build by build ID | | **Get wave build status** `seqera_get_wave_build_status` | Retrieve the status of a Wave container build by build ID | | **Inspect wave container** `seqera_inspect_wave_container` | Inspect container image metadata via Wave | | **List action event types** `seqera_list_action_event_types` | List supported action event types | | **List compute environments** `seqera_list_compute_environments` | Retrieve a list of compute environments | | **List organizations** `seqera_list_organizations` | List all organizations | | **List pipelines** `seqera_list_pipelines` | List all pipelines accessible to the authenticated user | | **List workflows** `seqera_list_workflows` | List workflows | | **Validate action name** `seqera_validate_action_name` | Validate action name | | **Validate pipeline name** `seqera_validate_pipeline_name` | Validate a pipeline name | | **Create wave container** `seqera_create_wave_container` | Submit a request to Wave for accessing a private container registry or building a container | ## Example prompts **Get Organization Details** > Pull the relevant data from Seqera, summarize it in plain English, and point out anything that needs attention. **Get Service Info** > Pull the relevant data from Seqera, summarize it in plain English, and point out anything that needs attention. **Get User Info** > Pull the relevant data from Seqera, summarize it in plain English, and point out anything that needs attention. **Get Wave Build Logs** > Pull the relevant data from Seqera, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key 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 Seqera working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Seqera API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Seqera account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Seqera. | 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 Seqera actions to the runtime in a format your agent can reliably use. | 14 tools for Seqera are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Seqera 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 Seqera in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the Seqera 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 Seqera 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 Seqera 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 Seqera tools Seqera 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 Seqera 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. ### Seqera 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. ### API key setup works but results look incomplete Double-check that the API key for Seqera has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Hermes Agent Seqera integration? Yes. ClawLink is the fastest way to connect Hermes to Seqera: link your Seqera account once in the browser and Hermes Agent can call the Seqera API through 14 ready-made tools — no custom code or token handling. ### How do I connect Seqera 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 Seqera in the dashboard and Hermes can use it from the next message — no config files, and the Seqera key you paste is stored server-side instead of in your environment. ### How long does it take to connect Seqera to Hermes Agent? About two minutes. Sign in, click Connect next to Seqera in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Seqera up myself? The alternative to ClawLink is usually manual API key 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 Seqera working from chat. ### Hermes paired but still can't use Seqera 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 - [PostHog](https://claw-link.dev/hermes/posthog) — Track user behavior and feature flags - [DataforSEO](https://claw-link.dev/hermes/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Metabase](https://claw-link.dev/hermes/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.