Un servidor MCP que ejecuta comandos tox para ejecutar pruebas de Python en un proyecto con pytest. Este servidor proporciona una forma práctica de ejecutar y administrar pruebas de Python mediante el Protocolo de Contexto de Modelo (MCP).
run_tox_tests - Ejecuta pruebas toxicológicas con varios modos y opciones
Admite diferentes modos de ejecución:
all : Ejecutar todas las pruebas o pruebas de un grupo específico
file : Ejecutar pruebas desde un archivo específico
case : Ejecutar un caso de prueba específico
directory : ejecuta todas las pruebas en un directorio específico
Grupos de prueba admitidos:
clients : Pruebas relacionadas con el cliente
api : pruebas de puntos finales de API
auth : Pruebas de autenticación
uploads : Pruebas de funcionalidad de carga
routes : Pruebas del controlador de rutas
Related MCP server: MCP Pytest Server
Instalar dependencias:
npm installConstruir el servidor:
npm run buildPara desarrollo con reconstrucción automática:
npm run watchPara usar con VSCode, agregue la configuración del servidor a su archivo de configuración de MCP en: ~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
{
"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"
}
}
}
}env.TOX_TIMEOUT : (Opcional) Tiempo máximo en segundos de espera para que se complete la ejecución de la prueba. Si una prueba tarda más de este tiempo límite, se finalizará. El valor predeterminado es 600 segundos (10 minutos).
env.TOX_APP_DIR : (Obligatorio) Directorio que contiene el archivo tox.ini. Desde aquí se ejecutarán los comandos tox. La ruta debe apuntar a la raíz de su proyecto Python, donde se encuentra tox.ini.
El tiempo de espera es particularmente importante para:
Prevención de procesos de prueba bloqueados
Gestión de pruebas de integración de larga duración
Cómo garantizar que las canalizaciones de CI/CD no se atasquen
El servidor proporciona una única herramienta, run_tox_tests que se puede utilizar en diferentes modos:
// Run all tests
{
"mode": "all"
}
// Run tests from a specific group
{
"mode": "all",
"group": "api"
}
// Run tests from a specific file
{
"mode": "file",
"testFile": "tests/test_api.py"
}
// Run a specific test case
{
"mode": "case",
"testFile": "tests/test_api.py",
"testCase": "test_endpoint_response"
}
// Run tests from a specific directory
{
"mode": "directory",
"directory": "tests/api/"
}Al usar este MCP con Cline, puede configurar las instrucciones personalizadas de Cline para gestionar la ejecución de pruebas de forma eficiente. A continuación, se recomienda un flujo de trabajo:
If asked to run tests on the project, use the tox-testing MCP. Follow these steps:
1. Run all tests across the project unless you are given instructions to run a specific test file or test case.
2. Review and rerun each failed test case individually as you troubleshoot and fix the issue from its output.
3. Repeat step 2 until the testcase passes.
4. Once all failed test cases from step 1 are passing rerun all tests again and repeat all steps until all tests pass.Este flujo de trabajo garantiza:
Cobertura de pruebas integral ejecutando todas las pruebas primero
Depuración enfocada mediante el aislamiento de casos de prueba fallidos
Verificación de correcciones mediante la repetición de pruebas en casos individuales
Validación final ejecutando nuevamente todas las pruebas
Ejemplos de interacciones con Cline:
You: Run the tests for this project
Cline: I'll use the tox-testing MCP to run all tests:
{
"mode": "all"
}
You: Fix the failing test in test_api.py
Cline: I'll first run the specific test file:
{
"mode": "file",
"testFile": "tests/test_api.py"
}
Then address each failing test case individually:
{
"mode": "case",
"testFile": "tests/test_api.py",
"testCase": "test_endpoint_response"
}Consulte CONTRIBUTING.md para obtener detalles sobre nuestro código de conducta y el proceso para enviar solicitudes de extracción.
Run tox tests with different modes and options
| Name | Required | Description | Default |
|---|---|---|---|
| mode | Yes | Test execution mode | |
| directory | No | Directory containing tests to run (required for directory mode) | |
| group | No | Test group to run in all mode (defaults to clients) | |
| testFile | No | Specific test file to run (required for file and case modes) | |
| testCase | No | Specific test case to run (required for case mode) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool runs tests but fails to describe execution behavior, side effects, permissions needed, or output format. This leaves critical operational traits undocumented for a test-running tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's function without unnecessary words. It is appropriately sized and front-loaded, making it easy to understand quickly with zero waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (5 parameters, no output schema, and no annotations), the description is incomplete. It does not explain return values, error handling, or behavioral nuances, leaving gaps that could hinder effective tool invocation in a testing context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description mentions 'different modes and options,' which aligns with the parameters in the schema. However, with 100% schema description coverage, the schema already documents all parameters thoroughly. The description adds minimal semantic context beyond what the schema provides, meeting the baseline for high coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Run') and resource ('tox tests'), specifying the tool's purpose as executing tests with different modes and options. It distinguishes the tool's functionality but lacks explicit differentiation from siblings since none are provided, making it clear but not fully optimized for sibling comparison.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or contextual cues. It mentions 'different modes and options' but does not specify scenarios or exclusions, leaving usage entirely implicit and lacking actionable advice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.1.0run_tox_testsScored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, making disambiguation perfect. The single tool has a clear and distinct purpose that cannot be confused with any other tool in the set.
Since there is only one tool, naming consistency is inherently perfect as there are no other tools to compare it against. The tool name 'run_tox_tests' follows a clear verb_noun pattern, which is consistent with itself.
A single tool is generally too few for most server purposes, as it limits functionality and flexibility, making the server feel thin and underdeveloped. While it might suffice for a very narrow scope, it often indicates a lack of comprehensive coverage for the domain.
With only one tool, the server is severely incomplete for the domain of tox testing, as it lacks essential operations such as configuring environments, listing tests, checking results, or managing dependencies. This minimal surface will likely cause agent failures when more complex tasks are required.
An MCP server that provides access to Testiny projects, test cases and test runs
A MCP server built for developers enabling Git based project management with project and personal…
Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.
