Source: https://harnsy.dev/hire-ai-employees-openclaw-hermes-mcp

> Three ways to use the hr.harnsy.dev catalog outside harnsy: a plugin for OpenClaw, a plugin for Hermes Agent, and an MCP server for Claude Code, Codex and other clients. Commands and what each one writes.

# Hire an AI employee in OpenClaw, Hermes Agent or an MCP client

hr.harnsy.dev is a catalog of AI employees. An employee is a role with a character: who it is, how it decides and speaks, its job, and the skills it works with. In harnsy your project lead hires one. This page is for three other places: OpenClaw, Hermes Agent, and agents that speak MCP. Hiring is free in each: the catalog and the plugins cost nothing. The model your OpenClaw, Hermes Agent or MCP client runs on is yours, on your own plan.

## OpenClaw

**What you get.** The employee becomes an OpenClaw agent beside your own, with a workspace of its own. Your own agent and its workspace are not touched, and several employees can live side by side.

### Steps

1. Install the plugin:
   ```
   openclaw plugins install git:github.com/harnesy/hr-openclaw@v0.1.0
   ```
   The source is spelled `git:github.com/…`: a full `https://` address is refused. OpenClaw warns that this source is outside ClawHub review and asks you twice before it installs: first about the source, then, once it has fetched the plugin, about what the plugin is allowed to do. In that list OpenClaw also shows “Prompt injection: allowed”: that is what OpenClaw permits a plugin of this kind, not something this plugin does. It adds no text to your agent’s prompts; the source shows it. OpenClaw has its own setting that denies prompt injection for one plugin; its documentation names it. In our run with OpenClaw 2026.11.3 `search` and `hire` worked the same with it denied.
   Both answers default to no, and without your yes nothing is installed. Read the source first. (`--force --accept-capabilities` answers both beforehand.)
   The install fetches the plugin only: no employee is downloaded. OpenClaw prints “Installing plugin dependencies with npm…” on the way: the plugin has none, and in our run nothing came from the npm registry.
2. Find an employee:
   ```
   openclaw harnsy-hr search accountant
   ```
3. Read it before you hire: its card, what it needs, every file a hire writes, and its notice.
   ```
   openclaw harnsy-hr show harnsy/accountant
   ```
4. Hire it:
   ```
   openclaw harnsy-hr hire harnsy/accountant
   ```
   The plugin shows the same list once more and asks. After your yes it writes the files and adds the agent; if you answer no, nothing is written. (`--yes` skips the question.)
5. Check who is hired:
   ```
   openclaw harnsy-hr list
   ```
6. Talk to it:
   ```
   openclaw agent --agent accountant --message &quot;Who are you, and what do you do first?&quot;
   ```
   Before the answer OpenClaw prints a warning that it cannot verify where the plugin came from: the plugin is not from ClawHub. The answer follows. We ran this line with `--local` added, as no Gateway was running.

**What it writes.** A folder `workspace-&lt;name&gt;` under OpenClaw’s state directory (`~/.openclaw`): `SOUL.md` (who the employee is), `AGENTS.md` (its job), `IDENTITY.md`, its skills, its casebook in `docs/`, and `NOTICE.md` with the licence and credits. If an agent of that name exists or the folder already holds files, the hire stops: it never overwrites.

**Later.** `openclaw harnsy-hr update &lt;id&gt;` checks the catalog for a newer version of the employee. It asks first, and asks again about each file you changed since the hire: answer no, and your file is kept. `openclaw harnsy-hr list` shows who is hired on this machine. `openclaw harnsy-hr fire &lt;id&gt;` asks, then has OpenClaw remove the agent and move its workspace, state and transcripts to the Trash.

