jmeter-mcp-server-ts

The server utilizes `child_process.spawn` and `execFile` with array arguments for executing JMeter, which is the safest method to run external commands programmatically as it avoids shell interpretation. Environment variables `JMETER_HOME` and `JMETER_BIN` are read, preventing hardcoded secrets. The primary security consideration arises if an attacker can control the *values* of paths (`testPlan`, `resultsFile`, `reportDir`) or properties passed to JMeter, as JMeter itself would then process these potentially malicious inputs. However, the server's code itself mitigates direct command injection risk from its side.