MCP Server Make
The MCP Server Make allows LLMs to securely execute and manage make targets from any Makefile.
Run make targets safely: Execute targets with output capture and error handling
Execute standard development tasks: Run tests, linting, formatting, building, and cleaning
Automate development workflows: Perform repetitive tasks and project management steps
Work with custom Makefiles: Use either the included opinionated Makefile or your own custom build scripts
Respect context: Operates within the specified working directory for consistent results
Provides access to make functionality, allowing execution of targets from a Makefile in a controlled environment. Enables running build processes, tests, formatting, and other development tasks defined in Makefiles.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Server Makerun the test suite and show me the results"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Server Make
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.
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.
Related MCP server: MCP Python Toolbox
Quick Start
Installation
Using uv (recommended):
uv pip install mcp-server-makeUsing pip:
pip install mcp-server-makeBasic 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/dirMCP 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
Automated Assistance
Let Claude run and interpret test results
Get build system suggestions and improvements
Automate repetitive development tasks
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:
Start with
make help: Most well-designed Makefiles include a help targetHuman: Please run make help to see what commands are available.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.Use standard conventions: Common targets that many Makefiles include:
make test- Run testsmake lint- Check code qualitymake format- Format codemake build- Build the projectmake 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 Makefiletarget(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
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.
TDQS
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
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
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.1822ISC
- 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.812MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that enables LLMs to run ANY code safely in isolated Docker containers.121MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/wrale/mcp-server-make'
If you have feedback or need assistance with the MCP directory API, please join our Discord server