Pare Make

Community

Structured Make/Just task runner operations (run, list) as typed JSON.

How to install ↓ Compare GitHub source repository ↗

Category: Dev Tools #429 of 438
Stars: ★ 138 Popular
Transport: stdio (local process)
Runtime: Node.js 20+
Credentials: No credential needed
License: MIT
Last commit: 53 days ago
Tools: 2

25FMRS · D

Pare Make is a useful MCP server for converting make/just task execution into structured JSON, reducing agent parsing overhead. It is part of the larger Pare ecosystem, offering consistent output. However, it is a standalone server and does not include other Pare tools.

Strongest · Maintenance 8/20 Weakest · Reliability 2/20

Reliability

2/20

Security and permissions

4/20

Maintenance

8/20

Documentation

4/20

Setup experience

7/20

Why each score

Reliability 2/20: Only the server.json manifest was supplied; no source code, tests, or CI workflows for server-make were available. Startup, MCP handshake, and declared run/list tool behavior cannot be verified. The manifest is well-formed, but no executable evidence exists, so a strong conservative deduction was applied.
Security and permissions 4/20: The server is described as running make/just tasks, which can execute arbitrary local commands with side effects. No evidence of confirmation prompts, sandboxing, least-privilege design, or data-flow disclosure was provided. No red-line malware or exfiltration evidence was found, but the command-execution risk is uncontrolled, justifying a low score.
Maintenance 8/20: The repository is not archived, uses an MIT license, and the manifest shows a versioned npm package (0.22.0), indicating some release governance. However, commit history, release cadence, and issue-response behavior were not observable; README badges are untrusted and not attributable to this specific server.
Documentation 4/20: For server-make, documentation is limited to a one-line description and a brief mention in a README table. No tool parameters, response examples, limits, authentication, or troubleshooting specific to this server were supplied. The long README is repo-wide and does not substitute for server-specific documentation.
Setup experience 7/20: The manifest provides the npm package identifier and stdio transport, and the README's generic npx-based install workflow is plausibly applicable. However, no server-specific client configuration example was provided, and no CI or tests verify that the installation path works, so the score is conservative.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessRuns commands or code

Best for

AI agents that require structured, typed output.
Developers who need consistent behavior across environments without platform-specific quirks.
Those looking to reduce token consumption and improve reliability.

Not for

Users needing a graphical task-running interface.
Projects that do not use make or just as their task runner.
Environments with strict Node version requirements (requires Node >= 20).

Required permissions

Execute tasks defined in Makefile or Justfile.
Access project filesystem to locate and run tasks.
May install dependencies or modify files, depending on task definitions.

Risks and side effects

Arbitrary code execution: make and just tasks can run arbitrary shell commands.
Permission abuse: if granted broad filesystem or network permissions, it could be misused.
Token cost: although output is structured, listing many targets may still consume significant tokens.

Setup

Before you start

Runtime：Node.js 20+

Other optional settings (1)

PARE_TOOLS optional Optional. Universal filter across all Pare servers in server:tool format (e.g. make:run); takes precedence over per-server variables.

Ensure Node.js >= 20 is installed.
Add the following configuration to your MCP client:

{
"mcpServers": {
"pare-make": {
"command": "npx",
"args": ["-y", "@paretools/make"]
}
}
}

Restart your MCP client session.
Verify by running npx -y @paretools/make.

claude_desktop_config.json

{
  "mcpServers": {
    "pare-make": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/make"
      ]
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json

{
  "servers": {
    "pare-make": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/make"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal

claude mcp add pare-make -- npx -y @paretools/make

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

The run and list tools from pare-make should appear in the client's tool list; invoking list and getting schema-validated JSON back confirms the install works.

Troubleshooting

If you get npx or ENOENT errors, use `cmd /c npx` on Windows.
If Node version is too old, upgrade to >= 20.
If first start is slow, pre-run `npx -y @paretools/make` to cache, or install globally.
If MCP connection times out, increase initTimeout in client config.

Things to try

Once connected, you can ask your AI assistant things like:

List all tasks defined in the project's Makefile or Justfile
Run make build and return the result as structured JSON
Use pare-make to list available build targets, then run the default one
Run the project's test task and give me only the key output

Tools 2

run writes

Run a specified task in a Make or Just project, returning a structured result with fields like status, output, and error.

list read-only

List available Make or Just targets, returning a structured list with fields such as name and description.

Use cases

Reliable task execution for development workflows without fragile text parsing.

Let AI agents obtain structured task lists and results from Make/Just directly.

Integrate task running into CI/CD or other automation scripts.

Supported clients

Claude Desktop

Claude Code

Cursor

VS Code

Windsurf

Listed from the project's documentation, not tested by this site.

Overview

Pare Make is an MCP server within the Pare project that provides structured, typed JSON output for task runners such as make and just, replacing fragile text parsing. The server exposes two tools: run (execute a task) and list (enumerate available tasks). It returns schema-validated data via MCP's structuredContent, allowing AI agents to act on the data directly without parsing raw terminal output. It is published as the npm package @paretools/make and communicates over stdio.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →

NPM Sentinel MCP Server 79 · B

AI-powered NPM package analysis MCP server

★ 18 · Tools 19 Compare with this →

MartinLoop MCP Server 79 · B

An independent control layer that gives AI coding agents budgets, brakes, and receipts

★ 409 Compare with this →

GitHub MCP Server 76 · B

GitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language

★ 33.5k · Tools 15 Compare with this →

Compare with other MCP servers

More servers from this repository

Source revision 57e1980e8375 Data synced 2026-10-11 Read the FMRS scoring method