g0t4/mcp-server-commands

Instead of mode=executable / mode=shell ... make mode implicit off of:

• command_line implies mode=shell
• command+args implies mode=executable
  And really that all dictates whether or not spawn options have shell set to interpret the command_line vs just execute the command + argv

Added custom timeout mechanism with SIGTERM followed by SIGKILL if the process doesn't terminate. And, detached processes now make a process group which is terminated/killed as a whole to decrease the likelihood of hanging processes (hanging tool calls waiting for process to fully shut down)... all in all, when shit hits the fan, i.e. an agent tries to git commit --amend that triggers an editor like vim... that won't block your agent indefinitely... instead it will be terminated after a timeout (no user input possible into vim)... and then the agent will know what happened becuase vim produces enough messages to indicate it was blocking for user input... IOTW agent can proceed with a different approach instead of remaining stuck waiting for a process that will never close in the case of git-commit+core.editor=vim

Pass --verbose (as was previously available) and logs will now be written to ~/.local/share/mcp-server-commands/commands.log, so you can do this to monitor what exactly is happening... down to the level of events emitted from the child_process object that is created with spawn... I added this to troubleshoot timeouts and I love it so I kept it! Also can get example JSONRPC request objects to copy paste for manual testing as I now log ToolRequest and ToolResponse JSON objects!

tail -F ~/.local/share/mcp-server-commands/commands.log 

Dropped dryRun arg, never implemented it and really there's no reason for it...