An MCP server that executes tox commands to run python tests within a project using pytest
An MCP server that executes tox commands to run python tests within a project using pytest. That is what the tox testing mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The server publishes 11 tools. What each one is for:
run_tox_tests — Execute tox tests with various modes and optionsall — Run all tests or tests from a specific groupfile — Run tests from a specific filecase — Run a specific test casedirectory — Run all tests in a specified directoryclients — Client-related testsapi — API endpoint testsauth — Authentication testsuploads — Upload functionality testsroutes — Route handler testsTools — The Tools tool exposed by this serverSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Configuration is passed through the environment: TOX_APP_DIR, TOX_TIMEOUT. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the file and storage access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Tox Testing's toolset — run_tox_tests, all, file and 8 more — is a fair guide to whether it matches your workflow. It is maintained by that1guy15; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Tox Testing's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| run_tox_tests | Execute tox tests with various modes and options |
| all | Run all tests or tests from a specific group |
| file | Run tests from a specific file |
| case | Run a specific test case |
| directory | Run all tests in a specified directory |
| clients | Client-related tests |
| api | API endpoint tests |
| auth | Authentication tests |
| uploads | Upload functionality tests |
| routes | Route handler tests |
| Tools | The Tools tool exposed by this server. |
| Variable | Description | Required |
|---|---|---|
| TOX_APP_DIR | Filesystem location the server is allowed to use. | Optional |
| TOX_TIMEOUT | Configuration value read at startup. | Optional |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.