Loading...
Locust-MCP-Server enables AI-driven load testing by integrating Locust load tests with AI development environments via the Model Context Protocol.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
Locust-MCP-Server enables AI-driven load testing by integrating Locust load tests with AI development environments via the Model Context Protocol.
The Locust-MCP-Server is relatively safe when used with trusted test files and properly configured environment variables. However, running untrusted test files poses a significant risk due to arbitrary code execution. It's crucial to limit resource usage to prevent denial-of-service scenarios.
Performance depends on the complexity of the Locust test script, the target host, and the available resources. Large numbers of users and high spawn rates can consume significant resources.
Cost depends on the infrastructure used to run the Locust tests. Cloud-based load testing services may incur costs based on usage.
{
"mcpServers": {
"locust": {
"command": "/Users/naveenkumar/.local/bin/uv",
"args": [
"--directory",
"/Users/naveenkumar/Gits/locust-mcp-server",
"run",
"locust_server.py"
]
}
}
}LOCUST_HOSTLOCUST_USERSLOCUST_SPAWN_RATELOCUST_RUN_TIMErun_locustRuns a Locust load test with configurable parameters like host, users, and runtime.
Executes arbitrary Python code from the specified test file and can potentially exhaust resources.
None
The Locust-MCP-Server is relatively safe when used with trusted test files and properly configured environment variables. However, running untrusted test files poses a significant risk due to arbitrary code execution. It's crucial to limit resource usage to prevent denial-of-service scenarios.
Autonomy is limited by the configurable parameters of the `run_locust` tool. However, the execution of arbitrary code within the test file means that the actual autonomy is dependent on the contents of the test file.
Production Tip
Monitor resource usage (CPU, memory, network) during load tests to prevent impacting production systems.
The primary risk is arbitrary code execution from the Locust test file.
Only use trusted Locust test files and carefully review their contents.
The server itself does not provide sandboxing. You would need to implement sandboxing at the OS level (e.g. containers).
This server does not implement any authentication mechanism.
The target host is configured using the `host` parameter in the `run_locust` tool or via the `LOCUST_HOST` environment variable.
Yes, Locust provides real-time test execution output, which can be monitored.
The server may become unresponsive, and the target system may be negatively impacted. Monitor resource usage and set appropriate test parameters.