I spent 2 weeks in the hospital right after launching. Here's what happened to my MVP.
I’ve been completely MIA for the last two weeks due to an unexpected hospital stay. It was a rough time, and as a solo founder, my biggest anxiety was abandoning my MVP (MCP Studio) right as it was gaining traction from my last dev log here.
But this is why we build SaaS, right?
I logged into my Firebase and Render dashboards today, bracing for crashed servers or angry users. Instead, I saw that developers had been quietly using the app to turn their OpenAPI specs into managed MCP servers the entire time I was in a hospital bed.
I was digging through the use cases, and people are building some wild agentic workflows. One user pruned down the Stripe API so they could issue refunds directly from Claude Desktop. Another used the PII Redaction toggle to securely analyze patient booking data without leaking names to the LLM.
It was an incredible morale boost to return to. I'm officially back at my desk, feeling much better, and ready to start shipping updates again.
If anyone else is stuck in "Boilerplate Hell" trying to connect APIs to Cursor, I'd love for you to try out the tool!
Link:
https://eleayuen-png.github.io/OpenAPI-to-MCP-Converter-MVP/
Good sign that usage continued while you were away.
The thing I’d be careful with is not over-reading interesting technical use cases as proof of repeatable demand.
“Someone built something cool with it” and “a clear painful workflow keeps pulling people in” are close, but not identical.
Feels like the next decision is less about shipping features and more about which workflow MCP Studio should become obviously useful for first.