Get API key

Integration

Memory for OpenClaw agents

This page shows how to add Harny memory to an OpenClaw setup through the Harny MCP server. Harny keeps dated memories for each person, so a changed value with a newer timestamp becomes the current value and the earlier value stays answerable by date.

Jump to the code

On this page

What Harny adds

  • Which value is current. Harny keeps dated memories, so a changed value with a newer timestamp becomes the current value.
  • When a fact happened. Harny stores each memory with an occurrence time, so you can ask what was true on a given date.
  • One person's memory. Harny keeps each person's memory separate, and a key that belongs to one person scopes every call to that person.

The pattern: the Harny MCP server

Add the Harny MCP server to your OpenClaw setup. The key belongs to one person (fsk_), so every call is scoped to that person. Call describe to list the tools that key can reach.

Calls are scoped to the key's user.

export HARNY_USER_KEY=fsk_...   # the person's key, from your Harny app

openclaw mcp set harny '{"url":"https://api.harny.ai/v1/mcp/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer ${HARNY_USER_KEY}"}}'
openclaw mcp probe harny

What the tools return

The server lists the tools your key may call. A person's key (starts with fsk_) reaches the memory tools for that person only.

  • assemble_context is the Recall Memory tool. It reads for the person whose key you hold.
  • ingest_text is the Ingest Memory tool. It writes into that person's memory.
  • describe lists the tools the key may call.

When to use which

  • Use OpenClaw's own state for what OpenClaw manages itself.
  • Add Harny when the assistant needs memory that is dated, that a person owns, and that can answer what was true on a given date.

Frequently asked questions

Is a package needed?

This page uses the Harny MCP server, so it does not need a separate Harny package. The Memory API is available over HTTP from a server, using the app key or a user key.

Where does the user id come from?

The user id comes from your own app's sign-in. Your server sends it in the X-Harny-User header with the app key. A user key (fsk_) names its own user and needs no X-Harny-User header.

Keep reading

Go on. Get Harny.

The first 500 monthly-active end users are free for good. Create an app key and make your first call in minutes.

Get API keyRead the docs