Looks like a notebook. Built like a backend.
Pages, typed tables and files your team writes in, with an MCP endpoint and a REST API your agents write to. Same data, live, in both directions.
Four layers, one workspace.
The page you write in sits on the same records the API serves. There’s no export and no second system to keep in sync.
The underside is for agents.
Point an assistant at one URL. There’s no API key to make: it signs in with OAuth and you approve it. It sees the same workspace as JSON and can never do more than you can.
Agents write. You watch it land.
Writes over MCP or REST show up in open pages as they happen. Each one is checked against the table’s fields, attributed, and logged in the activity feed.
One table, eight ways to look at it.
Change a value in one and every other view already has it.
- Table
- Board
- Gallery
- List
- Feed
- Calendar
- Timeline
- Map
Three ways in. Each knows its limits.
What separates them isn’t the protocol. It’s how much of the person’s account they reach.
Claude, Cursor or your own agent, acting as a person.
A tool someone connects to one workspace.
Something the workspace owner runs themselves.
The parts people use every day.
Write together in real time, with tables, math, drawings and files inline. Pages you pin keep working offline.
Typed fields, relations and formulas. Every view reads the same records.
Delete a page and the files only it used are archived with it. Restore it and they come back.
Threads on a page or on one field of a record. An agent can post as itself or on your behalf.
When something changes, send a webhook or a push notification.
Full text across titles and page bodies, including notes written on records, and forgiving of typos in titles.
One URL. No API key.
Any MCP client finds the sign-in on its own. You approve it once in the browser.
https://aurochs.oxen.dev/api/mcp$ claude mcp add --transport http aurochs https://aurochs.oxen.dev/api/mcp