# How to connect Cloudpress to Hermes Agent (paste one key, 5 tools)

> Connect Cloudpress to Hermes with ClawLink: paste your Cloudpress key once and 5 tools work from chat. No MCP server to run, nothing stored on your machine.

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

Most guides for giving Hermes Agent Cloudpress 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 Cloudpress setup: pair once in the browser and your always-on Hermes agent can act on Cloudpress 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 Cloudpress.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Cloudpress** — 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 cloudpress  # connect Cloudpress (browser OAuth)
npx -y @useclawlink/cli actions cloudpress  # list available actions
npx -y @useclawlink/cli run cloudpress <action> --input '<json>'  # 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 Cloudpress in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Cloudpress API key once.

Verify the connection by asking Hermes:

> Pull the relevant data from Cloudpress, 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 Cloudpress is connected in the dashboard, that agent calls the same 5 Cloudpress 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).

## Cloudpress MCP for Hermes

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

## What the Hermes Agent Cloudpress integration can do

5 Cloudpress tools are ready for Hermes Agent once the account is connected.

### All 5 Cloudpress tools for Hermes

| Tool | What it does |
|---|---|
| **Get account information** `cloudpress_get_account_information` | Retrieve authenticated account information |
| **List collections** `cloudpress_list_collections` | List all collections in the user's Cloudpress account |
| **List connections** `cloudpress_list_connections` | List all connections with pagination |
| **List document exports** `cloudpress_list_document_exports` | Retrieve a paginated list of document exports |
| **List webhooks** `cloudpress_list_webhooks` | Retrieve a paginated list of webhooks |

## Example prompts

**Get Account Information**

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

**List Collections**

> List the relevant items in Cloudpress, group them by priority, and recommend what Hermes should do next.

**List Connections**

> List the relevant items in Cloudpress, group them by priority, and recommend what Hermes should do next.

**List Document Exports**

> List the relevant items in Cloudpress, 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 Cloudpress working from chat.

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

## ClawLink vs. Composio

Composio also exposes Cloudpress 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 Cloudpress in the browser, and the 5 tools above work from chat. There is no SDK and no config file, and the Cloudpress 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 Cloudpress
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 Cloudpress 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 Cloudpress tools
Cloudpress 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 Cloudpress 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.

### Cloudpress 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 Cloudpress 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 Cloudpress integration?
Yes. ClawLink is the fastest way to connect Hermes to Cloudpress: link your Cloudpress account once in the browser and Hermes Agent can call the Cloudpress API through 5 ready-made tools — no custom code or token handling.

### How do I connect Cloudpress 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 Cloudpress in the dashboard and Hermes can use it from the next message — no config files, and the Cloudpress key you paste is stored server-side instead of in your environment.

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

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

### Hermes paired but still can't use Cloudpress
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

- [Box tools](https://claw-link.dev/hermes/box) — Store, share, and manage files and folders
- [Hermes Supabase integration](https://claw-link.dev/hermes/supabase) — Query and manage Postgres databases
- [Dropbox](https://claw-link.dev/hermes/dropbox) — Store, sync, and share files