Before last week in order to use Founders OS required editing a config file by hand and running a command. That's a fine start for other MCP developers. It's a wall for the actual target user, a founder who just wants their AI assistant to know their business and improve decisions with that information.
So we packaged the whole server as a self-contained installable bundle. No terminal, no manual JSON editing, just typed fields for your database credentials in an install dialog.
We also submitted it to a public MCP registry so people can find it without already knowing our repo name. Nothing about the product changed. Same server, same tools, same self-hosted data model, your own database, nothing routed through us. What changed is how many steps stand between someone hearing about it and actually running it.
Our Site:
www.foundersmcp.com
Open Source Code:
github.com/OurThinkTank/founders-os
Curious what other solo builders found was the actual friction point once they looked, versus what they assumed it was going in.
The shift from “can install it” to “will actually install it” is a meaningful distinction. Curious what changed in user behavior after removing that setup friction.