# How to connect Honeyhive to Hermes Agent (paste one key, 42 tools) > Connect Honeyhive to Hermes with ClawLink: paste your Honeyhive key once and 42 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/honeyhive Most guides for giving Hermes Agent Honeyhive 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 Honeyhive setup: pair once in the browser and your always-on Hermes agent can act on Honeyhive 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 Honeyhive. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Honeyhive** — 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 honeyhive # connect Honeyhive (browser OAuth) npx -y @useclawlink/cli actions honeyhive # list available actions npx -y @useclawlink/cli run honeyhive --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 Honeyhive in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Honeyhive API key once. Verify the connection by asking Hermes: > Use Honeyhive to compare runs 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 Honeyhive is connected in the dashboard, that agent calls the same 42 Honeyhive 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). ## Honeyhive MCP for Hermes Looking for a Honeyhive MCP server for Hermes Agent? ClawLink connects Honeyhive to Hermes Agent and exposes 42 Honeyhive 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 Honeyhive integration](https://claw-link.dev/openclaw/honeyhive) works the same way. ## What the Hermes Agent Honeyhive integration can do 42 Honeyhive 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 42. ### 30 of 42 Honeyhive tools for Hermes | Tool | What it does | |---|---| | **Compare runs** `honeyhive_compare_runs` | Retrieve experiment comparison between two evaluation runs | | **Compare runs events** `honeyhive_compare_runs_events` | Compare events between two experiment runs side-by-side | | **Get configurations** `honeyhive_get_configurations` | Retrieve a list of configurations | | **Get datasets** `honeyhive_get_datasets` | Retrieve datasets from HoneyHive for a specified project | | **Get events** `honeyhive_get_events` | Query events with filters and projections from HoneyHive | | **Get events by session ID** `honeyhive_get_events_by_session_id` | Retrieve the complete tree of nested events for a specific session | | **Get events chart** `honeyhive_get_events_chart` | Retrieve charting and analytics data for events over time | | **Get metrics** `honeyhive_get_metrics` | Retrieves all metrics associated with a HoneyHive project | | **Get projects** `honeyhive_get_projects` | Retrieve all projects in the HoneyHive account | | **Get run** `honeyhive_get_run` | Get details of an evaluation run by its UUID | | **Get run metrics** `honeyhive_get_run_metrics` | Get event metrics for an experiment run | | **Get runs** `honeyhive_get_runs` | Retrieve a list of evaluation runs from HoneyHive | | **Get runs schema** `honeyhive_get_runs_schema` | Retrieve the schema for experiment runs in HoneyHive | | **Get session** `honeyhive_get_session` | Retrieve a complete session tree by session ID from HoneyHive | | **List tools** `honeyhive_list_tools` | List all available Honeyhive tools | | **Retrieve datapoint** `honeyhive_retrieve_datapoint` | Retrieve a specific datapoint by its ID from HoneyHive | | **Retrieve datapoints** `honeyhive_retrieve_datapoints` | Retrieve datapoints from a HoneyHive project | | **Retrieve events** `honeyhive_retrieve_events` | Retrieve and export events from a HoneyHive project | | **Retrieve experiment result** `honeyhive_retrieve_experiment_result` | Retrieve the result of a specific experiment run | | **Add datapoints to dataset** `honeyhive_add_datapoints_to_dataset` | Add datapoints to a dataset | | **Create batch datapoints** `honeyhive_create_batch_datapoints` | Create multiple datapoints in a single batch operation | | **Create batch model events** `honeyhive_create_batch_model_events` | Create multiple model events in a single request | | **Create batch tool events** `honeyhive_create_batch_tool_events` | Log a batch of external API calls as tool events | | **Create configuration** `honeyhive_create_configuration` | Creates a new configuration in HoneyHive for managing LLM or pipeline settings | | **Create datapoint** `honeyhive_create_datapoint` | Create a new datapoint with input-output pairs | | **Create dataset** `honeyhive_create_dataset` | Create a dataset | | **Create event** `honeyhive_create_event` | Create a new event in HoneyHive to track execution of different parts of your application | | **Create metric** `honeyhive_create_metric` | Create a new metric in HoneyHive | | **Create model event** `honeyhive_create_model_event` | Create a new model event to log LLM call data | | **Create tool** `honeyhive_create_tool` | Creates a new tool definition in a HoneyHive project | ## Example prompts **Compare Runs** > Use Honeyhive to compare runs and walk me through the result in plain English. **Compare Runs Events** > Use Honeyhive to compare runs events and walk me through the result in plain English. **Get Configurations** > Pull the relevant data from Honeyhive, summarize it in plain English, and point out anything that needs attention. **Get Datasets** > Pull the relevant data from Honeyhive, 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 Honeyhive working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Honeyhive API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Honeyhive 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 Honeyhive. | 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 Honeyhive actions to the runtime in a format your agent can reliably use. | 42 tools for Honeyhive are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Honeyhive 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 Honeyhive in the browser, and the 42 tools above work from chat. There is no SDK and no config file, and the Honeyhive 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 Honeyhive 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 Honeyhive 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 Honeyhive tools Honeyhive 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 Honeyhive 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. ### Honeyhive 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 Honeyhive 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 Honeyhive integration? Yes. ClawLink is the fastest way to connect Hermes to Honeyhive: link your Honeyhive account once in the browser and Hermes Agent can call the Honeyhive API through 42 ready-made tools — no custom code or token handling. ### How do I connect Honeyhive 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 Honeyhive in the dashboard and Hermes can use it from the next message — no config files, and the Honeyhive key you paste is stored server-side instead of in your environment. ### How long does it take to connect Honeyhive to Hermes Agent? About two minutes. Sign in, click Connect next to Honeyhive in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Honeyhive 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 Honeyhive working from chat. ### Hermes paired but still can't use Honeyhive 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 - [DataRobot](https://claw-link.dev/hermes/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Chatbotkit](https://claw-link.dev/hermes/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Connect Just One API](https://claw-link.dev/hermes/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.