Not a website. A site that runs.
Making, distributing, running, thinking — four pieces carried on one stage.
One engine, taking three forms.
Bundle, server and FlowHub aren't three competing products. They are three ways the same AppPlayer + MCP engine gets consumed — making, running, connecting.
An app that runs without being installed. One declarative spec becomes a living app — music, books, courses and tools published as serialised apps.
Put UI, knowledge and tools on top of a bundle and it runs as a finished service — homepage, database, chat, ERP. Sign-up, settlement and auth can be taken care of underneath.
A relay between local, embedded and cloud instances. Factory machines can be bound under one I/O standard — or the data can stay local while only the hub flows.
One runtime, every device.
The universal client that takes the UI and tools a server sends, puts them on stage, and runs them.
It renders the pages, widgets and actions an MCP server publishes, and a button press becomes a tool call. iOS, Mac, Windows, Linux, Web, embedded — the same client, a different stage.
The domain expert stands at the front.
Free for anyone — a making tool that starts at App Builder.
Build MCP server apps and bundle apps with App Builder, then stack the Knowledge, Ops, Book, Album and Course builders on top. The bundle is the universal app format — and the person who made it is the one the market is about.
Tools, strung into a flow.
AppPlayer's third face — calling the same MCP tools with no wrapper in between.
An outside model calls exactly the same tools, chaining quotes, lookups and device control into an automated flow. Where handing over full authority isn't acceptable, a layer of human confirmation and rollback stays in place.
Three markets, one stage.
One place to find MCP servers, bundles and FlowHubs — and put them on stage.
Servers that germinate into an app the moment they connect. Bundles that travel as one package. FlowHubs that reach the outside world. Search all three at once and stage any of them in a click.
One server, used from many surfaces.
Make an MCP server once and the same tools reach every surface. The four below are only the familiar examples — when a new surface appears, the server stays as it is.
It looks like a web page. Shareable URL, findable in search, catalogue intact.
https://mysite.appThe same server becomes a booking, quoting or support bot. The tools don't change.
chat: "book a meeting"Like an app, in a dedicated runtime. Kiosk, panel, control console.
app://mysite/opsCalls the same tools directly. An outside model needs no wrapper written for it.
model → mcp tool call+ kiosk · embedded · voice · widget · watch · in-vehicle terminal — the surfaces keep multiplying.
Turn every site into a server that runs.
Make it in Studio, find it in the Marketplace, and stage it with AppPlayer on any device.