digitopia.app
The business OS we run Labs on, with its own MCP server.
Problem
Every tool sat in its own box - the tracker, the notes, the client records - and none of them could tell Claude anything. Each conversation started from nothing, and the context had to be retyped or re-explained. digitopia.app was built to be the second brain: one place holding every project, so a conversation in Claude already knows what is running, and Claude Code knows it too the moment a repo is opened.
What we built
A business OS with an MCP server of its own: projects, tasks and deliverables, plus the brand and business context Claude reads before it writes anything. Per-project operating rules are generated from the database, so claude.ai and Claude Code cannot drift apart. The connector exposes around ninety tools, and `whoami` returns the team, the active brands and the connector revision the session is actually talking to.
Stack
Next.js and Supabase, with its own MCP server.
Timeframe
A couple of days before it replaced ClickUp, then developed continuously for three months with new functionality each week.
What it does now
Live and in daily use, and it has absorbed several tools it replaced - ClickUp first, then Cal.com and WeTransfer among others. It is the record of what happened: work that is not on it did not happen, and every session in every repo orients against it before it starts.