# How to connect Layerre to Hermes Agent (paste one key, 15 tools) > Connect Layerre to Hermes with ClawLink: paste your Layerre key once and 15 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/layerre Most guides for giving Hermes Agent Layerre 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 Layerre setup: pair once in the browser and your always-on Hermes agent can act on Layerre 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 Layerre. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Layerre** — 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 layerre # connect Layerre (browser OAuth) npx -y @useclawlink/cli actions layerre # list available actions npx -y @useclawlink/cli run layerre --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 Layerre in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Layerre API key once. Verify the connection by asking Hermes: > Use Layerre to analyze canva design 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 Layerre is connected in the dashboard, that agent calls the same 15 Layerre 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). ## Layerre MCP for Hermes Looking for a Layerre MCP server for Hermes Agent? ClawLink connects Layerre to Hermes Agent and exposes 15 Layerre 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 Layerre integration](https://claw-link.dev/openclaw/layerre) works the same way. ## What the Hermes Agent Layerre integration can do 15 Layerre tools are ready for Hermes Agent once the account is connected. The 12 below are the ones people reach for most; your agent can call all 15. ### 12 of 15 Layerre tools for Hermes | Tool | What it does | |---|---| | **Analyze canva design** `layerre_analyze_canva_design` | Extract colors, fonts, and images from a public Canva share URL without creating a documented | | **Get layer** `layerre_get_layer` | Return one template layer, refreshing its signed image URL when needed | | **Get template** `layerre_get_template` | Return one template with its layers and refreshed signed image URLs | | **Get variant** `layerre_get_variant` | Return one generated variant with a refreshed signed output URL | | **List template variants** `layerre_list_template_variants` | Return one page of a template's generated variants with refreshed signed URLs and an opaque | | **List templates** `layerre_list_templates` | Return one page of the connected account's templates, most recently modified first, with an | | **Create layer** `layerre_create_layer` | Create a text or image layer on a template and return the new layer | | **Create template** `layerre_create_template` | Import a public Canva share URL as a Layerre template | | **Create variant** `layerre_create_variant` | Synchronously render one template variant and return its signed output URL | | **Create variants bulk** `layerre_create_variants_bulk` | Synchronously render multiple variants with one shared output format | | **Update layer** `layerre_update_layer` | Update a layer and return the refreshed layer | | **Update template** `layerre_update_template` | Update a template and return the refreshed template | ## Example prompts **Analyze Canva Design** > Use Layerre to analyze canva design and walk me through the result in plain English. **Get Layer** > Pull the relevant data from Layerre, summarize it in plain English, and point out anything that needs attention. **Get Template** > Pull the relevant data from Layerre, summarize it in plain English, and point out anything that needs attention. **Get Variant** > Pull the relevant data from Layerre, 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 Layerre working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Layerre API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Layerre 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 Layerre. | 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 Layerre actions to the runtime in a format your agent can reliably use. | 15 tools for Layerre are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Layerre 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 Layerre in the browser, and the 15 tools above work from chat. There is no SDK and no config file, and the Layerre 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 Layerre 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 Layerre 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 Layerre tools Layerre 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 Layerre 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. ### Layerre 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 Layerre 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 Layerre integration? Yes. ClawLink is the fastest way to connect Hermes to Layerre: link your Layerre account once in the browser and Hermes Agent can call the Layerre API through 15 ready-made tools — no custom code or token handling. ### How do I connect Layerre 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 Layerre in the dashboard and Hermes can use it from the next message — no config files, and the Layerre key you paste is stored server-side instead of in your environment. ### How long does it take to connect Layerre to Hermes Agent? About two minutes. Sign in, click Connect next to Layerre in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Layerre 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 Layerre working from chat. ### Hermes paired but still can't use Layerre 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 - [Cloudinary](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. - [Canva](https://claw-link.dev/hermes/canva) — Create designs, upload assets, export content, and manage brand templates