Uscreen’s biggest creators were starting to outgrow its storefronts, and vibe coding had made a custom build cheap enough for any of them to leave. Rather than wait for the churn, Uscreen ran a scoped R&D project with us to test one hypothesis: give those creators a supported way to build on top of the platform instead of away from it, and they’ll stay. Three months after kickoff, we have a headless SDK in beta that supports both storefront architectures: everything in the browser, or a thin server between the browser and the platform. It’s delivered as npm packages: a typed client generated from the OpenAPI spec, React storefront components, a Next.js adapter that keeps the viewer’s session on that server, and a localization engine.
Meanwhile, creators of every size now run their day in front of an AI agent and expect it to reach into the system their business runs on. So Uscreen asked us to take its MCP prototype further: a TypeScript package with 14 read-only tools that took five steps to install. The code was fine, the install wasn’t, so together with Uscreen’s engineers we made it a remote server. That belongs next to the users and the data, inside the Rails monolith, and any creator now connects by pasting one URL: OAuth 2.1 with PKCE and dynamic client registration on Doorkeeper, 57 read and write tools gated by scope, destructive tools that dry-run by default, and no session store, so any request can land on any pod.
