# How to connect Render to Hermes

> Connect Render to Hermes in one click. 8 Render tools your agent can call from chat. No API keys.

Web version: https://claw-link.dev/hermes/render

ClawLink gives Hermes a more practical Render setup than rolling your own integration. Pair once in the browser and your always-on Hermes agent can act on Render for you — reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

## Render MCP for Hermes

Looking for a Render MCP server for Hermes Agent? ClawLink connects Render to Hermes Agent and exposes 8 Render 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 Render integration](https://claw-link.dev/openclaw/render) works the same way.

**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 Render.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Render** — 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 render  # connect Render (browser OAuth)
npx -y @useclawlink/cli actions render  # list available actions
npx -y @useclawlink/cli run render <action> --input '<json>'  # execute (add --confirm for writes)
```

## What the Hermes Agent Render integration can do

8 Render tools are ready for Hermes Agent once the account is connected.

### All 8 Render tools for Hermes

| Tool | What it does |
|---|---|
| **Get cpu** `render_get_cpu` | Retrieve CPU usage metrics for Render resources |
| **Get memory** `render_get_memory` | Get memory usage metrics for Render resources |
| **Get disk usage** `render_get_disk_usage` | Retrieve disk usage metrics |
| **Get instance count** `render_get_instance_count` | Get instance count metrics |
| **Add headers** `render_add_headers` | Add a custom HTTP header rule to a service |
| **Add or update secret file** `render_add_or_update_secret_file` | Add or update a secret file for a service |
| **Add resources to environment** `render_add_resources_to_environment` | Add resources to a Render environment |
| **Add route** `render_add_route` | Add redirect or rewrite rules to a service |

## Example prompts

**Get Cpu**

> Pull the relevant data from Render, summarize it in plain English, and point out anything that needs attention.

**Get Memory**

> Pull the relevant data from Render, summarize it in plain English, and point out anything that needs attention.

**Get Disk Usage**

> Pull the relevant data from Render, summarize it in plain English, and point out anything that needs attention.

**Get Instance Count**

> Pull the relevant data from Render, 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 Render working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Render API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Render 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 Render. | 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 Render actions to the runtime in a format your agent can reliably use. | 8 tools for Render are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Render 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 Render in the browser, and the 8 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison.

### Hermes paired but still can't use Render
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 Render from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

### The Render account is connected but the action fails
Check whether the connected account has access to the workspace, inbox, store, or project you are trying to use. Most failures at this stage are permission mismatches, not ClawLink bugs.

### API key setup works but results look incomplete
Double-check that the API key for Render 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 Render integration?
Yes. ClawLink is the fastest way to connect Hermes to Render: link your Render account once in the browser and Hermes Agent can call the Render API through 8 ready-made tools — no custom code or token handling.

### How do I connect Render 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 Render in the dashboard and Hermes can use it from the next message — no config files or API keys to manage.

### How long does it take to connect Render to Hermes Agent?
About two minutes. Sign in, click Connect next to Render in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

### Why use ClawLink instead of wiring Render 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 Render working from chat.

### Hermes paired but still can't use Render
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 Apify integration](https://claw-link.dev/hermes/apify) — Run web scrapers, manage Actors, datasets, and schedules
- [Hostinger](https://claw-link.dev/hermes/hostinger) — Manage domains, DNS, VPS, and web hosting
- [Hermes Vercel integration](https://claw-link.dev/hermes/vercel) — Manage projects, deployments, domains, and environment variables