I think this is a mistake on the part of the developers.
My statement.
How NPX, Shell, and Child Processes Work on Windows:
NPX is a tool for running Node.js packages without installing them globally.
When you run npx some-command, NPX starts as a process and creates a child process for your app.
On Windows, this child process needs a shell environment to properly handle input/output and termination.
Using cmd /k npx some-command ensures the shell stays open, preventing unexpected process termination.
Unix systems handle this differently due to their built-in process management.
npx needs an interpreter
use “cmd /k npx @agentdeskai/browser-tools-mcp” as command