one-brain

Description

**Shared, permanent memory for a team working with coding agents.** Every session starts from zero and forgets it all on close. One Brain fixes that, and not just for you: what one teammate records, everyone gets at the start of their next session, with the name and the date still attached. Someone asks their agent about a service they didn't build: > **why does the payments worker stop retrying after 2 attempts?** > > That cap is deliberate, not a leftover. It was set after the duplicate-charge incident in March. > > *"Two retries on payments, hard stop. At five we double-charged 40 customers in one night. If a queue genuinely needs more, it comes through me."* > Priya Raman, Platform, Mar 12 That answer came out of a teammate's session six months earlier. Nobody wrote a document for it. ## What makes it different Nobody writes documents. Memory gets recorded when you close a topic, so there is no form to fill in and no wiki to keep alive. Every answer carries a name and a date, so you stop reconstructing intent from commit messages a year later. Every service, client or person is a tag. Ask about one and you get everything the team wrote about it, whichever teammate wrote it. The server itself runs no model. It stores and retrieves, and the judgment stays in your agent. ## Getting in Sign in with Google at [onebrain.prophet.lat](https://onebrain.prophet.lat) and your brain exists immediately. No form, no card, nothing to approve. Free during the open beta. ## Your data One Brain stores what your team decides and learns, not your repository. It does not read your source code. Every brain is isolated from every other one, you can see and edit every entry, and you can export all of it whenever you want without asking anyone.

Community Metrics

Categories

• mcp

Tags

• mcp
• smithery

Capabilities

• Remote MCP server

Information