run_tox_tests
Run tox tests with different modes and options
LABSCO SUMMARY
One tool, four scopes, and the timeout you will be glad of.
The scope argument is the whole design: run everything to find what broke, rerun the single case while you fix it, then run everything again to confirm nothing else moved — a loop the README spells out as a custom instruction worth pasting into your client. TOX_TIMEOUT matters more than it looks: without a ceiling, one hung integration test takes the session with it.
What it is
A single-tool MCP server that executes tox in a Python project, running its pytest suite at whatever scope you name. The point is the narrowing: after a full run fails, the same tool reruns just the failing case, which is the loop debugging actually takes.
What you get
- The whole suite run, or one named test group —
clients,api,auth,uploadsorroutes— withmodeset toall—run_tox_tests - A single file run by passing
modeasfilewithtestFile, or one test case by addingtestCase - Every test under a directory run with
modeset todirectory - A time limit on the run, so a hung test process is terminated rather than blocking the session
Requirements
No account and no key — it runs tox on your machine. TOX_APP_DIR is required and must point at the directory containing tox.ini, since that is where tox is invoked from. TOX_TIMEOUT sets the maximum seconds for a run and defaults to 600. The npm package name is tox-testing (0.1.0) and it is marked private, so build from a clone with npm install and npm run build, then point your client at the built index.js. Running tests means running the project's code, so point it at a project you trust.
Setup effort
One command — npx -y github:that1guy15/tox-testing
USE CASES
01
Finding out what is broken
Run the whole suite once and let the model read the failures, instead of switching to a terminal.
02
Fixing one failing test without waiting for the rest
Rerun just that file, then just that case, as you iterate on the fix.
03
Checking one area after a change
Run the group that covers what you touched — auth, routes, uploads — rather than the entire suite.
04
Confirming a fix did not break something else
Run everything again after the individual case passes, which is the step that gets skipped when testing is manual.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected.
Requires
- npx on PATH
- TOX_APP_DIR in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Server setup
Configuration file
JSON
{
"mcpServers": {
"tox-testing": {
"command": "node",
"args": [
"<YOUR_PATH_TO_TOX_TESTING>/build/index.js"
],
"env": {
"TOX_APP_DIR": "<YOUR_TOX_APP_DIR>",
"TOX_TIMEOUT": "600"
}
}
}
}Clone https://github.com/that1guy15/tox-testing and build it (npm install, then npm run build); <YOUR_PATH_TO_TOX_TESTING> is the folder you cloned. Set TOX_APP_DIR to the root of your Python project, where tox.ini is.
npx
TERMINAL
npx -y github:that1guy15/tox-testing
