mcp-daemonize

mcp-daemonize is an MCP server that lets AI agents manage long-running processes (daemons) directly from the MCP interface. It provides tools to start a daemon, stop it, list all active daemons, and stream real-time logs from running daemons. This enables autonomous debugging and development workflows where an agent can spin up servers (like Vite or Next.js), monitor their output as they run, and tear them down when finished. With these capabilities, agents can orchestrate complex development tasks without manual intervention, maintaining visibility into output and status throughout the lifecycle of a daemon.

Prerequisites:

• Docker installed and running (if using the provided Docker-based run method).
• Alternatively, a Go toolchain if you prefer building from source.

Install via Docker (recommended for quick start):

1. Ensure Docker is installed and running.
2. Pull and run the MCP daemonize container as needed (the MCP host can connect to this service once running).

Option A: Run with Docker (example placeholder image name):

docker run -d --name mcp-daemonize -p 8080:8080 mackee/mcp-daemonize:latest

Option B: Build from source (Go 1.24.2+ required):

go install github.com/mackee/mcp-daemonize/cmd/mcp-daemonize@latest

Configure your MCP host to point to the daemonize service (see the example in the README for how to add the server to mcp.json).

Notes and tips:

• If you run via Docker, ensure the container exposes or maps any required ports for MCP to communicate with the daemonize service.
• The daemonize tools (daemonize_start, daemonize_stop, daemonize_list, daemonize_logs) expect a daemon name and, for start, a command array and working directory. Ensure absolute paths for workdir and properly escaped command arguments.
• Logs are streamed for real-time debugging; use daemonize_logs with a suitable tail size to observe recent activity.
• When stopping daemons, consider gracefully stopping long-running servers to avoid port or resource leftovers.
• If you encounter permissions issues on Go binaries, ensure the binary has execute permissions (chmod +x) and is located in a PATH directory on the host running the MCP server.
• For production, consider running mcp-daemonize in a container and managing access controls to prevent unauthorized daemon manipulation.