Skip to main content
Glama

Servidor MCP Make

CI Release PyPI version

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-make

Usando pip:

pip install mcp-server-make

Uso 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/dir

Configuració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:

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

  1. 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

  2. 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:

  1. Empiece con make help: La mayoría de los Makefiles bien diseñados incluyen un objetivo de ayuda

    Human: Please run make help to see what commands are available.
  2. 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.
  3. Utilice convenciones estándar: Objetivos comunes que incluyen muchos Makefiles:

    • make test - Ejecutar pruebas

    • make lint - Comprobar la calidad del código

    • make format - Formatear código

    • make build - Compilar el proyecto

    • make 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 Makefile

    • target (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 tool
makeA

Run a make target from the Makefile

ParametersJSON Schema
NameRequiredDescriptionDefault
targetYesMake target to run
argsNoList of command line arguments (e.g. VAR=value)

TDQS

A3.6/5.0
Behavior2/5

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.

Conciseness5/5

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.

Completeness4/5

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.

Parameters3/5

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.

Purpose5/5

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.

Usage Guidelines3/5

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. 1 tool updatev0.4.0
    • Changedmake1 field changed
      • addedInput schema / properties / args
        Added value: +{
        +  "description": "List of command line arguments (e.g. VAR=value)",
        +  "items": {
        +    "type": "string"
        +  },
        +  "title": "Args",
        +  "type": "array"
        +}
  2. 1 tool updatev1.0.0
    • Addedmake

TDQS

A3.8/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools. The single tool 'make' is clearly distinct by default.

Naming Consistency5/5

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.

Tool Count3/5

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.

Completeness4/5

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

ActivityInactive
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    A 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.
    9
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    A 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 npm
    2
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol (MCP) server that enables LLMs to run ANY code safely in isolated Docker containers.
    122
    MIT