Build MCP server
Structured build tool output (tsc, generic commands) as typed JSON diagnostics.
138 stars
Reviews
Write oneNobody has reviewed Build yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Build tools (5, 5 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
buildwrite actionRuns a build command and returns structured success/failure with errors and warnings. Use instead of running build commands in the terminal.
esbuildwrite actionRuns the esbuild bundler and returns structured errors, warnings, and output files. Use instead of running `esbuild` in the terminal.
tscwrite actionRuns the TypeScript compiler and returns structured diagnostics (file, line, column, code, message). Use instead of running `tsc` in the terminal.
vite-buildwrite actionRuns Vite production build and returns structured output files with sizes. Use instead of running `vite build` in the terminal.
webpackwrite actionRuns webpack build with JSON stats output and returns structured assets, errors, and warnings. Use instead of running `webpack` in the terminal.
Public scan report
scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it
- Code scan23 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 6 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Install Build in Claude Code, Cursor or VS Code
Runs npx -y @paretools/build on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add build -- npx -y @paretools/build
What the publisher says
From the Build repository's README, as published. We do not edit it. Read it on GitHub
Pare
Reliable, structured CLI output for AI agents — no more parsing fragile terminal text.
Pare provides MCP servers that wrap common developer tools (git, npm, docker, test runners, etc.) and return clean, schema-validated JSON instead of raw terminal text. Agents get typed data they can act on directly, without brittle string parsing.
The Problem
Parsing CLI output is fragile. Raw terminal text includes ANSI escape codes, decorative headers, progress bars, locale-specific formatting, and platform differences that break agent workflows in subtle ways. An agent that works fine with git status on macOS may fail on Windows because the output format changed. A test runner's summary line might shift between versions, silently breaking a regex.
Pare eliminates this entire class of errors by returning schema-validated JSON with consistent field names, regardless of platform, tool version, or locale. As a bonus, structured output is significantly smaller — agents use fewer tokens per tool call:
Token estimates use ~4 chars/token. The biggest savings appear on verbose commands (builds, installs, tests). For simpler tools like eslint or tsc, the main advantage is reliable structured data — agents can use typed JSON directly rather than parsing strings.
How It Works
Each Pare tool returns two outputs:
- content — human-readable text, for MCP clients that display it
- structuredContent — typed, schema-validated JSON, ready for agents to process
This uses MCP's structuredContent and outputSchema features to provide type-safe, validated data that agents can rely on without custom parsing.
Example: git status
Raw git output (~118 tokens):
On branch main
Your branch is ahead of 'origin/main' by 2 commits.
(use "git push" to publish your local commits)Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Build: common questions
- Is Build MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Build safety report
- How do I install Build?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Build need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Build maintained?
- The last commit was 21 days ago (2026-09-22). The latest release is v0.8.0.
- What can I use instead of Build?
- Servers from other publishers that do the same job: Ouroboros MCP server.
Alternatives to Build
Same job from other publishers: the closest match first, then the best rated.
- OuroborosPins an acceptance spec; the verify command and expected output never enter the success contract.not reviewedWidely usedC