Quickstart
Pick the door that matches what you have and what you want to build with MDK
See it work
Run a mining site
You want to see MDK working. One command brings up Workers, mock hardware, a Gateway API, and a live browser dashboard⏱️ <5 min, ends in a dashboard
See a plugin serve your data
The Gateway serves no data routes of its own. Watch one mounted plugin answer an HTTP request with live telemetry⏱️ <2 min, ends in JSON from your own route
Build it
Three things you can author. A plugin gets your data out, a Worker gets your hardware in, and an agent generates the interface.
Build a Gateway plugin
Serve your own data. Write a manifest and a controller, then mount them so the Gateway answers the routes your app needsEnds in your own mounted route
Build a Worker
Your hardware, firmware, or data feed is not supported yet. Ship a Worker package and its contract from your own repoEnds in a Worker package
Build with an AI agent
You drive Cursor or Claude. Wire your IDE once, then build dashboards from plain-language prompts⏱️ ~12 min, ends in a scaffolded page
Other starting points
Build an endpoint and a dashboard
The whole vertical slice from an empty directory: one Worker, one Gateway route, and one React page⏱️ ~15 min
Wire an existing React app
You already have a React app and want to hand-wire MDK into it rather than generate pages⏱️ ~3 min to install
Deploy a site
You know what you are shipping and need a topology: one process, supervised services, or the full Worker fleetEnds in a running deployment
Next steps
- Understand how the pieces fit together: the runtime stack and its deployment modes
- Learn the vocabulary: Kernel, Worker, Gateway, manager, and thing
- Browse every runnable example: what each one demonstrates and how to start it