Request for an MCP shutdown tool

[c64cryptoboy]

Please consider adding an MCP shutdown tool

I'm using the pi.dev harness with an AI-written proxy to connect from inside the agent's Docker container to Retro Debugger running outside the container on Windows/WSL.

The proxy is mostly reliable about not leaving orphaned Retro Debugger processes, but process-level termination from WSL/Windows is awkward. Sometimes Retro Debugger does not like being killed externally and creates a Windows popup.

A dedicated MCP shutdown tool would let Retro Debugger shut itself down gracefully through its normal shutdown path, instead of requiring the client/proxy to use OS-specific process killing such as taskkill.exe.

Possible MCP API shape:

{
 "tool": "retro_shutdown",
 "args": {
   "force": false
 }
}

Suggested behavior:

• stop the MCP server / close MCP stdio cleanly
• request normal app shutdown, ideally using the same path as File → Quit / SYS_Shutdown()
• allow Retro Debugger's existing shutdown handling to save settings, plugin state, symbols, etc.
• optionally support "force": true if there is a more aggressive internal shutdown path

[slajerek]

Thanks, that's a good idea. I'll add it to my TODO list!