Best for
- Projects using TypeScript, esbuild, Vite, or webpack
- Developers wanting reliable build diagnostics for agents
- Use cases needing minimal token overhead from build logs
P
Pare Build
Community
Structured build output as typed JSON diagnostics
- Category
- Dev Tools #272 of 438
- Stars
- ★ 138 Popular
- Transport
- stdio (local process)
- Runtime
- Node.js >=20
- Credentials
- No credential needed
- License
- MIT
- Last commit
49FMRS · D
This server provides structured diagnostics from common frontend build tools to AI agents as JSON, reducing parsing overhead. It is non-official and maintained by Dave-London. Specific tools are not listed due to insufficient info, but overall description is clear.
Strongest · Setup experience 12/20 Weakest · Reliability 7/20
Why each score
- Reliability 7/20
- Based only on the supplied README and manifest, Pare Build is described as a stdio MCP server with an npm package, version, and structuredContent output. However, no tool list, output schemas, tests, or CI evidence for this server were supplied, so the handshake and real behavior cannot be verified. Deducted for missing execution evidence; static review caps reliability at 12.
- Security and permissions 7/20
- The server wraps local build tools (tsc/esbuild/vite/webpack), so it can read and execute build configs or plugins; the supplied materials contain no confirmation, sandboxing, least-privilege, or dangerous-operation notes, and no credential-handling documentation. No clear red-line issue is visible, but permission/scoping and data-flow disclosure are missing, so full marks are not justified.
- Maintenance 12/20
- The repository is not archived, has an MIT license, a versioned package (0.22.0), and README badges hint at CI and coverage, suggesting ongoing releases. But no commit/release dates, security-response channel, or dependency-update evidence was supplied, and the 17 open issues show no triage evidence, so the score is moderate.
- Documentation 11/20
- The README covers general installation, client configuration, tool filtering, and troubleshooting, and the manifest gives package/transport details. However, no server-build-specific tool parameters, output schemas, examples, or limitations are included; links to tool-schema docs are not part of the supplied evidence, so documentation is rated below full.
- Setup experience 12/20
- Setup is described clearly: `npx @paretools/init` quickstart, presets, client-specific guides, Node >=20, and a Windows npx workaround are all in the README. However, no direct `@paretools/build` invocation example is provided and no executable verification evidence exists; static calibration caps setup at 15, so 12 is awarded.
Static review · not runListed 2026-08-07
Read the FMRS scoring method →Fit and risk
What it can accessReads local filesWrites / deletes local filesRuns commands or codeUses the network
Not for
- Human users desiring unstructured raw build output
- Projects not using build tools
- Scenarios requiring source code or project metadata
Required permissions
- Read project files to perform builds
- Execute build commands
- Communicate with MCP client via stdio
Risks and side effects
- Build commands might execute arbitrary code (e.g., scripts)
- Build output may contain sensitive info (like paths or env vars)
- Dependencies on npm package and build toolchain availability and security
Setup
Before you start
Runtime：Node.js >=20
Other optional settings (4)
PARE_TOOLS
Universal tool filter in server:tool,... format limiting tools registered across all Pare servers.
PARE_GIT_TOOLS
Per-server tool filter for the git server, e.g. status,log,diff.
PARE_NPM_TOOLS
Per-server tool filter for the npm server, e.g. install,test,run.
MCP_TIMEOUT
MCP connection timeout in milliseconds for Claude Code, e.g. 30000, to fix connection timeouts.
Configure this server in an MCP client to run the npm package @paretools/build using npx. Example config (if JSON config supported): use "command": "npx", "args": ["-y", "@paretools/build"].
Check that it works
After restarting the client, check that tools from the Pare build server (tsc/esbuild/vite/webpack related) appear in the tool list, or run `npx @paretools/init doctor` to validate the connection.
Troubleshooting
- Check Node.js version >= 20
- Ensure npx is available or use absolute path
- Verify MCP client config for stdio transport correctly
- If connection timeouts, increase client initTimeout
Things to try
Once connected, you can ask your AI assistant things like:
- Show the current git branch status and list staged files
- Run the vitest suite and give me structured pass/fail results
- Build the project with tsc and return type errors as JSON diagnostics
- Run npm install and report installed packages and warnings
Use cases
AI agents needing structured build errors and warnings
Automated build pipelines requiring stable machine-readable output
Reducing token usage for agents parsing build logs
Overview
Pare Build is one of the Pare MCP servers, focused on build tools. It transforms output from tsc, esbuild, vite, and webpack into typed JSON diagnostics, allowing AI agents to directly use structured data without parsing fragile terminal text. The server runs over stdio and is available as an npm package.
Similar servers
Context7
80 · B
Upstash's official server providing up-to-date third-party library docs for AI coding assistants
NPM Sentinel MCP Server
79 · B
AI-powered NPM package analysis MCP server
MartinLoop MCP Server
79 · B
An independent control layer that gives AI coding agents budgets, brakes, and receipts
GitHub MCP Server
76 · B
GitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
More servers from this repository
Source revision 57e1980e8375 Data synced 2026-10-11 Read the FMRS scoring method