# How to connect Rocketlane to Hermes Agent (paste one key, 69 tools)

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

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

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

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

Verify the connection by asking Hermes:

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

## Rocketlane MCP for Hermes

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

## What the Hermes Agent Rocketlane integration can do

69 Rocketlane 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 69.

### 30 of 69 Rocketlane tools for Hermes

| Tool | What it does |
|---|---|
| **Get all conversations** `rocketlane_get_all_conversations` | Retrieve all conversations in Rocketlane |
| **Get all fields** `rocketlane_get_all_fields` | Retrieve all custom fields available in the system |
| **Get all resource allocations** `rocketlane_get_all_resource_allocations` | Retrieve all resource allocations from Rocketlane |
| **Get all spaces** `rocketlane_get_all_spaces` | Retrieve all spaces for a specific project in Rocketlane |
| **Get all tasks** `rocketlane_get_all_tasks` | Retrieve all tasks from Rocketlane with advanced filtering options |
| **Get all timeoffs** `rocketlane_get_all_timeoffs` | Retrieve all time-offs from Rocketlane with advanced filtering options |
| **Get comments** `rocketlane_get_comments` | Retrieve all comments from Rocketlane |
| **Get company** `rocketlane_get_company` | Retrieves detailed information about a specific company/account in Rocketlane by its ID |
| **Get conversation** `rocketlane_get_conversation` | Retrieve detailed information about a conversation by its ID |
| **Get field by ID** `rocketlane_get_field_by_id` | Retrieve detailed information about a specific custom field using its unique identifier |
| **Get phase by ID** `rocketlane_get_phase_by_id` | Retrieve extensive information about a specific phase by its unique identifier |
| **Get project by ID** `rocketlane_get_project_by_id` | Retrieves detailed information about a specific project using its unique identifier |
| **Get space** `rocketlane_get_space` | Retrieve detailed information about a specific space using its unique identifier |
| **Get task by ID** `rocketlane_get_task_by_id` | Retrieve extensive information about a specific task using the task's unique identifier (taskId) |
| **Get template by ID** `rocketlane_get_template_by_id` | Retrieve detailed information about a specific template using its unique identifier (templateId) |
| **Get time entries** `rocketlane_get_time_entries` | Retrieve all time entries from Rocketlane |
| **Get time entry by ID** `rocketlane_get_time_entry_by_id` | Retrieve detailed information about a specific time entry using its unique identifier |
| **Get time entry categories** `rocketlane_get_time_entry_categories` | Retrieve time entry categories from Rocketlane |
| **Get user by ID** `rocketlane_get_user_by_id` | Retrieve detailed information about a specific user using their unique identifier (userId) |
| **List companies** `rocketlane_list_companies` | Retrieves a list of all companies/accounts in Rocketlane |
| **List currencies** `rocketlane_list_currencies` | Returns a predefined list of commonly used currencies since Rocketlane API doesn't provide a |
| **List project phases** `rocketlane_list_project_phases` | Retrieves a list of project phases from Rocketlane |
| **List projects** `rocketlane_list_projects` | Retrieves a list of all projects in the Rocketlane instance |
| **List templates** `rocketlane_list_templates` | Retrieves a list of all available templates in Rocketlane |
| **List users** `rocketlane_list_users` | Retrieves all users in the Rocketlane instance |
| **Retrieve subscription details** `rocketlane_retrieve_subscription_details` | Retrieves detailed information about the current subscription |
| **Search invoices** `rocketlane_search_invoices` | Retrieve all invoices from Rocketlane |
| **Search time entries** `rocketlane_search_time_entries` | Search time entries with filters in Rocketlane |
| **Search user by email** `rocketlane_search_user_by_email` | Search User By Email Id |
| **Add assignee to task** `rocketlane_add_assignee_to_task` | Add assignees to a task by task ID |

## Example prompts

**Get All Conversations**

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

**Get All Fields**

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

**Get All Resource Allocations**

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

**Get All Spaces**

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

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

## ClawLink vs. Composio

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

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

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

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

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

### Hermes paired but still can't use Rocketlane
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
- [Connect Moco](https://claw-link.dev/hermes/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions.
- [Hermes ClickUp integration](https://claw-link.dev/hermes/clickup) — Manage tasks, docs, goals, and sprints
