Schedule Docker builds via Windows Task Scheduler — survives VS Code terminal timeouts
The publisher's own command. Not a PlugMCP endpoint.
uvx docker-wts-build==0.1.2
DWTB_PROJECT_DIR=<value> DWTB_COMPOSE_FILE=<value> DWTB_CUSTOM_SERVICES=<value> DWTB_LOGS_DIR=<value> DWTB_TASK_PREFIX=<value> DWTB_TASK_TIMEOUT_MS=<value> DWTB_MAX_TASK_AGE_DAYS=<value> claude mcp add io.github.artemdruzhininad-star-docker-wts-build -- uvx docker-wts-build==0.1.2
Run in a terminal.
{
"mcpServers": {
"io.github.artemdruzhininad-star-docker-wts-build": {
"command": "uvx",
"args": [
"docker-wts-build==0.1.2"
],
"env": {
"DWTB_PROJECT_DIR": "<value>",
"DWTB_COMPOSE_FILE": "<value>",
"DWTB_CUSTOM_SERVICES": "<value>",
"DWTB_LOGS_DIR": "<value>",
"DWTB_TASK_PREFIX": "<value>",
"DWTB_TASK_TIMEOUT_MS": "<value>",
"DWTB_MAX_TASK_AGE_DAYS": "<value>"
}
}
}
}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchSchedule Docker builds via Windows Task Scheduler — survives VS Code terminal timeouts
README is not crawled yet. No repository on file.
No tool list yet. Remote servers get one after the first health check.