The problem: too many clients, too few discovery hooks We expose Supabase Edge Functions as MCP (Model Context Protocol) servers. The clients that hit them are heterogeneous — Claude Desktop, Codex CLI, Cursor, VS Code Continue, a couple of in-house browser extensions. None of them ship with a hard-coded "use WorkOS AuthKit, scope is tool:ai_chat, audience must contain urn:jibun:tool:<tool>" rec
I like servers. Not in a "let me spend Saturday hand-tuning nginx" way. More in a "this $6 VPS is sitting right here and could probably run half my side projects" way. The weird part is that deploying to one still feels more complicated than it should. For a lot of small and medium web apps, the app itself is not the hard part. The annoying part is everything around it: building the app getting it
A Fully Native, Dependency‑Free Web5 Case Study TL;DR: This case study demonstrates how the Ascoos OS Kernel 1.0.0 performs OAuth2 authentication, event‑driven processing, torrent file creation, and secure P2P upload using raw sockets — all without frameworks, external libraries, or middleware. 🔗 Full source code: https://github.com/ascoos/oauth2-torrent-upload Modern decentralized systems