Makefile MCP Server

Exposes Makefile targets as callable tools for AI assistants.

An MCP (Model Context Protocol) server that exposes Makefile targets as callable tools for AI assistants like Claude, Cursor, etc.

⚠️ALPHA SOFTWARE - LOCAL USE ONLY⚠️
This server executes Make commands with user-provided arguments. Only use in trusted environments. It intelligently parses out commands and args. This almost certainly won't work flawlessly for your Makefile. In fact, it might not even work at all.

- Node.js 16 or higher
- makecommand available in PATH
- A Makefile in your project directory

git clone https://github.com/mparker3/makefilemcpserver.git cd makefilemcpserver

{ "mcpServers": { "makefilemcpserver": { "command": "node", "args": [ "/absolute/path/to/makefilemcpserver/build/index.js", "/path/to/your/project" ] } } }

The second argument (optional) specifies the directory containing your Makefile. If omitted, uses the current directory.

# Build the project build: npm run build # Run tests test: npm test # Deploy to production deploy: build test ./deploy.sh

This will expose tools:make_build,make_test, andmake_deployto Claude.
- The server reads your Makefile at startup
- Each Make target becomes a tool with the namemake_<target>
- Comments directly above targets become tool descriptions
- MCP clients can then run any target with optional arguments. We do some best-effort parsing of args from docs + commands, a better approach would just be to offload it to yet another LLM call(s) at startup.

⚠️WARNING: This server executes shell commands via Make. It currently has minimal input validation.

- Anything you expose in your Makefile, any MCP client will have access to. Highly recommend runninglocally only.
- The server does some de rigeur input sanitization, but no guarantees that an enterprising security researcher can't figure out a way around it.

# Install dependencies npm install # Build once npm run build # Build and watch for changes npm run watch # Run the MCP Inspector for debugging npm run inspector

Since MCP servers communicate over stdio, use the MCP Inspector:

Then open the provided URL to access debugging tools.

This is alpha software. Contributions are welcome! Please:
- Fork the repository
- Create a feature branch
- Make your changes
- Submit a pull request

- Support for multiple Makefiles
- Configuration for timeout values
- Better error messages and logging
- Tests and CI/CD pipeline

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

A command-line interface to prompt users for their next plan or confirmation.

A server that provides background process management capabilities, enabling LLMs to start, stop, and monitor long-running command-line processes.

Paid remote MCP for CLI tool MCP, structured receipts, usage logs, and audit-ready evidence for agent and CI workflows.

Durable MCP control plane for long-running Codex Desktop tasks.

Interact with the CODING DevOps platform for managing projects and work items.

A flexible MCP server that executes arbitrary command-line tools defined in a configuration file.

7 tools for AI agent cron job scheduling with SQLite persistence, retry logic, and structured observability. MIT license.

A development management tool for project planning, task management, and development workflows.

Clean and audit messy MCP setups: stale servers, unused tools, context-heavy MCPs, outdated packages, and safe repair plans.