Gateway how-to guides
Task guides for running and extending the MDK Gateway
Overview
The Gateway is a container that hosts plugins and delivers an HTTP interface for your frontend: each plugin builds its own @tetherto/mdk-client from its context. These guides cover how to run it and extend it with the plugin system.
An AI agent reaches MDK over MCP, not the Gateway's HTTP surface directly — served either by a standalone
@tetherto/mdk-mcp process, or by the Gateway itself when it auto-generates tools from a mounted plugin's routes.
If Gateway, Kernel, or plugin are unfamiliar, read terminology first. For the full developer model — extension, data access, auth design — read the Gateway concept page.
Choose a guide
| Goal | Guide |
|---|---|
| Start the Gateway for the first time | Run the Gateway |
| Use built-in plugins or build your own | Gateway plugins |
| Stop Kernel, Gateway, and Workers cleanly | Tear down MDK services |
| Operator in the loop: submit and approve write actions | Submit and approve write actions |
Next steps
- Understand the Gateway as a development surface
- Read the Gateway API reference
- Choose a deployment shape
- Give an operator a chat interface to the fleet by deploying the operator agent behind the Gateway