Memory for teams and their agents
It is in a Meet call, a Trello card, an email nobody re-reads. OneBrain turns all of it into one memory: your team searches it, your agents call it, and every answer arrives with its source.
Your email domain picks which organization you land in.
Sound familiar
Decisions
from Trello cards, notes and coding sessions
Meetings
from Meet transcripts, Gmail and Calendar
People
ranked by the facts that prove it, not job titles
Every one of these was answered once already. Somebody on your team is about to answer it again — or an agent is about to guess.
Why it answered
Other tools hand you ten results and let you guess. OneBrain shows which search found each one, where it ranked, and what moved it — so you can tell a real match from a lucky one.
When it changes
Change a price, a plan or an owner and the old fact is retired — search stops returning it, instead of leaving it one row below the new one waiting to mislead somebody.
Nothing is lost: you keep the trail of what it said, when it changed, and what replaced it.
How it works
Gmail, Meet transcripts, Calendar and Trello land in a log that is only ever added to — along with the coding sessions your team runs and any of 1,200+ other tools you connect. Nothing gets rewritten. Nothing gets thrown away.
Each one becomes single facts, tied to the people and projects they name. API keys and passwords are stripped before anything is saved.
Ask in the browser, or let Claude ask for you. Same answer either way, with the same explanation attached.
Your data
You are about to point this at everything your company writes down. The first question is always the same one, so here is the answer.
Access is read-only, per member, and revocable at any time from your Google account or from OneBrain’s Sources page.
OneBrain’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We never sell your data or use it for advertising.
Wire it up
An agent with tools and no memory will confidently tell you something your team decided against in March. Point it here and it checks first — same URL and token in your terminal, your editor, or a job running at 3am.
$ claude mcp add --scope user --transport http onebrain \
__MCP_URL__For everyone on the team who works in the terminal. Sign in with Google on the first call; hooks make memory automatic — nobody has to remember to say “remember this”.
{
"mcpServers": {
"onebrain": {
"type": "http",
"url": "__MCP_URL__"
}
}
}Any MCP client takes the same URL and signs in the same way. Nothing about OneBrain is specific to one harness.
$ curl -s __API_URL__/v1/recall \
-H "Authorization: Bearer $ONEBRAIN_TOKEN" \
-H 'Content-Type: application/json' \
-d '{"query":"why did we not adopt cognee"}'For agents that never touch a laptop — CI jobs, cron, a service in your cluster. Plain REST with a personal token from Settings, so a shell hook is one curl.
Your email domain picks which organization you land in.