Own your memory

Your portable
memory

One memory that follows you across AIs.

Connect your agent
instruction ›
claude mcp add --transport http waku https://api.waku.one/mcp
Local-firstPython 3.11+SQLite No accountNo telemetry~2,000 LOCv0.4.2
[01]
Problem

Your context outgrows your tools.

Months teaching your tools how you work. Switch tools and you start from zero.

[02]

Giulio Camillo · the Theatre of Memory, 1530s Giulio Camillo designed this wooden amphitheatre so that everything you knew had a place you could walk back to. He never finished it. The machine it needed did not exist. 500 years on, it does.

Waku memory

One memory across every AI.

Every AI knows only a fragment of you. Waku memory builds the full profile of you.

[03]
Structure

Structure forms in motion.

Stay visible No black box. Watch memory take shape as it happens.
A Chladni figure: sand on a bowed plate runs off whatever moves and settles where it holds still, so the same note always draws the same one
Stay traceable Never drifts. Every action stays on the record.
data-cell="1.0" data-density="1.6" role="img" aria-label="Odin as an old one-eyed wanderer under a wide drooping hat, holding a spear, with one raven perched on his shoulder and another flying in with its wings spread, drawn as a cloud of ink grains."> Huginn and Muninn — thought and memory — fly out at dawn and are back by dusk, so Odin never works from yesterday’s world
Always current It learns and grows with you. What your agent reads is who you are now.
Early access

Your memory palace.

A memory that stays yours.

MCP server
https://api.waku.one/mcp

Connect Claude Code

Two steps. The second one happens in your browser, not your terminal.

  1. Run this. It writes the server into ~/.claude.json — no file to create by hand.

    claude mcp add --transport http waku https://api.waku.one/mcp
  2. Open Claude Code. The first time it reaches Waku a browser opens and you sign in here; the token is stored by Claude Code, so there is nothing to paste back.

That is the whole setup. To feel it working, say “remember that I prefer tabs” in a session — what an agent writes shows up on your account here. To check first instead, claude mcp list should show waku, connected.

Connect Waku Agent

Three steps. The browser opens on its own at the end.

  1. Install the harness, with the MCP extra. Without the extra it runs, but cannot reach a remote server.

    pip install 'waku-agent[mcp]'
  2. Create .waku/mcp.json in the folder you run Waku from, with exactly this in it.

    {"servers":[{"name":"waku_memory","url":"https://api.waku.one/mcp","oauth":true}]}
  3. Start it. A browser opens the first time and you sign in here; the token is kept in .waku/mcp-auth/, so there is nothing to paste back.

    waku

That is the whole setup. waku dashboard opens the same Waku in a browser cockpit instead of the terminal — two doors, one memory.