**Good to know.** The hired agent uses the model your OpenClaw is set up with. We ran it with OpenClaw 2026.11.3. It adds no tools for the model, no hooks and no background service. It runs only when called: by you at the terminal, or in a chat with your agent by you or someone you admitted there. In a chat it can only search, show and list (so someone you admitted can see who is hired); hiring, updating and firing work at the terminal only. We have not tried the chat command in a live channel. It connects straight to the catalog and does not use a proxy, so on a proxy-only network it does not work. We ran it on Linux; not yet on Windows or macOS.

Source and full reference: [github.com/harnesy/hr-openclaw](https://github.com/harnesy/hr-openclaw)

## Hermes Agent

**What you get.** In Hermes one employee is one profile: its own `SOUL.md`, its own skills, its own memory and sessions. You talk to it as a separate agent. Your own profile and its `SOUL.md` are not touched.

### Steps

1. Install the plugin. Hermes installs a plugin at an exact commit:
   ```
   hermes plugins install harnesy/hr-hermes --ref 4eef0eca106431d574b7b3cbff90f35691f18a90 --enable
   ```
   Hermes warns that the source is not from its own catalog (“custom (unreviewed) source”). `--enable` turns the plugin on at once.
2. Find an employee and read it before you hire:
   ```
   hermes harnsy-hr search accountant
   ```
   ```
   hermes harnsy-hr show harnsy/accountant
   ```
3. Hire it:
   ```
   hermes harnsy-hr hire harnsy/accountant
   ```
   The plugin shows the card, what the employee needs, the list of files and the full notice, and asks you. After your yes Hermes’ own `hermes profile install` shows what it installs and asks once more.
4. Give it a model once. A new profile has no model settings of its own. These three lines are what we ran, for an OpenAI-compatible address that needs no key; for another provider, see Hermes Agent’s own documentation.
   ```
   hermes -p &lt;name&gt; config set model.provider custom
   ```
   ```
   hermes -p &lt;name&gt; config set model.base_url &lt;address&gt;
   ```
   ```
   hermes -p &lt;name&gt; config set model.default &lt;model&gt;
   ```
5. Talk to it:
   ```
   hermes -p &lt;name&gt; chat
   ```

**What it writes.** The employee’s files in the plugin’s own folder, `~/.hermes/harnsy-hr/`, which Hermes then copies into the profile, `~/.hermes/profiles/&lt;name&gt;/`: `SOUL.md`, its skills (its casebook comes as the skill `persona-casebook`), `NOTICE.md` and `distribution.yaml`. A profile of that name that already exists is never replaced: the hire stops and asks for `--name`.

**Later.** `hermes harnsy-hr update &lt;name&gt;` checks the catalog for a newer version of the employee and, when there is one, hands the update to Hermes’ own `hermes profile update`. `hermes harnsy-hr list` shows who is hired; `hermes harnsy-hr fire &lt;name&gt;` hands over to Hermes, which asks you to type the profile’s name and then deletes the profile with its memory and sessions. What Hermes itself keeps outside a profile is Hermes’ own.

**Good to know.** We ran it with Hermes Agent v0.23.1. It connects straight to the catalog and does not use a proxy named in the environment, so on a proxy-only network it does not work. We ran it on Linux; not yet on Windows or macOS. It registers no tools and no hooks. It adds a chat command that can only search, show and list; hiring, updating and firing work at the terminal only. Who may send it a command is set by your Hermes Agent’s own settings. We have not tried it in a live gateway. It never updates itself: a new version arrives only when you install a newer commit. Use `hermes harnsy-hr update`, not `hermes profile update`, to update a hired employee: only the plugin’s own command checks the signature.

Source and full reference: [github.com/harnesy/hr-hermes](https://github.com/harnesy/hr-hermes)

## MCP: Claude Code, Codex and other clients

**What you get.** An MCP server at `https://hr.harnsy.dev/mcp` (streamable HTTP, no sign-in). Add it to your agent and ask in plain words: “Find an accountant on hr and install it in this project”. The server only reads: it cannot write to your disk, so it returns the employee as a list of files and your own agent writes them. Whether it asks you first is set by its own permission settings.

### Add it

Claude Code

```
claude mcp add --transport http hr https://hr.harnsy.dev/mcp
```

Codex

```
codex mcp add hr --url https://hr.harnsy.dev/mcp
```

OpenClaw

```
openclaw mcp set hr &#39;{&quot;url&quot;:&quot;https://hr.harnsy.dev/mcp&quot;,&quot;transport&quot;:&quot;streamable-http&quot;}&#39;
```

Hermes Agent

```
hermes mcp add hr --url https://hr.harnsy.dev/mcp
```

Then answer `n` to “Does this server require authentication?” and press Enter at “Enable all 4 tools?”

Another client

Add a remote MCP server (streamable HTTP, no sign-in) with the address above

We ran a full hire with Claude Code 2.1.322 and Codex 0.167.0. In OpenClaw 2026.11.3 and Hermes Agent v0.23.1 we added the server and saw its four tools; we did not run a hire through them. Another client needs remote MCP servers over streamable HTTP and a way to write files.

**Then** ask for an employee by what you need done. The agent searches, and the server tells it to show you the employee’s title, licence and notice before it writes. If your agent runs without permission checks, it writes without asking.

**What lands in your project (Claude Code).** The employee as a subagent in `.claude/agents/&lt;name&gt;.md` (start it with `claude --agent &lt;name&gt;`, or say “use the &lt;name&gt; subagent”), its skills in `.claude/skills/`, and its notice and casebook in `harnsy-hr/&lt;name&gt;/`. Whether Claude Code asks before a write under `.claude/` follows your Claude Code permission settings. For an agent that only reads files, you get one folder with `AGENT.md`: tell the agent “Read `&lt;name&gt;/AGENT.md` and work as that employee”.

**Plugin or MCP?** In OpenClaw and Hermes Agent we ran a hire with the plugin; the MCP server can be added there too. The plugin checks the catalog’s signature on your machine. Over MCP the files reach your agent as text over TLS, without the catalog’s signature; every answer names the SHA-256 of the bundle and of each file, so you can check that your agent wrote the files as the server sent them.

Source and full reference: [github.com/harnesy/hr-mcp](https://github.com/harnesy/hr-mcp)

## What is checked, and what is not

- The two plugins check on your machine, before anything is written: the catalog’s Ed25519 signature on its list of employees, that the list is current, the size and SHA-256 of the employee’s bundle, and the catalog’s signature on the bundle’s own list of files. Any failure stops the command with the reason, and nothing is written.
- The MCP server serves only a catalog release that passes the same checks on the server.
- A signature says the files are the ones the catalog published. It does not say an employee’s text or scripts are right for your purpose: read what you hire. Scripts that come with a skill are saved as plain files; the plugins never run them. Your agent may run them later, when it uses the skill: read them before you hire.
- What goes over the network: the plugins make `GET` requests to `hr.harnsy.dev` only (the list, its signature, the employee you asked for), with no account, no cookies and no search words: the search runs on your machine. Over MCP the server receives what your agent asks it: the search words and the employee’s id. What our server records of these requests is in the [hr.harnsy.dev privacy notice](https://hr.harnsy.dev/privacy).

This is how the plugins and the server are built; it is not a guarantee against bugs. The code is open and comes as is, under the MIT licence.

## Licences

The code of the three projects is under the MIT licence. The employees are not part of those repositories: each has its own licence, most often CC BY 4.0, and arrives with a `NOTICE.md` that names its author, licence, source and the works it is built on. Keep that file with the employee. If you pass an employee on, or something made from it, its licence says what must go with it: for CC BY 4.0, the credit in that file.

harnsy is not affiliated with or endorsed by OpenClaw, Nous Research (Hermes Agent), Anthropic, OpenAI or the MCP project; their names are used only to say what this works with.

- [Browse the employees](https://hr.harnsy.dev/)
- [Hire in harnsy itself](https://hr.harnsy.dev/#how)
