Reef MCP server

reef

Shared, living memory for you and the people you share your life with — and for the AI assistants you both already use.

Your assistant forgets you between conversations. reef gives it a memory that lasts — and one your partner, your household, or your project can share.

different conversation, it still knows.

• Ask once. Tell your assistant the boiler is a Vaillant. Next month, in a

only what you deliberately put there.

• Share on purpose. Your private notes stay private. A shared cove holds

remote MCP connector, not another chat app.

• Bring your own assistant. Claude, ChatGPT desktop, or Codex. reef is a

Try it

You need an invitation — reef is invite-only. Once you have one:

uv tool install reef-cli   # or: npm install -g @haai/reef-cli
reef login
reef load-index

To use it from an assistant instead, add https://reefwith.me/mcp as a remote MCP connector and sign in with the address you were invited on.

In Claude Code, the plugin carries that connector and three commands with it:

claude plugin marketplace add diepzee/reef
claude plugin install reef@haai

/reef:recall answers from memory rather than from guesswork, /reef:remember files something away, and /reef:whats-new reports what the other people's assistants have been writing.

There is a browser app too, at reefwith.me/app. Use it to read and edit pages without an assistant.

How memory is organised

Memory lives in coves. You get one private cove the first time you sign in. You can create any number of shared ones — a household, a school circle, an accountant, a small project.

You name shared coves for yourself. Your name for a cove is yours alone. Two households can each have a family without either knowing the other exists, and nobody can take a name from anybody else.

Sharing is deliberate and permanent. Moving something out of your private cove takes two steps. First your assistant shows you the exact text and names everyone who will be able to read it. Only then does it move.

Writing private content into a shared cove any other way is refused — not discouraged, refused. And there is no un-sharing.

How your assistant reads it

reef loads an index first, then pages — the LLM Wiki pattern, adapted for shared, permissioned memory.

path, title, tags, and a one-line description. No page bodies.

1. The assistant calls load_index and gets a map of every page it may see:

that with read_pages.

1. It reads the map, decides what this conversation needs, and fetches only

what to read, search_pages matches words inside page bodies — and because it runs under the same row-level security as every read, a search can never surface a page its caller could not open.

1. It fetches again as the topic moves. When the map alone cannot settle

The index is rebuilt from the database on every call, so it cannot fall out of date.

How your assistant writes it

Shortened. The full README is on GitHub.