# How to connect Clientary to Hermes Agent (paste one key, 57 tools)

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

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

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

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

Verify the connection by asking Hermes:

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

## Clientary MCP for Hermes

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

## What the Hermes Agent Clientary integration can do

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

### 30 of 57 Clientary tools for Hermes

| Tool | What it does |
|---|---|
| **Get client** `clientary_get_client` | Fetch details for a specific client using its ID |
| **Get contact** `clientary_get_contact` | Retrieve a single contact by its ID |
| **Get estimate** `clientary_get_estimate` | Retrieve details for a single estimate by ID |
| **Get expense** `clientary_get_expense` | Retrieve details for a single expense record in Clientary |
| **Get hour** `clientary_get_hour` | Obtain details about a specific time entry in Clientary |
| **Get invoice** `clientary_get_invoice` | Retrieve detailed information for a specific invoice by ID |
| **Get lead** `clientary_get_lead` | Retrieve a single lead by its ID |
| **Get project** `clientary_get_project` | Retrieve a single project by its identifier |
| **Get staff** `clientary_get_staff` | Retrieve a single staff member by their ID |
| **Get task** `clientary_get_task` | Retrieve a specific task by its ID |
| **List client contacts** `clientary_list_client_contacts` | Retrieve all contacts for a specific client with pagination support |
| **List client estimates** `clientary_list_client_estimates` | Retrieve all estimates for a specific client with pagination support (30 results per page) |
| **List client expenses** `clientary_list_client_expenses` | Retrieve all expenses for a specific client within an optional date range |
| **List client invoices** `clientary_list_client_invoices` | Retrieve all invoices for a specific client with pagination support (30 results per page) |
| **List client payment profiles** `clientary_list_client_payment_profiles` | Retrieve payment profiles for a specific client |
| **List client projects** `clientary_list_client_projects` | Retrieve all projects associated with a specific client with pagination support (10 results per |
| **List clients** `clientary_list_clients` | Retrieve all clients with pagination support (10 results per page) |
| **List estimates** `clientary_list_estimates` | Retrieve all estimates with pagination support (30 results per page) |
| **List expenses** `clientary_list_expenses` | Retrieve expenses by date range (defaults to current fiscal year) |
| **List leads** `clientary_list_leads` | Retrieve all leads with pagination support |
| **List payments** `clientary_list_payments` | Retrieve all payments with pagination support (30 results per page) |
| **List project estimates** `clientary_list_project_estimates` | Retrieve estimates scoped to a particular project with pagination support (30 results per page) |
| **List project expenses** `clientary_list_project_expenses` | Retrieve all expenses for a specific project within an optional date range |
| **List project hours** `clientary_list_project_hours` | Retrieve all time tracking entries logged against a specific project |
| **List project invoices** `clientary_list_project_invoices` | Retrieve all invoices linked to a specific project with pagination support (30 results per page) |
| **List project tasks** `clientary_list_project_tasks` | Retrieve all tasks for a specific project |
| **List projects** `clientary_list_projects` | Retrieve all projects with pagination support (10 results per page) |
| **List recurring schedule invoices** `clientary_list_recurring_schedule_invoices` | Retrieve all invoices generated by a specific recurring schedule with pagination support (30 |
| **List staff** `clientary_list_staff` | Retrieve all staff members for an account |
| **List tasks** `clientary_list_tasks` | Retrieve all tasks with pagination support (50 results per page) |

## Example prompts

**Get Client**

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

**Get Contact**

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

**Get Estimate**

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

**Get Expense**

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

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

## ClawLink vs. Composio

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

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

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

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

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

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

- [Trello tools](https://claw-link.dev/hermes/trello) — Manage boards, lists, and cards
- [Moco](https://claw-link.dev/hermes/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions.
- [ClickUp](https://claw-link.dev/hermes/clickup) — Manage tasks, docs, goals, and sprints