# How to connect Honeycomb to Hermes Agent (no API keys) > Connect Honeycomb to Hermes with ClawLink in one click — 32 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/hermes/honeycomb Most guides for giving Hermes Agent Honeycomb 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 Honeycomb setup: pair once in the browser and your always-on Hermes agent can act on Honeycomb 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 Honeycomb. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Honeycomb** — 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 honeycomb # connect Honeycomb (browser OAuth) npx -y @useclawlink/cli actions honeycomb # list available actions npx -y @useclawlink/cli run honeycomb --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 Honeycomb in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking Hermes: > Use Honeycomb to mcp find columns 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 Honeycomb is connected in the dashboard, that agent calls the same 32 Honeycomb 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). ## Honeycomb MCP for Hermes Looking for a Honeycomb MCP server for Hermes Agent? ClawLink connects Honeycomb to Hermes Agent and exposes 32 Honeycomb 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 Honeycomb integration](https://claw-link.dev/openclaw/honeycomb) works the same way. ## What the Hermes Agent Honeycomb integration can do 32 Honeycomb 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 32. ### 30 of 32 Honeycomb tools for Hermes | Tool | What it does | |---|---| | **Mcp find columns** `honeycomb_mcp_find_columns` | Search for columns and calculated fields by intent across one or all datasets in an environment | | **Mcp find queries** `honeycomb_mcp_find_queries` | Search query history and saved queries by intent; returns matching queries with their run PKs | | **Mcp get aiconversation** `honeycomb_mcp_get_aiconversation` | Fetch the full event timeline for a single AI conversation, identified by its OpenTelemetry | | **Mcp get dataset** `honeycomb_mcp_get_dataset` | Get dataset metadata and its full column schema (columns + calculated fields), sorted by most | | **Mcp get dataset columns** `honeycomb_mcp_get_dataset_columns` | Get the full column schema for one dataset, with optional sample values for specific columns | | **Mcp get environment** `honeycomb_mcp_get_environment` | Get details for a specific environment, including its dataset list sorted by most recent | | **Mcp get query results** `honeycomb_mcp_get_query_results` | Retrieve results and metadata from an existing query execution | | **Mcp get semconv attribute** `honeycomb_mcp_get_semconv_attribute` | Get the full definitions of one or more semantic convention attributes by their exact names | | **Mcp get span details** `honeycomb_mcp_get_span_details` | Summarize attributes and their common values observed on spans with a specific name | | **Mcp get trace** `honeycomb_mcp_get_trace` | Retrieve all spans for a specific trace ID and render them as a waterfall | | **Mcp get triggers** `honeycomb_mcp_get_triggers` | List triggers (alert rules) for the team, or fetch full configuration for a single trigger | | **Mcp get workspace context** `honeycomb_mcp_get_workspace_context` | Call this tool first to orient yourself in a Honeycomb workspace | | **Mcp list aiconversations** `honeycomb_mcp_list_aiconversations` | Discover recent AI agent conversations (gen_ai.conversation.id values) in an environment | | **Mcp list boards** `honeycomb_mcp_list_boards` | List boards (saved dashboards) in an environment, or fetch one board's full contents by ID | | **Mcp list recipients** `honeycomb_mcp_list_recipients` | List all pre-registered notification recipients (email, Slack, PagerDuty, webhook) for the team | | **Mcp list semconv namespaces** `honeycomb_mcp_list_semconv_namespaces` | List the top-level semantic convention namespaces available in this team's registry | | **Mcp list spans** `honeycomb_mcp_list_spans` | List span names in trace data, ranked by count, with how often each is a trace root and which | | **Mcp search semconv** `honeycomb_mcp_search_semconv` | Search the semantic convention registry for attributes matching a query | | **Mcp canvas agent invoke** `honeycomb_mcp_canvas_agent_invoke` | Kick off a single-turn run of the Honeycomb Canvas agent | | **Mcp canvas agent poll response** `honeycomb_mcp_canvas_agent_poll_response` | Poll for the result of a previously-issued canvas_agent_invoke call | | **Mcp create board** `honeycomb_mcp_create_board` | Create a board (dashboard) with query, SLO, and text panels | | **Mcp create marker** `honeycomb_mcp_create_marker` | Creates a marker (a vertical annotation on charts) to mark a point or window in time, such as a | | **Mcp create recipient** `honeycomb_mcp_create_recipient` | Create a notification recipient (email, Slack, PagerDuty, or webhook) so it can be attached to | | **Mcp create slo** `honeycomb_mcp_create_slo` | Create an SLO (Service Level Objective) backed by an auto-created SLI derived column | | **Mcp create trigger** `honeycomb_mcp_create_trigger` | Create a trigger that fires alerts when a query result crosses a threshold | | **Mcp feedback** `honeycomb_mcp_feedback` | Submit feedback about Honeycomb's MCP server to the agentic-intelligence team | | **Mcp refinery docs** `honeycomb_mcp_refinery_docs` | Read Honeycomb Refinery documentation | | **Mcp run bubbleup** `honeycomb_mcp_run_bubbleup` | Run BubbleUp analysis to find what makes a selected data subset different from the baseline | | **Mcp run query** `honeycomb_mcp_run_query` | Run a time-series aggregation query against a Honeycomb dataset and return computed results | | **Mcp update board** `honeycomb_mcp_update_board` | Edit an existing board (dashboard) in place | ## Example prompts **Mcp Find Columns** > Use Honeycomb to mcp find columns and walk me through the result in plain English. **Mcp Find Queries** > Use Honeycomb to mcp find queries and walk me through the result in plain English. **Mcp Get Aiconversation** > Use Honeycomb to mcp get aiconversation and walk me through the result in plain English. **Mcp Get Dataset** > Use Honeycomb to mcp get dataset and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app 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 Honeycomb working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Honeycomb app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Honeycomb through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Honeycomb. | 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 Honeycomb actions to the runtime in a format your agent can reliably use. | 32 tools for Honeycomb are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Honeycomb 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 Honeycomb in the browser, and the 32 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Honeycomb 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 Honeycomb 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 Honeycomb tools Honeycomb 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 Honeycomb 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. ### Honeycomb 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. ### OAuth finished in the browser but the account is still missing Try reconnecting Honeycomb and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a Hermes Agent Honeycomb integration? Yes. ClawLink is the fastest way to connect Hermes to Honeycomb: link your Honeycomb account once in the browser and Hermes Agent can call the Honeycomb API through 32 ready-made tools — no custom code or token handling. ### How do I connect Honeycomb 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 Honeycomb in the dashboard and Hermes can use it from the next message — no config files or API keys to manage. ### How long does it take to connect Honeycomb to Hermes Agent? About two minutes. Sign in, click Connect next to Honeycomb in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Honeycomb up myself? The alternative to ClawLink is usually manual OAuth app 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 Honeycomb working from chat. ### Hermes paired but still can't use Honeycomb 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 - [Hermes GitHub integration](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 tools](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.