I have been evaluating devenv 2.0 and one noteable feature I am missing from my previous setup (a process-compose-flake / services-flake based setup) is tooling for my agents to interact with process compose api to fetch logs, restart servers, etc.
For the MCP, the one I'm using exposes these tools, I find start/stop process, list/get process, and get_process_logs are the most useful for the agent
└ mcp__process-compose__scale_process
└ mcp__process-compose__start_process
└ mcp__process-compose__stop_project
└ mcp__process-compose__get_dependency_graph
└ mcp__process-compose__restart_process
└ mcp__process-compose__list_processes
└ mcp__process-compose__get_project_info
└ mcp__process-compose__get_process_logs
└ mcp__process-compose__health_check
└ mcp__process-compose__reload_project
└ mcp__process-compose__get_process
└ mcp__process-compose__stop_process
the process-compose cli has a similar API, I'm using similar commands that I listed above in some skills:
~> process-compose process
Execute operations on the available processes
Usage:
process-compose process [command]
Available Commands:
get Get a process state
list List available processes
logs Fetch the logs of a process(es). For multiple processes, separate them with a comma (proc1,proc2)
ports Get the ports that a process is listening on
restart Restart a process
scale Scale a process to a given count
start Start a process
stop Stop running processes
I have been evaluating devenv 2.0 and one noteable feature I am missing from my previous setup (a process-compose-flake / services-flake based setup) is tooling for my agents to interact with process compose api to fetch logs, restart servers, etc.
For the MCP, the one I'm using exposes these tools, I find start/stop process, list/get process, and get_process_logs are the most useful for the agent
the process-compose cli has a similar API, I'm using similar commands that I listed above in some skills: