# How to connect Bannerbite to Hermes Agent (paste one key, 6 tools) > Connect Bannerbite to Hermes with ClawLink: paste your Bannerbite key once and 6 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/bannerbite Most guides for giving Hermes Agent Bannerbite 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 Bannerbite setup: pair once in the browser and your always-on Hermes agent can act on Bannerbite 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 Bannerbite. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Bannerbite** — 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 bannerbite # connect Bannerbite (browser OAuth) npx -y @useclawlink/cli actions bannerbite # list available actions npx -y @useclawlink/cli run bannerbite --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 Bannerbite in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Bannerbite API key once. Verify the connection by asking Hermes: > Pull the relevant data from Bannerbite, 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 Bannerbite is connected in the dashboard, that agent calls the same 6 Bannerbite 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). ## Bannerbite MCP for Hermes Looking for a Bannerbite MCP server for Hermes Agent? ClawLink connects Bannerbite to Hermes Agent and exposes 6 Bannerbite 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 Bannerbite integration](https://claw-link.dev/openclaw/bannerbite) works the same way. ## What the Hermes Agent Bannerbite integration can do 6 Bannerbite tools are ready for Hermes Agent once the account is connected. ### All 6 Bannerbite tools for Hermes | Tool | What it does | |---|---| | **Get bite** `bannerbite_get_bite` | Return one Bannerbite bite by its numeric bite ID, including template and output-size details | | **Get project** `bannerbite_get_project` | Return one Bannerbite project by its numeric project ID; fail explicitly when the project does | | **Get scene data** `bannerbite_get_scene_data` | Return the editable scene fields for a Bannerbite bite so their names and current values can be | | **List bites** `bannerbite_list_bites` | Return one provider page of Bannerbite bites in a project, up to 100 bites; the API exposes no | | **List projects** `bannerbite_list_projects` | Return one provider page of projects owned by the connected Bannerbite account, up to 100 | | **Generate media** `bannerbite_generate_media` | Queue one asynchronous image, video, or overlay render from a Bannerbite bite | ## Example prompts **Get Bite** > Pull the relevant data from Bannerbite, summarize it in plain English, and point out anything that needs attention. **Get Project** > Pull the relevant data from Bannerbite, summarize it in plain English, and point out anything that needs attention. **Get Scene Data** > Pull the relevant data from Bannerbite, summarize it in plain English, and point out anything that needs attention. **List Bites** > List the relevant items in Bannerbite, 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 Bannerbite working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Bannerbite API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Bannerbite 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 Bannerbite. | 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 Bannerbite actions to the runtime in a format your agent can reliably use. | 6 tools for Bannerbite are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Bannerbite 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 Bannerbite in the browser, and the 6 tools above work from chat. There is no SDK and no config file, and the Bannerbite 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 Bannerbite 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 Bannerbite 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 Bannerbite tools Bannerbite 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 Bannerbite 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. ### Bannerbite 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 Bannerbite 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 Bannerbite integration? Yes. ClawLink is the fastest way to connect Hermes to Bannerbite: link your Bannerbite account once in the browser and Hermes Agent can call the Bannerbite API through 6 ready-made tools — no custom code or token handling. ### How do I connect Bannerbite 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 Bannerbite in the dashboard and Hermes can use it from the next message — no config files, and the Bannerbite key you paste is stored server-side instead of in your environment. ### How long does it take to connect Bannerbite to Hermes Agent? About two minutes. Sign in, click Connect next to Bannerbite in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Bannerbite 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 Bannerbite working from chat. ### Hermes paired but still can't use Bannerbite 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 Cloudinary integration](https://claw-link.dev/hermes/cloudinary) — Cloudinary is a cloud-based media management platform for uploading, storing, transforming, and delivering images and videos via CDN. - [Hermes Penpot integration](https://claw-link.dev/hermes/penpot) — Open-source design and prototyping platform for collaborative design workflows. - [Connect Canva](https://claw-link.dev/hermes/canva) — Create designs, upload assets, export content, and manage brand templates