MDK Logo

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.

These apps are deliberately slim demonstrations of a stack serving routes end to end, not reference architecture. The apps guide is the pattern to build your own app on.

Availability

Install an app from its repository with mdk add app github:tetherto/<repository>, which writes its spec.apps entry, mount included. mdk onboard installs them from the same repositories. The browser half of the agent app, the @tetherto/mdk-ui-agent panel, is on npm and renders without the app.

Route tables

AppPackageRepositoryWhat it demonstratesAvailabilityMount
agent@tetherto/mdk-app-agentmdk-app-agentA chat API with SSE message streams and approval round-trips for write toolsPublic repository, not on npm/, because its UI calls /agent/sessions… at the Gateway root
demo@tetherto/mdk-app-demomdk-app-demoA read-only fleet summary and history read through @tetherto/mdk-clientPublic repository, not on npmThe default, /apps/demo

Each repository's README carries the app's route table, configuration, and errors.

Next steps

On this page