Tox Testing

Runs tox-based pytest tests from your project via MCP with flexible modes and environment controls.

javascript

5

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "that1guy15-tox-testing": {
      "command": "node",
      "args": [
        "/path/to/tox-testing/build/index.js"
      ],
      "env": {
        "TOX_APP_DIR": "/path/to/your/python/project",
        "TOX_TIMEOUT": "600"
      }
    }
  }
}

You have a lightweight MCP server that runs tox-based Python tests inside your project. It lets you execute pytest-driven test suites from an MCP client, with flexible modes to run all tests, a specific file, directory, or an individual test case. This makes test discovery, debugging, and iterative fixes quick and repeatable within your development workflows.

How to use

You interact with the tox testing MCP server through an MCP client to run tests in your Python project. Use the available modes to focus your testing work as you develop and debug.

How to install

Prerequisites you need on your machine before installing and using the server:

Node.js and npm must be installed
A Python project with a tox.ini file

Install dependencies for the MCP server, build it, and optionally enable auto-rebuild during development:

npm install

npm run build

npm run watch

Configure the MCP server in your editor or environment to point to your project and set sensible timeouts. The example below defines the server that runs locally via Node from a built index file and passes environment variables for the tox workflow.

Configuration example

{
  "mcpServers": {
    "tox-testing": {
      "command": "node",
      "args": ["/path/to/tox-testing/build/index.js"],
      "env": {
        "TOX_APP_DIR": "/path/to/your/python/project",
        "TOX_TIMEOUT": "600"
      }
    }
  }
}

Configuration options

Environment variables you can tune when running the server:

TOX_TIMEOUT: Optional. Maximum time in seconds to wait for test execution to complete. Default is 600 seconds.
TOX_APP_DIR: Required. Directory containing the tox.ini file. This is the root of your Python project where tox commands are executed.

Usage patterns

The server exposes a single tool named run_tox_tests that you can invoke in different modes to control which tests run. You can run all tests, tests from a specific group such as api or auth, tests from a particular file, a single test case, or all tests within a directory.

Security and notes

Respect the timeout to prevent hung processes in long-running scenarios or CI pipelines. Provide a valid TOX_APP_DIR pointing to the root of your Python project to ensure tox runs from the correct location.

Contributing

Contributions follow your project’s governance and contribution guidelines.

Available tools

run_tox_tests

Executes tox tests with multiple modes: all, file, case, or directory. Supports test groups such as clients, api, auth, uploads, and routes.