Launching today

drobek

Launching today

Open-source MCP hosting for apps your coding agent builds

5 followers

Open-source MCP hosting for apps your coding agent builds

5 followers

Visit website

Drobek gives Claude, Codex and Cursor an MCP loop to create, compile, preview and publish browser apps. Every write creates an immutable version and returns esbuild errors in the same response. Add auth, data, files, forms, email and controlled API calls through server-side modules. App code runs in the browser; secrets stay with the server. Use drobek.app or self-host the AGPL-3.0 core.

Free Options

Launch tags:Open Source•Developer Tools•GitHub

Launch Team

Maker

📌

Hi Product Hunt! I'm Tomáš, the maker of drobek. I kept building small browser apps with coding agents, then leaving them on localhost. The app worked. Giving it to a colleague meant setting up hosting, access rules, secrets and deployments. So I built a place the same agent could publish to. Drobek gives the agent a short MCP loop: create_app → write_files → preview → publish Every write creates an immutable version and returns esbuild errors in the same tool response. The agent can fix them on its next call. Publishing has its own token scope and happens only when I ask. I keep using my coding agent and model provider; drobek doesn't sell model tokens. Backend features come from modules: auth, data, forms, email, proxy and files. For example, the proxy can call an allowed upstream API and inject credentials on the server, so the app doesn't need the secret in its browser code. I also put a hosting tycoon game on it. Building a hosting platform, then using it to publish a game about running a hosting company, was probably inevitable. 😅 Try the game: https://drobek-tycoon.drobek.app/ See the proxy in use: https://pokedex.drobek.app/ The public core is AGPL-3.0 and runs on your own server. The hosted service has a free plan with limits. Your model provider bills model usage, and self-hosting still comes with infrastructure costs. A boundary worth knowing: app code runs in the browser. The backend modules are trusted code installed by the operator. Drobek doesn't run arbitrary agent-written server code or background workers. I'd love feedback on the boundary between agent-written browser code and operator-installed backend modules. And if you already have a small app stuck on localhost, what stopped you from putting it online?

Report

16d ago

Maker

Small launch-day update: the first technical question I keep coming back to is what happens when a browser app needs an API key.

I made a 36-second demo with the public Pokédex:
https://youtu.be/EeUG2dwL4qI

The agent registers one upstream with the allowed methods and path prefixes. An admin confirms it. The owner enters the secret in the dashboard. The app then calls it through `drobek.proxy.fetch()`.

The key stays on the drobek server. The browser and the coding agent never receive it.

You can try the Pokédex here:
https://pokedex.drobek.app/

This is the boundary I would especially like feedback on: browser code written by the agent, trusted backend modules installed by the operator. Which API would you try first?

Report

2h ago

Maker

📌

Report

16d ago

Maker

Report

2h ago