A Model Context Protocol server with six memory tools, speaking stdio and streamable HTTP, over one SQLite file that lives where you put it. Everything below is the whole story — what it does, which apps it plugs into, and the honest limits — sentence for sentence.
For the people working out of a terminal. Tell Claude on Monday that you take your coffee black; ask Grok on Wednesday how you take your coffee. Same file. Two companies. One brain. It is a Model Context Protocol server with six tools — remember, recall, save a conversation summary, forget, stats, and a review pass for pruning — speaking both stdio and streamable HTTP, over one SQLite file that lives where you put it. Zero dependencies. Unzip, init, connect.
The privacy-maximum lane. Run it locally over stdio and the server is a process on your machine with your data on your own disk and nothing on a network. Run the HTTP door for web and phone apps and it sits behind a bearer token, on your disk or on a box you rent — your choice, and the README says exactly what each choice means.
The phone answer. Run the HTTP transport behind a tunnel or your own cloud box and add it as a custom connector.
The same six tools inside the coding agent you already have open, reading and writing the same local database file.
Point it at the HTTP endpoint. When an app supplies its name, the kit records it, so stats can show that one client wrote sixty entries and another wrote twelve. A name is a label the caller reports, not an authenticated identity, and a merged memory keeps one surviving label.
Run it on your machine, through a tunnel, or on your own cloud box — your account, your bill, your data.