# build [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/Dave-London/pare  
**GitHub Stars:** 138  
**npm Downloads (last month):** 344  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/build

## Description
Structured build tool output (tsc, generic commands) as typed JSON diagnostics.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "build": {
    "command": "npx",
    "args": ["-y","@paretools/init"]
  }
}
```

## Documentation

## What build does

The build MCP server wraps developer build commands and presents their results as structured MCP tool output. The repository description specifically identifies TypeScript compiler output and generic commands as use cases, while the project catalog lists tsc, esbuild, Vite, and webpack among the wrapped build tools.

Instead of returning only terminal text, the server is intended to give an agent data with stable fields that can be inspected programmatically. This is useful for workflows that need to identify compilation failures, warnings, file locations, or command status without relying on regular expressions over console output.

Pare is organized as a collection of MCP servers. The build server is one package in that collection, alongside separate servers for linting, testing, version control, package managers, and infrastructure tools. Install only the packages relevant to the project rather than enabling the full catalog.

## How it works

Each Pare tool produces two MCP outputs. The `content` value contains human-readable text for clients that display command results. The `structuredContent` value contains typed JSON validated against an output schema. MCP clients and agents can use the structured value directly instead of parsing raw command output.

This design addresses formatting differences caused by ANSI escape sequences, progress indicators, decorative headers, locales, operating systems, and tool versions. Build output can therefore be consumed through fields defined by the tool schema rather than through assumptions about how a command prints its messages.

The build MCP server is most suitable when an agent must make decisions from compiler or bundler results, such as reporting failures or determining whether a build completed successfully. The repository also publishes tool schemas and response examples for its packages, although the provided material does not include the individual build tool schemas.

## Setup and configuration

The documented project setup uses the Pare initializer. Its non-interactive example configures MCP servers for a client and preset:

```bash
npx @paretools/init --client claude-code --preset web
```

The available presets include `web`, `python`, `rust`, `go`, `jvm`, `dotnet`, `ruby`, `swift`, `mobile`, `devops`, and `full`. After configuration, the README instructs users to add the supplied agent rules to the project, restart the client session, and run:

```bash
npx @paretools/init doctor
```

The provided material does not specify a standalone package command for launching only the build server, nor does it list environment variables or credentials required by the build package.

## Tools and capabilities

- Return structured JSON for build command results.
- Wrap TypeScript compiler output through `tsc`.
- Support listed build tools including esbuild, Vite, and webpack.
- Provide human-readable and schema-validated outputs together.
- Give agents consistent data instead of raw terminal text.

## Limitations and notes

The README describes a broader Pare catalog containing 28 packages and 240 tools, but those totals apply to the complete project rather than specifically to the build package. The supplied material does not enumerate the build server's individual tool names, input parameters, response fields, supported operating systems, or failure-handling behavior. Review the package-specific schemas before depending on a particular diagnostic field.

The build MCP server focuses on structured command output; it does not claim to replace the underlying compilers, bundlers, or build systems. Those tools must be available in the environment where the MCP server runs.

## Getting started with this build MCP server
Always refer to the official documentation for the most accurate and up-to-date information.

_Full upstream README: https://allmcps.com/mcp/build/readme_