# How to connect Everhour to Hermes Agent (paste one key, 38 tools)

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

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

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

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

Verify the connection by asking Hermes:

> Use Everhour to client list 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 Everhour is connected in the dashboard, that agent calls the same 38 Everhour 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).

## Everhour MCP for Hermes

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

## What the Hermes Agent Everhour integration can do

38 Everhour 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 38.

### 30 of 38 Everhour tools for Hermes

| Tool | What it does |
|---|---|
| **Client list** `everhour_client_list` | Retrieves all clients in the Everhour workspace |
| **Expenses list** `everhour_expenses_list` | Lists expense records from your Everhour workspace |
| **Get client** `everhour_get_client` | Retrieve a specific client by ID |
| **Get project** `everhour_get_project` | Retrieve a specific project |
| **Get section** `everhour_get_section` | Retrieve details of a specific section by its ID |
| **Get timecard** `everhour_get_timecard` | Retrieve a specific timecard for a user on a date |
| **Get user profile** `everhour_get_user_profile` | Retrieve profile information of the authenticated user |
| **Get webhook** `everhour_get_webhook` | Retrieve details of a specific webhook by its ID |
| **List expense categories** `everhour_list_expense_categories` | Lists all expense categories available in your Everhour account |
| **List hooks** `everhour_list_hooks` | Lists all webhooks configured for the Everhour account |
| **List invoices** `everhour_list_invoices` | Retrieves all invoices from your Everhour workspace |
| **List projects** `everhour_list_projects` | List all Everhour projects accessible by the authenticated user |
| **List sections** `everhour_list_sections` | Lists all sections within a specific Everhour project |
| **List tags** `everhour_list_tags` | List all tags in the Everhour workspace |
| **List team members** `everhour_list_team_members` | Retrieves all team members in the authenticated Everhour workspace |
| **List teams** `everhour_list_teams` | Retrieves information about the authenticated team/workspace in Everhour |
| **List timecards** `everhour_list_timecards` | Retrieve all team timecards with optional date filtering |
| **List user timecards** `everhour_list_user_timecards` | Retrieve timecards for a specific user with optional date filtering |
| **List user timesheets** `everhour_list_user_timesheets` | Retrieve timesheets for a specific user |
| **Client create** `everhour_client_create` | Creates a new client in Everhour for tracking billable work, invoicing, and project organization |
| **Clock in** `everhour_clock_in` | Clock in a user for time tracking |
| **Clock out** `everhour_clock_out` | Clock out a user for time tracking |
| **Create webhook** `everhour_create_webhook` | Create a new webhook for event notifications in Everhour |
| **Project create** `everhour_project_create` | Create a new project in Everhour |
| **Request timesheet approval** `everhour_request_timesheet_approval` | Request approval for a timesheet or approve a week (for admins) |
| **Section create** `everhour_section_create` | Create a new section in a project |
| **Task create** `everhour_task_create` | Creates a new task in an Everhour project |
| **Timer start** `everhour_timer_start` | Start a new timer for a task |
| **Update client** `everhour_update_client` | Update an existing client in Everhour |
| **Update project** `everhour_update_project` | Updates an existing Everhour project's settings |

## Example prompts

**Client List**

> Use Everhour to client list and walk me through the result in plain English.

**Expenses List**

> Use Everhour to expenses list and walk me through the result in plain English.

**Get Client**

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

**Get Project**

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

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

## ClawLink vs. Composio

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

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

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

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

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

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