# How to connect Builder.io to Hermes Agent (paste one key, 10 tools) > Connect Builder.io to Hermes with ClawLink: paste your Builder.io key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/builder-io Most guides for giving Hermes Agent Builder.io 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 Builder.io setup: pair once in the browser and your always-on Hermes agent can act on Builder.io 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 Builder.io. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Builder.io** — 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 builder-io # connect Builder.io (browser OAuth) npx -y @useclawlink/cli actions builder-io # list available actions npx -y @useclawlink/cli run builder-io --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 Builder.io in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Builder.io API key once. Verify the connection by asking Hermes: > Pull the relevant data from Builder.io, 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 Builder.io is connected in the dashboard, that agent calls the same 10 Builder.io 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). ## Builder.io MCP for Hermes Looking for a Builder.io MCP server for Hermes Agent? ClawLink connects Builder.io to Hermes Agent and exposes 10 Builder.io 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 Builder.io integration](https://claw-link.dev/openclaw/builder-io) works the same way. ## What the Hermes Agent Builder.io integration can do 10 Builder.io tools are ready for Hermes Agent once the account is connected. The 9 below are the ones people reach for most; your agent can call all 10. ### 9 of 10 Builder.io tools for Hermes | Tool | What it does | |---|---| | **Get content entry** `builder_io_get_content_entry` | Retrieve one content entry by model name and entry ID from the connected Builder.io Space | | **Get space details** `builder_io_get_space_details` | Return the authenticated Builder.io Space ID and its read-only settings | | **List assets** `builder_io_list_assets` | List, filter, and sort assets in the connected Builder.io Space without modifying the Asset | | **List content entries** `builder_io_list_content_entries` | List and filter content entries from any model in the connected Builder.io Space, one | | **List content folders** `builder_io_list_content_folders` | List the content folders configured in the connected Builder.io Space | | **List models** `builder_io_list_models` | List the content models in the connected Builder.io Space, optionally including each model's | | **List space users** `builder_io_list_space_users` | List users and roles with access to the connected Builder.io Space | | **Create content entry** `builder_io_create_content_entry` | Create a draft, published, or archived entry in an existing Builder.io model | | **Update content entry** `builder_io_update_content_entry` | Partially update an existing Builder.io content entry | ## Example prompts **Get Content Entry** > Pull the relevant data from Builder.io, summarize it in plain English, and point out anything that needs attention. **Get Space Details** > Pull the relevant data from Builder.io, summarize it in plain English, and point out anything that needs attention. **List Assets** > List the relevant items in Builder.io, group them by priority, and recommend what Hermes should do next. **List Content Entries** > List the relevant items in Builder.io, group them by priority, and recommend what Hermes should do next. ## 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 Builder.io working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Builder.io API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Builder.io 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 Builder.io. | 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 Builder.io actions to the runtime in a format your agent can reliably use. | 10 tools for Builder.io are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Builder.io 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 Builder.io in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Builder.io 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 Builder.io 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 Builder.io 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 Builder.io tools Builder.io 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 Builder.io 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. ### Builder.io 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 Builder.io 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 Builder.io integration? Yes. ClawLink is the fastest way to connect Hermes to Builder.io: link your Builder.io account once in the browser and Hermes Agent can call the Builder.io API through 10 ready-made tools — no custom code or token handling. ### How do I connect Builder.io 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 Builder.io in the dashboard and Hermes can use it from the next message — no config files, and the Builder.io key you paste is stored server-side instead of in your environment. ### How long does it take to connect Builder.io to Hermes Agent? About two minutes. Sign in, click Connect next to Builder.io in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Builder.io 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 Builder.io working from chat. ### Hermes paired but still can't use Builder.io 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 - [Hermes PagerDuty integration](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.