# How to connect Hex to Hermes Agent (paste one key, 32 tools) > Connect Hex to Hermes with ClawLink: paste your Hex key once and 32 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/hex Most guides for giving Hermes Agent Hex 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 Hex setup: pair once in the browser and your always-on Hermes agent can act on Hex 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 Hex. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Hex** — 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 hex # connect Hex (browser OAuth) npx -y @useclawlink/cli actions hex # list available actions npx -y @useclawlink/cli run hex --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 Hex in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Hex API key once. Verify the connection by asking Hermes: > Pull the relevant data from Hex, 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 Hex is connected in the dashboard, that agent calls the same 32 Hex 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). ## Hex MCP for Hermes Looking for a Hex MCP server for Hermes Agent? ClawLink connects Hex to Hermes Agent and exposes 32 Hex 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 Hex integration](https://claw-link.dev/openclaw/hex) works the same way. ## What the Hermes Agent Hex integration can do 32 Hex tools are ready for Hermes Agent once the account is connected. The 29 below are the ones people reach for most; your agent can call all 32. ### 29 of 32 Hex tools for Hermes | Tool | What it does | |---|---| | **Get cell** `hex_get_cell` | Get a single cell by ID from the draft version of a Hex project | | **Get collection** `hex_get_collection` | Get information about a specific collection in Hex | | **Get group** `hex_get_group` | Retrieve information about a specific Hex group | | **Get project** `hex_get_project` | Get metadata about a single Hex project | | **Get project runs** `hex_get_project_runs` | Retrieve the status of API-triggered runs for a specific Hex project | | **Get run chart image** `hex_get_run_chart_image` | Retrieve a rendered chart image from a Hex project run | | **Get run status** `hex_get_run_status` | Retrieve the status of a specific Hex project run | | **List cells** `hex_list_cells` | List all cells from the draft version of a Hex project | | **List collections** `hex_list_collections` | Retrieve all collections in the workspace with pagination support | | **List data connections** `hex_list_data_connections` | List all data connections in the Hex workspace with pagination support | | **List groups** `hex_list_groups` | List all groups in the Hex workspace with pagination support | | **List projects** `hex_list_projects` | List all viewable Hex projects with pagination and filtering support | | **List users** `hex_list_users` | List all users in the Hex workspace with pagination support | | **Create cell** `hex_create_cell` | Create a new cell in the draft version of a Hex project | | **Create collection** `hex_create_collection` | Create a new collection in the Hex workspace | | **Create group** `hex_create_group` | Create a new group in the Hex workspace | | **Deactivate user** `hex_deactivate_user` | Deactivates a user in the Hex workspace | | **Edit collection** `hex_edit_collection` | Edit a collection's name, description, and sharing settings in Hex | | **Edit group** `hex_edit_group` | Edit a group's name and/or members in Hex | | **Edit project sharing collections** `hex_edit_project_sharing_collections` | Add a project to collections or remove it from collections | | **Edit project sharing groups** `hex_edit_project_sharing_groups` | Edit project sharing settings for groups in Hex | | **Edit project sharing org and public** `hex_edit_project_sharing_org_and_public` | Edit project sharing settings for workspace members and public web access | | **Edit project sharing users** `hex_edit_project_sharing_users` | Edit project sharing settings for individual users in Hex | | **Publish guide drafts** `hex_publish_guide_drafts` | Publish all currently drafted guides or specific guides by ID | | **Run project** `hex_run_project` | Trigger a run of the latest published version of a Hex project | | **Update cell** `hex_update_cell` | Update a cell's source code and/or data connection in Hex | | **Update project** `hex_update_project` | Add or remove a status (including endorsements) from a Hex project | | **Upsert guide draft** `hex_upsert_guide_draft` | Update or create guide drafts by filePath | | **Cancel run** `hex_cancel_run` | Cancel a project run that is in progress | ## Example prompts **Get Cell** > Pull the relevant data from Hex, summarize it in plain English, and point out anything that needs attention. **Get Collection** > Pull the relevant data from Hex, summarize it in plain English, and point out anything that needs attention. **Get Group** > Pull the relevant data from Hex, summarize it in plain English, and point out anything that needs attention. **Get Project** > Pull the relevant data from Hex, 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 Hex working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Hex API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Hex 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 Hex. | 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 Hex actions to the runtime in a format your agent can reliably use. | 32 tools for Hex are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Hex 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 Hex in the browser, and the 32 tools above work from chat. There is no SDK and no config file, and the Hex 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 Hex 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 Hex 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 Hex tools Hex 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 Hex 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. ### Hex 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 Hex 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 Hex integration? Yes. ClawLink is the fastest way to connect Hermes to Hex: link your Hex account once in the browser and Hermes Agent can call the Hex API through 32 ready-made tools — no custom code or token handling. ### How do I connect Hex 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 Hex in the dashboard and Hermes can use it from the next message — no config files, and the Hex key you paste is stored server-side instead of in your environment. ### How long does it take to connect Hex to Hermes Agent? About two minutes. Sign in, click Connect next to Hex in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Hex 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 Hex working from chat. ### Hermes paired but still can't use Hex 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 PostHog](https://claw-link.dev/hermes/posthog) — Track user behavior and feature flags - [DataforSEO tools](https://claw-link.dev/hermes/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Hermes Metabase integration](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.