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.
Availability
Install an app from its repository with mdk add app github:tetherto/<repository>, which writes its spec.apps entry,
mount included. mdk onboard's catalog installs by package name from the registry, so selecting an app there fails until
it is published. The browser half of the agent app, the @tetherto/mdk-ui-agent panel, is on npm and
renders without the app.
Route tables
| App | Package | Repository | Availability | Mount |
|---|---|---|---|---|
agent | @tetherto/mdk-app-agent | mdk-app-agent | Public repository, not on npm | /, because its UI calls /agent/sessions… at the Gateway root |
demo | @tetherto/mdk-app-demo | mdk-app-demo | Public repository, not on npm | 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
- Render the agent chat: the npm package that pairs with the
agentapp, and what it shows without one