Supported apps
The apps MDK ships and the routes each serves
Overview
A Gateway serves exactly the apps your stack declares in spec.apps[], and nothing else. Nothing here
auto-registers: an app contributes its routes only when a stack names it. Each app MDK ships lives in its own repository,
is offered through mdk onboard, and is declared by its package name (@tetherto/mdk-app-<name>).
The Gateway serves an app's routes under /apps/<name> unless the app's spec.apps entry sets mount; mount: / serves them
at the Gateway root.
Route tables
| App | Package | Repository | Mount |
|---|---|---|---|
agent | @tetherto/mdk-app-agent | mdk-app-agent | /, because its UI calls /agent/sessions… at the Gateway root |
demo | @tetherto/mdk-app-demo | mdk-app-demo | The default, /apps/demo |
Each repository's README carries the app's route table, configuration, and errors.
Next steps
- Declare an app in your stack: the manifests, controllers, and how a stack runs them