# How to connect Better Stack to Hermes Agent (paste one key, 117 tools) > Connect Better Stack to Hermes with ClawLink: paste your Better Stack key once and 117 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/better-stack Most guides for giving Hermes Agent Better Stack 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 Better Stack setup: pair once in the browser and your always-on Hermes agent can act on Better Stack for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. **Start here — 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. ## Setup It takes three steps to connect Hermes to Better Stack. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Better Stack** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **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 better-stack # connect Better Stack (browser OAuth) npx -y @useclawlink/cli actions better-stack # list available actions npx -y @useclawlink/cli run better-stack --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 Better Stack in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Better Stack API key once. Verify the connection by asking Hermes: > Use Better Stack to acknowledge incident and walk me through the result in plain English. ### 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 Better Stack is connected in the dashboard, that agent calls the same 117 Better Stack 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). ## Better Stack MCP for Hermes Looking for a Better Stack MCP server for Hermes Agent? ClawLink connects Better Stack to Hermes Agent and exposes 117 Better Stack 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 Better Stack integration](https://claw-link.dev/openclaw/better-stack) works the same way. ## What the Hermes Agent Better Stack integration can do 117 Better Stack tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 117. ### 30 of 117 Better Stack tools for Hermes | Tool | What it does | |---|---| | **Acknowledge incident** `better_stack_acknowledge_incident` | Acknowledge an ongoing incident | | **Create escalation policy** `better_stack_create_escalation_policy` | Creates a new escalation policy for incident management | | **Create heartbeat** `better_stack_create_heartbeat` | Create a new heartbeat monitor for cron jobs and scheduled tasks | | **Create heartbeat group** `better_stack_create_heartbeat_group` | Create a new heartbeat group | | **Get escalation policy** `better_stack_get_escalation_policy` | Get a single escalation policy by its ID | | **Get heartbeat** `better_stack_get_heartbeat` | Get a single heartbeat by ID | | **Get heartbeat availability** `better_stack_get_heartbeat_availability` | Retrieve availability summary for a specific heartbeat | | **Get heartbeat group** `better_stack_get_heartbeat_group` | Get a single heartbeat group by ID | | **Get incident comment** `better_stack_get_incident_comment` | Get a single comment from an incident | | **Get monitor** `better_stack_get_monitor` | Get a single monitor. Use when you need full details of a specific monitor by its ID. | | **Get monitor availability** `better_stack_get_monitor_availability` | Return an availability summary for a specific monitor | | **Get monitor groups** `better_stack_get_monitor_groups` | Get a single monitor group by ID | | **Get monitor groups monitors** `better_stack_get_monitor_groups_monitors` | Get all monitors belonging to a monitor group | | **Get monitor response times** `better_stack_get_monitor_response_times` | Retrieves response time performance metrics for a specific uptime monitor | | **Get on call schedule** `better_stack_get_on_call_schedule` | Get a single on-call schedule by ID | | **Get outgoing webhook** `better_stack_get_outgoing_webhook` | Get a single outgoing webhook integration by ID | | **Get policy group** `better_stack_get_policy_group` | Get a single escalation policy group | | **Get status page** `better_stack_get_status_page` | Get a single status page by ID | | **Get status page group** `better_stack_get_status_page_group` | Get a single status page group by ID | | **Get status page report** `better_stack_get_status_page_report` | Get a single status page report by ID | | **Get status page resource** `better_stack_get_status_page_resource` | Get a single status page resource by ID | | **Get status page section** `better_stack_get_status_page_section` | Get a single status page section | | **Get status update** `better_stack_get_status_update` | Get a single status update by its ID | | **Get uptime API token** `better_stack_get_uptime_api_token` | Retrieve the configured Uptime API token | | **Get urgency** `better_stack_get_urgency` | Get a single severity level (urgency) by ID | | **Get urgency group** `better_stack_get_urgency_group` | Get a single urgency group (severity group) by ID | | **List aws cloudwatch integrations** `better_stack_list_aws_cloudwatch_integrations` | List all AWS CloudWatch integrations | | **List azure integrations** `better_stack_list_azure_integrations` | List all Azure integrations | | **List catalog relations** `better_stack_list_catalog_relations` | List all catalog relations | | **List datadog integrations** `better_stack_list_datadog_integrations` | List all Datadog integrations | ## Example prompts **Acknowledge Incident** > Use Better Stack to acknowledge incident and walk me through the result in plain English. **Create Escalation Policy** > Create it in Better Stack for me, then confirm the important fields before you finish. **Create Heartbeat** > Create it in Better Stack for me, then confirm the important fields before you finish. **Create Heartbeat Group** > Create it in Better Stack for me, then confirm the important fields before you finish. ## 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 Better Stack working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Better Stack API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Better Stack 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 Better Stack. | 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 Better Stack actions to the runtime in a format your agent can reliably use. | 117 tools for Better Stack are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Better Stack 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 Better Stack in the browser, and the 117 tools above work from chat. There is no SDK and no config file, and the Better Stack 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 Better Stack 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 Better Stack 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 Better Stack tools Better Stack 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 Better Stack 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. ### Better Stack 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 Better Stack 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 Better Stack integration? Yes. ClawLink is the fastest way to connect Hermes to Better Stack: link your Better Stack account once in the browser and Hermes Agent can call the Better Stack API through 117 ready-made tools — no custom code or token handling. ### How do I connect Better Stack 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 Better Stack in the dashboard and Hermes can use it from the next message — no config files, and the Better Stack key you paste is stored server-side instead of in your environment. ### How long does it take to connect Better Stack to Hermes Agent? About two minutes. Sign in, click Connect next to Better Stack in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Better Stack 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 Better Stack working from chat. ### Hermes paired but still can't use Better Stack 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 - [Connect GitHub](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](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.