Docker Wts Build
Schedule long Docker Compose builds on Windows Task Scheduler so VS Code terminal timeouts do not kill your images mid-build.
Overview
docker-wts-build is an MCP server for the Ship phase that schedules Docker Compose builds via Windows Task Scheduler outside IDE terminal limits.
What is this MCP server?
- PyPI package docker-wts-build with stdio MCP transport
- Registers Windows Task Scheduler jobs for docker compose builds
- DWTB_PROJECT_DIR required; optional compose file, services, logs dir, task prefix
- Build logs default to {project_dir}/builds/logs
- Survives VS Code integrated terminal session limits
- MCP package version 0.1.2 on PyPI (docker-wts-build)
- Required env: DWTB_PROJECT_DIR
- Default logs path: {project_dir}/builds/logs
What problem does it solve?
Long Docker builds on Windows die when VS Code or other terminals time out, wasting time and leaving half-built images.
Who is it for?
Windows-based indie devs using Docker Compose who build heavy images from Claude Code or Cursor.
Skip if: Linux-only workflows, Kubernetes deploys, or teams without Windows Task Scheduler.
What do I get? / Deliverables
Compose builds run as scheduled tasks with configurable logs so agents can trigger reliable local image builds.
- Scheduled Task Scheduler jobs for compose builds
- Persisted build logs under configured logs directory
- Agent-triggered builds independent of IDE terminal lifetime
Recommended MCP Servers
Journey fit
How it compares
Windows Docker scheduling MCP, not a cross-platform CI pipeline or cloud build skill.
Common Questions / FAQ
Who is docker-wts-build for?
Solo builders on Windows who use Docker Compose and need builds to outlive VS Code terminal sessions.
When should I use docker-wts-build?
Use it in Ship launch prep when local image builds are long enough to hit terminal timeouts or when you want scheduler-backed repeat builds.
How do I add docker-wts-build to my agent?
Install docker-wts-build from PyPI, set DWTB_PROJECT_DIR (and optional DWTB_* vars), and register the stdio MCP server in your agent config.