Skip to main content
Recipes are task-oriented: each one starts with a goal you can name (“connect HyphaeDB to Claude Code”, “erase an agent’s data”), gives the shortest path to it, and links out to the reference pages for the details. They assume you’ve done the quickstart — a server running and an API key in hand. If you’re looking to understand a subsystem rather than do a task, start with Core concepts or the Operations pages instead; recipes are the how-to layer on top of those.

​
The cookbook

Connect to Claude Code (MCP)

Wire HyphaeDB in as an MCP memory server an agent calls as tools.

Route knowledge with beacons

Give an agent standing interests so relevant memories gossip to it.

Tune how far a memory travels

Use salience and cell type to control propagation reach.

Watch a memory propagate

Stream propagation live from the Topology Observatory.

Erase data with a certificate

Run a compliant, audited erasure and keep the receipt.

​
The recipe format

Every recipe follows the same shape, so you can scan it fast:
  • Goal — one sentence: what you’ll have when you’re done.
  • Prerequisites — what must already be true (usually: server up, a key, sometimes an admin key).
  • Steps — the shortest correct path, copy-pasteable.
  • See also — the reference pages for the full surface.
Have a task that isn’t here yet? The SDK guides, the MCP tools, and the Operations reference cover the full surface these recipes draw from.