---
title: Hermes
description: Integrate Treeship with Hermes agents via skill file or MCP server.
---

import { Callout } from 'fumadocs-ui/components/callout';
import { Steps, Step } from 'fumadocs-ui/components/steps';

Hermes agents support two integration methods: a skill file (instruction-based) and an MCP server (tool-call interception).

## Method 1: Skill file

<Steps>
<Step>
### Install Treeship CLI

```bash
curl -fsSL treeship.dev/install | sh
treeship init
```
</Step>
<Step>
### Install the Treeship skill

```bash
curl -sL https://raw.githubusercontent.com/zerkerlabs/treeship/main/integrations/hermes/treeship.skill/SKILL.md \
  -o ~/.hermes/skills/treeship.skill/SKILL.md --create-dirs
```

The Hermes agent reads the skill and follows the instructions to wrap commands, set env vars, and manage session lifecycle.
</Step>
</Steps>

## Method 2: MCP server

Add Treeship as an MCP server in your Hermes config:

```yaml
# ~/.hermes/config.yaml
mcp_servers:
  treeship:
    command: npx
    args: ["-y", "@treeship/mcp"]
    env:
      TREESHIP_HUB_ENDPOINT: "https://api.treeship.dev"
```

This intercepts every MCP tool call and creates signed artifacts + session events automatically.

## What appears in the receipt

| Section | Skill file | MCP server |
|---------|-----------|------------|
| Commands | Via `treeship wrap` `[AUTO]` | Not applicable |
| Tool calls | Not applicable | Every MCP tool call `[AUTO]` |
| Model/cost | Via env vars `[EXPLICIT]` | Via env vars `[EXPLICIT]` |
| File operations | File snapshot diff `[AUTO]` | Not applicable |
| Handoffs | Via `treeship session event` `[EXPLICIT]` | Via `treeship session event` `[EXPLICIT]` |

<Callout type="info">
**Integration status**: Skill file and MCP server packages are ready. Full end-to-end testing with a live Hermes server is pending. If you test it, please report results at github.com/zerkerlabs/treeship/issues.
</Callout>
