How to connect Buildkite to Hermes Agent
Connect Buildkite to Hermes with ClawLink: paste your Buildkite key once and 5 tools work from chat. No MCP server to run, nothing stored on your machine.
BuildkiteAPI KEYMCPBuildkite is a platform for running fast, secure, and scalable continuous integration pipelines on your own infrastructure.. Once connected, Hermes Agent can read and act on Buildkite from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Buildkite 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 Buildkite setup: pair once in the browser and your always-on Hermes agent can act on Buildkite 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 Buildkite.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Buildkite
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Buildkite?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
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 testThen connect Buildkite in the ClawLink dashboard — paste your Buildkite API key once.
Verify the connection by asking Hermes:
Pull the relevant data from Buildkite, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Buildkite is connected in the dashboard, that agent calls the same 5 Buildkite tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Buildkite MCP for Hermes
Looking for a Buildkite MCP server for Hermes Agent? ClawLink connects Buildkite to Hermes Agent and exposes 5 Buildkite tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Buildkite integration works the same way.
What the Hermes Agent Buildkite integration can do
5 Buildkite tools are ready for Hermes Agent once the account is connected.
All 5 Buildkite tools for Hermes
| Tool | What it does |
|---|---|
Get current access token buildkite_get_current_access_token | Retrieve the authenticated API access token details |
Get meta buildkite_get_meta | Retrieve metadata about the Buildkite API |
Get user buildkite_get_user | Retrieve details about the current authenticated user |
List organizations buildkite_list_organizations | List all organizations the current user is a member of |
List pipeline agents buildkite_list_pipeline_agents | List connected agents for an organization |
Try it: find the Buildkite tool you need
Browse the 5 Buildkite tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Buildkite, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Buildkite, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Buildkite, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Buildkite, group them by priority, and recommend what Hermes should do next.
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 Buildkite working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Buildkite API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Buildkite 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 Buildkite. | 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 Buildkite actions to the runtime in a format your agent can reliably use. | 5 tools for Buildkite are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Buildkite 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 Buildkite in the browser, and the 5 tools above work from chat. There is no SDK and no config file, and the Buildkite key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
Hermes paired but still can't use Buildkite
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 Buildkite 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 Buildkite tools
Buildkite 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 Buildkite 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.
Buildkite 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 Buildkite has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a Hermes Agent Buildkite integration?
Yes. ClawLink is the fastest way to connect Hermes to Buildkite: link your Buildkite account once in the browser and Hermes Agent can call the Buildkite API through 5 ready-made tools — no custom code or token handling.
How do I connect Buildkite 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 Buildkite in the dashboard and Hermes can use it from the next message — no config files, and the Buildkite key you paste is stored server-side instead of in your environment.
How long does it take to connect Buildkite to Hermes Agent?
About two minutes. Sign in, click Connect next to Buildkite in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Buildkite 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 Buildkite working from chat.
Hermes paired but still can't use Buildkite
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
Manage repositories, issues, pull requests, and workflows
Hermes PagerDuty integration
Manage incidents, on-call schedules, and services
Hermes SafetyCulture integration
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.