Same controls as the dashboard
List applications, start and stop processes, read logs, inspect ports. The UI and the agent call the same operations — they cannot disagree about what is running.
Desktop app
Define an application from several repositories, start the whole thing with one click, watch every process, and hand the same controls to an AI agent over MCP.
Loading releases…
Paddock owns configuration, process lifecycle, logs and ports. The agent brings the intelligence — so “the backend died, restart it and tell me what the stack trace said” stops being your job.
List applications, start and stop processes, read logs, inspect ports. The UI and the agent call the same operations — they cannot disagree about what is running.
/mcp
Point Cursor or Claude at http://127.0.0.1:4599/mcp. The desktop app
serves the same URL as a checkout, so an agent already configured keeps working.
You define the application, the repositories and the commands. Paddock runs them and exposes the MCP surface. The agent decides what to do with a crash.
Published GitHub releases only. Drafts stay off this page until you publish them.