Mutmut MCP
Mutmut MCP
Un servidor de Model Context Protocol (MCP) para gestionar pruebas de mutación con mutmut. Esta herramienta proporciona un conjunto de API programáticas para ejecutar pruebas de mutación, analizar resultados y mejorar la cobertura de pruebas en proyectos de Python.
Características
Ejecutar sesiones de pruebas de mutación en cualquier módulo o paquete de Python
Mostrar resultados generales de pruebas de mutación y mutaciones supervivientes
Sugerir áreas que necesitan mejor cobertura de pruebas
Volver a ejecutar mutmut en supervivientes específicos o en todos los supervivientes
Limpiar la caché de mutmut
Diseñado para la automatización e integración con otras herramientas MCP
Related MCP server: MCP Python Server
Instalación
# Run directly from GitHub (no install needed)
uvx --from git+https://github.com/wdm0006/mutmut-mcp mutmut-mcp
# Or install from source
git clone https://github.com/wdm0006/mutmut-mcp
cd mutmut-mcp
uv sync
uv run mutmut_mcp.pyInstalación mediante Smithery
Para instalar mutmut-mcp para Claude Desktop automáticamente mediante Smithery:
npx -y @smithery/cli install @wdm0006/mutmut-mcp --client claudeConfiguración del cliente MCP
{
"mcpServers": {
"mutmut": {
"command": "uvx",
"args": ["--from", "git+https://github.com/wdm0006/mutmut-mcp", "mutmut-mcp"]
}
}
}API / Herramientas
Las siguientes herramientas están disponibles:
run_mutmut(target, options="", venv_path=None, project_path=None)– Ejecuta una sesión de pruebas de mutación en el objetivoshow_results(venv_path=None, project_path=None)– Muestra los resultados generalesshow_survivors(venv_path=None, project_path=None)– Enumera las mutaciones supervivientes, además de una sección etiquetada para los mutantes que ninguna prueba cubrererun_mutmut_on_survivor(mutation_id=None, venv_path=None, project_path=None)– Vuelve a ejecutar mutmut en un superviviente específico o en todos los supervivientesclean_mutmut_cache(venv_path=None, project_path=None)– Limpia la caché de mutmutshow_mutant(mutation_id, venv_path=None, project_path=None)– Muestra el diff del código y los detalles de un mutante específicoprioritize_survivors(venv_path=None, project_path=None)– Clasifica los mutantes no cubiertos y supervivientes según su probable materialidad
project_path
Cada herramienta acepta un project_path opcional: el directorio que contiene la configuración de mutmut del proyecto ([mutmut] source_paths= en setup.cfg / pyproject.toml), su código fuente, sus pruebas y el directorio de estado mutants/ de mutmut. Mutmut se ejecuta con ese directorio como su directorio de trabajo, y clean_mutmut_cache solo elimina el estado de su interior.
Pásalo cuando el servidor no se haya lanzado desde el directorio del proyecto — algo típico en clientes MCP de escritorio y en uvx. Si se omite, las herramientas recurren al directorio de trabajo del proceso del servidor, por lo que las llamadas existentes se comportan como antes. Un project_path que no sea un directorio existente devuelve un error sin ejecutar mutmut ni eliminar nada.
venv_path
venv_path apunta al entorno virtual que contiene el mutmut del proyecto (las herramientas usan <venv>/bin/mutmut, o <venv>\Scripts\mutmut.exe en Windows); si se omite, mutmut se toma de PATH. Un venv_path relativo se resuelve contra project_path cuando ambos se proporcionan, por lo que la forma habitual .venv funciona:
{ "project_path": "/home/me/src/myproject", "venv_path": ".venv" }Licencia
Este proyecto está bajo la licencia MIT. Consulta LICENSE para más detalles.
Available Tools
7 toolsclean_mutmut_cacheB
Clean mutmut cache using the mutmut CLI (if available), otherwise remove .mutmut-cache file. Returns the plain text output or confirmation message.
Inputs: venv_path. Returns: result
prioritize_survivorsA
Prioritize surviving mutants by likely materiality, filtering out log/debug-only changes and ranking by potential impact. Returns a sorted list of survivors with reasons for prioritization.
Inputs: venv_path. Returns: object
rerun_mutmut_on_survivorB
Rerun mutmut on specific surviving mutations or all survivors after test updates using the mutmut CLI. Returns the plain text output.
Inputs: mutation_id, venv_path. Returns: result
run_mutmutA
Run a full mutation testing session with mutmut on the specified target.
This tool initiates mutation testing on the given module or package. You can provide additional mutmut options as needed. The output includes a summary of mutations tested, including counts of killed, survived, and timed-out mutations. If a virtual environment path is provided, mutmut will be run using the binaries from that environment to ensure compatibility with project-specific dependencies.
Args: target (str): The module or package to run mutation testing on. options (str): Additional command-line options for mutmut (e.g., '--use-coverage'). Defaults to empty. venv_path (Optional[str]): Path to the project's virtual environment to use for running mutmut. Defaults to None.
Returns: str: Summary of the mutation testing run, or error message if the run fails.
Inputs: target (required), options, venv_path. Returns: result
show_mutantB
Show the code diff and details for a specific mutant using mutmut show. Args: mutation_id (str): The ID of the mutant to show. venv_path (Optional[str]): Path to the virtual environment, if any. Returns: str: The output of 'mutmut show <mutation_id>'.
Inputs: mutation_id (required), venv_path. Returns: result
show_resultsC
Display overall results from the last mutmut run using the mutmut CLI. Returns the plain text output.
Inputs: venv_path. Returns: result
show_survivorsC
List details of surviving mutations from the last mutmut run using the mutmut CLI. Returns the plain text output.
Inputs: venv_path. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool has a distinct purpose: run_mutmut initiates testing, show_results displays overall results, show_survivors lists survivors, show_mutant shows specific mutant details, rerun_mutmut_on_survivor retests survivors, prioritize_survivors ranks survivors, and clean_mutmut_cache manages cache. There is no overlap or ambiguity in functionality.
All tools follow a consistent snake_case naming pattern with clear verb_noun structures (e.g., run_mutmut, show_results, clean_mutmut_cache). The naming is predictable and readable throughout the set.
With 7 tools, this server is well-scoped for mutation testing with mutmut. Each tool serves a specific role in the workflow, from running tests to analyzing results, without being overly sparse or bloated.
The tool set provides complete coverage for the mutmut domain: it includes core testing (run_mutmut), result inspection (show_results, show_survivors, show_mutant), survivor management (rerun_mutmut_on_survivor, prioritize_survivors), and maintenance (clean_mutmut_cache). There are no obvious gaps in the mutation testing lifecycle.
Maintenance
Related MCP Connectors
A Model Context Protocol server for Wix AI tools
Model Context Protocol server for Studex tools, notifications, and profile integrations
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceA Model Context Protocol server that enables AI assistants like Claude to perform Python development tasks through file operations, code analysis, project management, and safe code execution.9MIT
- FlicenseNot gradedqualityDmaintenanceA Python-based implementation of the Model Context Protocol that enables communication between a model context management server and client through a request-response architecture.-
- AlicenseAqualityBmaintenanceA Model Context Protocol server that allows LLMs to interact with Python environments, execute code, and manage files within a specified working directory.10452 PyPI104MIT
- FlicenseAqualityNot gradedmaintenanceA Model Context Protocol server that allows LLMs to interact with Python environments, enabling code execution, file operations, package management, and development workflows.9-