# How to connect iLovePDF to Hermes Agent (paste one key, 9 tools)

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

Web version: https://claw-link.dev/hermes/i-love-pdf

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

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

Verify the connection by asking Hermes:

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

## iLovePDF MCP for Hermes

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

## What the Hermes Agent iLovePDF integration can do

9 iLovePDF tools are ready for Hermes Agent once the account is connected. The 8 below are the ones people reach for most; your agent can call all 9.

### 8 of 9 iLovePDF tools for Hermes

| Tool | What it does |
|---|---|
| **Get account info** `i_love_pdf_get_account_info` | Return the connected iLovePDF project's account type and remaining processing allowance |
| **Get task status** `i_love_pdf_get_task_status` | Inspect an iLovePDF task's current state and output metadata on its assigned worker |
| **Compress images** `i_love_pdf_compress_images` | Compress one or more images and immediately return the resulting image or ZIP as an offloaded |
| **Compress pdfs** `i_love_pdf_compress_pdfs` | Compress one or more PDFs and return the stored PDF or ZIP output in one workflow: task |
| **Convert images to PDF** `i_love_pdf_convert_images_to_pdf` | Convert one or more images into PDF output using iLovePDF's documented defaults and immediately |
| **Convert PDF to images** `i_love_pdf_convert_pdf_to_images` | Convert a PDF using iLovePDF's default PDF-to-JPG behavior and immediately return the generated |
| **Merge pdfs** `i_love_pdf_merge_pdfs` | Merge two or more PDFs in the supplied order and return the merged file in one workflow |
| **Split PDF** `i_love_pdf_split_pdf` | Split one PDF by explicit ranges, fixed page intervals, or removed pages and return the |

## Example prompts

**Get Account Info**

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

**Get Task Status**

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

**Compress Images**

> Use iLovePDF to compress images and walk me through the result in plain English.

**Compress Pdfs**

> Use iLovePDF to compress pdfs and walk me through the result in plain English.

## 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 iLovePDF working from chat.

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

## ClawLink vs. Composio

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

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

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

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

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

### Hermes paired but still can't use iLovePDF
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](https://claw-link.dev/hermes/box) — Store, share, and manage files and folders
- [Connect Supabase](https://claw-link.dev/hermes/supabase) — Query and manage Postgres databases
- [Connect Dropbox](https://claw-link.dev/hermes/dropbox) — Store, sync, and share files