Skip to main content

MCP Server Make

CI Release PyPI version

A Model Context Protocol server that provides make functionality. This server enables LLMs to execute make targets from any Makefile in a safe, controlled way.

Server Make MCP server

Overview

The server exposes make functionality through the Model Context Protocol, allowing LLMs like Claude to:

  • Run make targets safely with output capture
  • Understand and navigate build processes
  • Help with development tasks
  • Handle errors appropriately
  • Respect working directory context

MCP Server Make works with any valid Makefile - you can use the included opinionated Makefile or your own custom build scripts.

Quick Start

Installation

Using uv (recommended):

uv pip install mcp-server-make

Using pip:

pip install mcp-server-make

Basic Usage

# 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

MCP Client Configuration

To use with Claude Desktop, add to your Claude configuration (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"
      ]
    }
  }
}

Documentation

For detailed information about using MCP Server Make, please see our documentation:

  • User Guide - Complete guide to installation, configuration, and usage
  • Custom Makefiles - Creating effective Makefiles for use with MCP Server Make

Enhancing Development Workflows

This server enables powerful development workflows by giving LLMs direct access to make functionality:

For Developers

  1. Automated Assistance

    • Let Claude run and interpret test results
    • Get build system suggestions and improvements
    • Automate repetitive development tasks
  2. Project Management

    • Let Claude handle dependency updates
    • Automate release processes
    • Maintain consistent code quality

Working with Make Targets

MCP Server Make does not automatically discover available targets in your Makefile. To effectively use it with Claude:

  1. Start with make help: Most well-designed Makefiles include a help target

    Human: Please run make help to see what commands are available.
    
  2. Tell Claude about your targets: Explicitly mention available targets and their purpose

    Human: Our project has these make targets: test, lint, format, build, and clean.
    
  3. Use standard conventions: Common targets that many Makefiles include:

    • make test - Run tests
    • make lint - Check code quality
    • make format - Format code
    • make build - Build the project
    • make clean - Clean build artifacts

The repository includes an opinionated Makefile with additional utility targets - see the User Guide for details on these extended capabilities or for creating your own custom targets.

Note: Claude doesn't remember available targets between conversations. You'll need to introduce them at the start of each conversation.

Example Integration

Here's how Claude can help with development tasks:

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.

Available Tools

The server exposes a single tool:

  • make - Run a make target from the Makefile
    • target (string, required): Target name to execute

Contributing

We welcome contributions to improve mcp-server-make! Please see CONTRIBUTING.md for detailed instructions on setting up your development environment, using the project tools, and submitting changes.

License

MIT License - see LICENSE file for details

Metadata

Release files for mcp-server-make 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mcp-server-make 0.4.0
File Size Uploaded Provenance Actions
mcp_server_make-0.4.0.tar.gz 42.0 kB With provenance Details for mcp_server_make-0.4.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for mcp-server-make 0.4.0
File Interpreter ABI Platform Actions
mcp_server_make-0.4.0-py3-none-any.whl Python 3 none any Details for mcp_server_make-0.4.0-py3-none-any.whl

Total release size: 49.0 kB

Release files / mcp_server_make-0.4.0.tar.gz

Download URL mcp_server_make-0.4.0.tar.gz
Size 42.0 kB
Tags Source
SHA-256 checksum
How to use checksums
bb413d93ead2cad6929312fd6e939431bdd78929c4bedc1adb22ae6aaf595301
BLAKE2b-256 checksum
How to use checksums
8bd61d44cba42fd5571cb419bcfe005632c1d08dd8f6672a910af35e35f0f84c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 9, 2026.

Transparency log

Release files / mcp_server_make-0.4.0-py3-none-any.whl

Download URL mcp_server_make-0.4.0-py3-none-any.whl
Size 7.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9d71b94a26fe15be4d3d8cbfe527094bfddaa4e397bd0ebd604bcdcda42d081f
BLAKE2b-256 checksum
How to use checksums
d2586bf936b6c3c6227856e722c402615a81b4a53d0c8bcd93f34728dd5e2f85
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 9, 2026.

Transparency log

Security for mcp-server-make 0.4.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for mcp_server_make-0.4.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 9, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page