# How to connect Here to Hermes Agent (paste one key, 98 tools) > Connect Here to Hermes with ClawLink: paste your Here key once and 98 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/here Most guides for giving Hermes Agent Here 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 Here setup: pair once in the browser and your always-on Hermes agent can act on Here 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 Here. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Here** — 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 here # connect Here (browser OAuth) npx -y @useclawlink/cli actions here # list available actions npx -y @useclawlink/cli run here --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 Here in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Here API key once. Verify the connection by asking Hermes: > Use Here to autosuggest 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 Here is connected in the dashboard, that agent calls the same 98 Here 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). ## Here MCP for Hermes Looking for a Here MCP server for Hermes Agent? ClawLink connects Here to Hermes Agent and exposes 98 Here 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 Here integration](https://claw-link.dev/openclaw/here) works the same way. ## What the Hermes Agent Here integration can do 98 Here 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 98. ### 30 of 98 Here tools for Hermes | Tool | What it does | |---|---| | **Autosuggest** `here_autosuggest` | Fetch possible completions for a partial search term | | **Browse** `here_browse` | Search for places around a given location with optional filters | | **Calculate route** `here_calculate_route` | Calculate optimal routes between multiple waypoints supporting various transport modes (car, truck, bicycle, pedestrian) | | **Cancel problem** `here_cancel_problem` | Cancel a running asynchronous tour planning optimization job | | **Coordinates to tile indices** `here_coordinates_to_tile_indices` | Convert geographic coordinates to Web Mercator XYZ tile indices | | **Decode route handle** `here_decode_route_handle` | Decode and return a route from a previously calculated route handle via POST request | | **Discover** `here_discover` | Discover places and addresses by free-form text near a location | | **Find sequence** `here_find_sequence` | Solve a Vehicle Routing Problem (VRP) by optimizing routes for a fleet of vehicles serving multiple jobs | | **Find waypoint sequence** `here_find_waypoint_sequence` | Find the optimal sequence of waypoints using POST request to solve the Travelling Salesman Problem | | **Submit tour planning problem** `here_submit_tour_planning_problem` | Submit a tour planning problem synchronously to solve vehicle routing problems with constraints | | **Submit tour planning problem async** `here_submit_tour_planning_problem_async` | Submit a tour planning problem asynchronously for large-scale vehicle routing optimization | | **Geocode** `here_geocode` | Convert structured address data into geographic coordinates | | **Get aliases health** `here_get_aliases_health` | Check the health status of the HERE Tracking aliases service | | **Get aliases version** `here_get_aliases_version` | Get the current version of the HERE Tracking Aliases service | | **Get associations health** `here_get_associations_health` | Check the health status of the HERE Tracking Associations API service | | **Get associations version** `here_get_associations_version` | Retrieve the current version of the HERE Associations tracking service | | **Get autocomplete** `here_get_autocomplete` | Get address autocomplete suggestions for partial address queries | | **Get base map tile** `here_get_base_map_tile` | Retrieves a base map tile image from HERE Raster Tile API v3 | | **Get bulkjobs health** `here_get_bulkjobs_health` | Check the health status of the HERE Tracking bulkjobs service | | **Get bulkjobs version** `here_get_bulkjobs_version` | Retrieve the current version of the HERE Bulkjobs tracking service | | **Get c2 c health** `here_get_c2_c_health` | Check HERE C2C service health status | | **Get c2 c version** `here_get_c2_c_version` | Get the current version of the HERE C2C tracking service | | **Get copyright** `here_get_copyright` | Retrieve copyright information for HERE map tiles | | **Get departures** `here_get_departures` | Get next departures from transit stations | | **Get events health** `here_get_events_health` | Check the health status of the HERE Events API service | | **Get events version** `here_get_events_version` | Get the current version of the HERE Events service | | **Get features** `here_get_features` | Retrieve available map features per style for tile rendering | | **Get geofences health** `here_get_geofences_health` | Check the health status of the HERE Geofences service | | **Get geofences version** `here_get_geofences_version` | Get the current version of the HERE Geofences service | | **Get health** `here_get_health` | Check the health status of the HERE Tracking API service | ## Example prompts **Autosuggest** > Use Here to autosuggest and walk me through the result in plain English. **Browse** > Use Here to browse and walk me through the result in plain English. **Calculate Route** > Use Here to calculate route and walk me through the result in plain English. **Cancel Problem** > Use Here to cancel problem and walk me through the result in plain English. ## 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 Here working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Here API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Here 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 Here. | 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 Here actions to the runtime in a format your agent can reliably use. | 98 tools for Here are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Here 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 Here in the browser, and the 98 tools above work from chat. There is no SDK and no config file, and the Here 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 Here 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 Here 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 Here tools Here 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 Here 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. ### Here 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 Here 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 Here integration? Yes. ClawLink is the fastest way to connect Hermes to Here: link your Here account once in the browser and Hermes Agent can call the Here API through 98 ready-made tools — no custom code or token handling. ### How do I connect Here 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 Here in the dashboard and Hermes can use it from the next message — no config files, and the Here key you paste is stored server-side instead of in your environment. ### How long does it take to connect Here to Hermes Agent? About two minutes. Sign in, click Connect next to Here in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Here 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 Here working from chat. ### Hermes paired but still can't use Here 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](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.