# How to connect Grafbase to Hermes Agent (paste one key, 28 tools) > Connect Grafbase to Hermes with ClawLink: paste your Grafbase key once and 28 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/grafbase Most guides for giving Hermes Agent Grafbase 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 Grafbase setup: pair once in the browser and your always-on Hermes agent can act on Grafbase 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 Grafbase. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Grafbase** — 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 grafbase # connect Grafbase (browser OAuth) npx -y @useclawlink/cli actions grafbase # list available actions npx -y @useclawlink/cli run grafbase --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 Grafbase in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Grafbase API key once. Verify the connection by asking Hermes: > Pull the relevant data from Grafbase, 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 Grafbase is connected in the dashboard, that agent calls the same 28 Grafbase 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). ## Grafbase MCP for Hermes Looking for a Grafbase MCP server for Hermes Agent? ClawLink connects Grafbase to Hermes Agent and exposes 28 Grafbase 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 Grafbase integration](https://claw-link.dev/openclaw/grafbase) works the same way. ## What the Hermes Agent Grafbase integration can do 28 Grafbase tools are ready for Hermes Agent once the account is connected. The 21 below are the ones people reach for most; your agent can call all 28. ### 21 of 28 Grafbase tools for Hermes | Tool | What it does | |---|---| | **Get audit log** `grafbase_get_audit_log` | Retrieve a specific Grafbase audit log entry by searching organization activity | | **Get extension by name** `grafbase_get_extension_by_name` | Retrieve a Grafbase extension by its name | | **Get extension version by name and version** `grafbase_get_extension_version_by_name_and_version` | Retrieve details of a specific Grafbase extension version by name and version | | **Get federated schema** `grafbase_get_federated_schema` | Retrieves the composed federated graph schema from Grafbase in SDL format | | **Get invitation** `grafbase_get_invitation` | Retrieve details about a specific Grafbase invitation by ID | | **Get notifications inbox messages** `grafbase_get_notifications_inbox_messages` | Retrieve notifications inbox messages for the authenticated Grafbase user | | **Get schema check** `grafbase_get_schema_check` | Retrieve details of a specific schema check by its ID | | **Get subgraph schema** `grafbase_get_subgraph_schema` | Retrieves the GraphQL SDL schema for a specific subgraph by name | | **List API keys** `grafbase_list_api_keys` | List all API keys (access tokens) for the authenticated Grafbase user | | **List audit logs** `grafbase_list_audit_logs` | List audit logs for Grafbase organizations | | **List extensions** `grafbase_list_extensions` | List all extensions configured for a Grafbase project | | **List mcp servers** `grafbase_list_mcp_servers` | Check MCP server configuration status for a Grafbase gateway | | **List schema checks** `grafbase_list_schema_checks` | List schema checks for a Grafbase graph | | **List schemas** `grafbase_list_schemas` | List all schemas in the Grafbase schema registry | | **List subgraphs** `grafbase_list_subgraphs` | List published subgraphs in your Grafbase federated graphs | | **Add zitadel redirect** `grafbase_add_zitadel_redirect` | Add a redirect URI to Zitadel OAuth configuration in Grafbase | | **Assign team role** `grafbase_assign_team_role` | Assign a role to a team member in Grafbase | | **Enable mcp** `grafbase_enable_mcp` | Enable the Model Context Protocol (MCP) server on a Grafbase gateway | | **Mark notifications as read** `grafbase_mark_notifications_as_read` | Mark Grafbase notifications as read | | **Disable mcp** `grafbase_disable_mcp` | Disable the Model Context Protocol (MCP) server for a Grafbase project | | **Remove graph owner** `grafbase_remove_graph_owner` | Remove an owner from a Grafbase graph | ## Example prompts **Get Audit Log** > Pull the relevant data from Grafbase, summarize it in plain English, and point out anything that needs attention. **Get Extension By Name** > Pull the relevant data from Grafbase, summarize it in plain English, and point out anything that needs attention. **Get Extension Version By Name And Version** > Pull the relevant data from Grafbase, summarize it in plain English, and point out anything that needs attention. **Get Federated Schema** > Pull the relevant data from Grafbase, 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 Grafbase working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Grafbase API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Grafbase 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 Grafbase. | 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 Grafbase actions to the runtime in a format your agent can reliably use. | 28 tools for Grafbase are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Grafbase 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 Grafbase in the browser, and the 28 tools above work from chat. There is no SDK and no config file, and the Grafbase 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 Grafbase 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 Grafbase 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 Grafbase tools Grafbase 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 Grafbase 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. ### Grafbase 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 Grafbase 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 Grafbase integration? Yes. ClawLink is the fastest way to connect Hermes to Grafbase: link your Grafbase account once in the browser and Hermes Agent can call the Grafbase API through 28 ready-made tools — no custom code or token handling. ### How do I connect Grafbase 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 Grafbase in the dashboard and Hermes can use it from the next message — no config files, and the Grafbase key you paste is stored server-side instead of in your environment. ### How long does it take to connect Grafbase to Hermes Agent? About two minutes. Sign in, click Connect next to Grafbase in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Grafbase 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 Grafbase working from chat. ### Hermes paired but still can't use Grafbase 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 - [GitHub](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty tools](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [Connect 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.