Getting started
Never used MicroLab? What it is and your first scenario in 5 minutes. Start here
Launch your microservices locally, friction-free
MicroLab launches several microservices at once with the communication between them already resolved —local, cloud or mock— so you can test complete flows without setting up infrastructure or reconfiguring URLs by hand.
This guide covers the whole product and is designed both to be read and to look up “how do I X”: each page answers a specific question.
Where to start
Section titled “Where to start”Concepts
The mental model: micro, scenario and dependencies, resolved as local, cloud or mock. See concepts
The desktop app
How everything is done in the app, section by section. Open the app guide
Workflows
Task recipes: clone and launch, mock a dependency… See workflows
CLI reference
The same from the terminal, for scripts, CI and agents. Go to the CLI
Automation & AI
MCP server, copilot and /llms.txt with the whole guide in a single document. Automation & AI
The five surfaces
Section titled “The five surfaces”MicroLab is not just the app. The same functionality is offered through five front ends that share the same engine, so they never diverge:
| Surface | What for |
|---|---|
| Desktop app | Normal, visual use. |
CLI microlab | The same from the terminal: scripts, CI, agents. |
| Control server | Local HTTP API with a token; what the CLI uses to talk to an already-running engine. |
| MCP server | Curated surface for AI agents (Claude Code, Cursor…). |
| Copilot | Chat inside the app, with the same tools as the MCP. |
The app is free; the CLI, the MCP and the copilot are paid capabilities.