run_locustLABSCO SUMMARY
One tool, and its parameters are the whole interface.
You still write the Locust file; the server runs it with the user count, spawn rate, runtime and target host you give, headless by default or with the UI when you want to watch. The value lands on the way back — the output arrives in the conversation, so the analysis happens where the numbers are.
What it is
A Python server that runs your Locust test script with the parameters you name and streams the output back — headless or with the UI, against the host, runtime, user count and spawn rate you choose.
What you get
run_locust— takestest_file, plusheadless,host,runtime,usersandspawn_rate- Defaults set once in a
.env:LOCUST_HOST,LOCUST_USERS,LOCUST_SPAWN_RATE,LOCUST_RUN_TIME - Real-time output from the run rather than a summary after the fact
- HTTP and HTTPS support out of the box, and your own custom task scenarios
Requirements
Python 3.13 or higher and the uv package manager. Clone the repo, then point your client at uv --directory <YOUR_PATH_TO_LOCUST_MCP_SERVER> run locust_server.py; uv installs the dependencies listed in the repo's pyproject.toml (locust and mcp[cli]) on first launch. The README's uv pip install -r requirements.txt step names a file the repository does not have. You supply the Locust script — the tool takes its path.
Setup effort
Build from source
USE CASES
01
Running a load test without leaving the editor
Point at the script and give the user count and duration; the run starts and reports back in the thread.
02
Trying a different load shape quickly
Change users and spawn rate per call instead of editing the script or remembering the CLI flags.
03
Making sense of a failing run
The real-time output lands next to the model, so the failure and its interpretation are in the same place.
04
Watching the run in the Locust UI
Set headless off and the usual web interface comes up for the same test.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
- Python 3.13 or later
- uv
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/QAInsights/locust-mcp-server.gitMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"locust": {
"command": "uv",
"args": [
"--directory",
"<YOUR_PATH_TO_LOCUST_MCP_SERVER>",
"run",
"locust_server.py"
]
}
}
}
