MCP Server Make
Servidor MCP Make
Un servidor del Protocolo de Contexto de Modelo (MCP) que proporciona funcionalidad de make. Este servidor permite a los LLM ejecutar objetivos de make desde cualquier Makefile de forma segura y controlada.
Descripción general
El servidor expone la funcionalidad de make a través del Protocolo de Contexto de Modelo, permitiendo a LLMs como Claude:
Ejecutar objetivos de make de forma segura con captura de salida
Comprender y navegar por los procesos de compilación
Ayudar con tareas de desarrollo
Manejar errores de forma adecuada
Respetar el contexto del directorio de trabajo
El servidor MCP Make funciona con cualquier Makefile válido; puede utilizar el Makefile incluido o sus propios scripts de compilación personalizados.
Related MCP server: MCP Python Toolbox
Inicio rápido
Instalación
Usando uv (recomendado):
uv pip install mcp-server-makeUsando pip:
pip install mcp-server-makeUso básico
# Run with default Makefile in current directory
uvx mcp-server-make
# Run with specific Makefile and working directory
uvx mcp-server-make --make-path /path/to/Makefile --working-dir /path/to/working/dirConfiguración del cliente MCP
Para usarlo con Claude Desktop, añádalo a su configuración de Claude (claude_desktop_config.json):
{
"mcpServers": {
"make": {
"command": "uvx",
"args": [
"mcp-server-make",
"--make-path", "/absolute/path/to/Makefile",
"--working-dir", "/absolute/path/to/working/dir"
]
}
}
}Documentación
Para obtener información detallada sobre el uso del servidor MCP Make, consulte nuestra documentación:
Guía del usuario - Guía completa de instalación, configuración y uso
Makefiles personalizados - Creación de Makefiles efectivos para su uso con el servidor MCP Make
Mejora de los flujos de trabajo de desarrollo
Este servidor permite flujos de trabajo de desarrollo potentes al dar a los LLM acceso directo a la funcionalidad de make:
Para desarrolladores
Asistencia automatizada
Deje que Claude ejecute e interprete los resultados de las pruebas
Obtenga sugerencias y mejoras del sistema de compilación
Automatice tareas de desarrollo repetitivas
Gestión de proyectos
Deje que Claude gestione las actualizaciones de dependencias
Automatice los procesos de lanzamiento
Mantenga una calidad de código consistente
Trabajo con objetivos de make
El servidor MCP Make no descubre automáticamente los objetivos disponibles en su Makefile. Para utilizarlo eficazmente con Claude:
Empiece con
make help: La mayoría de los Makefiles bien diseñados incluyen un objetivo de ayudaHuman: Please run make help to see what commands are available.Informe a Claude sobre sus objetivos: Mencione explícitamente los objetivos disponibles y su propósito
Human: Our project has these make targets: test, lint, format, build, and clean.Utilice convenciones estándar: Objetivos comunes que incluyen muchos Makefiles:
make test- Ejecutar pruebasmake lint- Comprobar la calidad del códigomake format- Formatear códigomake build- Compilar el proyectomake clean- Limpiar artefactos de compilación
El repositorio incluye un Makefile con objetivos de utilidad adicionales; consulte la Guía del usuario para obtener detalles sobre estas capacidades extendidas o para crear sus propios objetivos personalizados.
Nota: Claude no recuerda los objetivos disponibles entre conversaciones. Deberá presentárselos al inicio de cada conversación.
Ejemplo de integración
Así es como Claude puede ayudar con las tareas de desarrollo:
Human: Can you run our test suite and format any code that needs it?
Claude: I'll help run the tests and format the code:
1. First, let's format the code:
[Calling make tool with args {"target": "format"}]
2 files reformatted, 3 files left unchanged
2. Now let's run the tests:
[Calling make tool with args {"target": "test"}]
Running tests...
4 passed, 0 failed
All formatting and tests completed successfully. The code is now properly formatted and all tests are passing.Herramientas disponibles
El servidor expone una única herramienta:
make- Ejecutar un objetivo de make desde el Makefiletarget(cadena, obligatorio): Nombre del objetivo a ejecutar
Contribución
¡Agradecemos las contribuciones para mejorar mcp-server-make! Consulte CONTRIBUTING.md para obtener instrucciones detalladas sobre cómo configurar su entorno de desarrollo, utilizar las herramientas del proyecto y enviar cambios.
Licencia
Licencia MIT - consulte el archivo LICENSE para obtener más detalles
Available Tools
1 toolmakeA
Run a make target from the Makefile
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes | Make target to run | |
| args | No | List of command line arguments (e.g. VAR=value) |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description does not mention potential side effects like file creation or environment changes, and with no annotations, the agent lacks awareness of destructive behavior.
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?
A single, direct sentence with no unnecessary words; highly concise and front-loaded.
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?
The description covers the essential functionality for a simple tool, though it could mention that the Makefile must exist in the current working directory.
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?
Schema coverage is 100%, so the description adds no extra meaning beyond the schema's parameter descriptions, earning a baseline score.
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 the resource (make target from the Makefile), leaving no ambiguity about the tool's purpose.
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?
No explicit guidance on when to use this tool or prerequisites, but given the absence of sibling tools, the description is minimally adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v0.4.0- Changed
make1 field changed- added
Input schema / properties / argsAdded value: +{ + "description": "List of command line arguments (e.g. VAR=value)", + "items": { + "type": "string" + }, + "title": "Args", + "type": "array" +}
1 tool update
v1.0.0- Added
make
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The single tool 'make' is clearly distinct by default.
With only one tool, naming consistency is perfect. The name 'make' directly describes the action, though it's a verb alone rather than verb_noun pattern.
A single tool for a server named 'MCP Server Make' is borderline. While it directly serves the core purpose, the domain could benefit from additional tools like listing targets or showing help.
The tool fulfills its stated function of running a make target. Minor gaps exist (e.g., no way to list targets or specify options), but the core workflow is supported.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
A Model Context Protocol server for Wix AI tools
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to control Unreal E…
Related MCP Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that allows secure execution of pre-approved commands, enabling AI assistants to safely interact with the user's system.16 npm22ISC
- AlicenseNot gradedqualityCmaintenanceA 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
- AlicenseNot gradedqualityDmaintenanceA comprehensive Model Context Protocol server implementation that enables AI assistants to interact with file systems, databases, GitHub repositories, web resources, and system tools while maintaining security and control.42 npm2MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that enables LLMs to run ANY code safely in isolated Docker containers.122MIT