Skip to content
Hoard Hoard

OpenClaw Setup

This guide covers connecting OpenClaw to Hoard via a bundled skill bridge.

Quick Setup

  1. Ensure Hoard server is running

    Terminal window
    hoard serve

  2. Run the setup command

    Terminal window
    hoard setup --openclaw

  3. Restart OpenClaw

  4. Test the connection Use hoard_client.py search "test"

Remote Hoard Server

If Hoard runs on another machine:

Terminal window
hoard setup remote --url https://hoard.example.com --token hoard_sk_... --openclaw

The generated OpenClaw config stores the base URL in HOARD_URL; the client appends /mcp automatically.

What Gets Installed

The setup command creates:

~/.openclaw/skills/hoard/
├── SKILL.md
├── scripts/
│   └── hoard_client.py
└── README.md

And updates ~/.openclaw/openclaw.json with token + URL.

Available hoard_client.py Commands

CommandDescription
search <query> [--limit N]Search indexed content
get <entity_id>Get full entity content
memory_get <key>Retrieve stored context
memory_put <key> <content> [--tags ...]Write memory
sync [--source <name>]Trigger sync
inbox_put <content> [--title ...] [--sync-immediately]Write to inbox

Examples:

Terminal window
{baseDir}/scripts/hoard_client.py memory_put "project.key" "Remember this"
{baseDir}/scripts/hoard_client.py sync --source inbox
{baseDir}/scripts/hoard_client.py inbox_put "Persist this note" --title "Note" --sync-immediately

Verifying the Connection

Terminal window
hoard setup --verify

The verify command checks file existence and server reachability.

Host Mode Only

Troubleshooting

Skill not found

  1. Check skill folder: ls ~/.openclaw/skills/hoard/
  2. Re-run setup: hoard setup --openclaw

Connection refused

  1. Ensure server is running: hoard serve --status
  2. Verify HOARD_URL in ~/.openclaw/openclaw.json

Authentication errors

  1. Verify apiKey in ~/.openclaw/openclaw.json
  2. Re-run setup: hoard setup --openclaw

Next Steps