Pare Build
Turn tsc, esbuild, Vite, and webpack failures into typed JSON diagnostics the agent can fix line by line.
Overview
io.github.Dave-London/pare-build is a Ship-phase MCP server that runs tsc, esbuild, Vite, and webpack and returns typed JSON build diagnostics.
What is this MCP server?
- Pare Build MCP (@paretools/build v0.8.1) for tsc, esbuild, Vite, and webpack
- Build output normalized to typed JSON diagnostics
- Reduces token load versus pasting full compiler and bundler logs
- stdio npm package aligned with other Pare toolchain servers
- GitHub source: Dave-London/Pare repository
- Server version 0.8.1
- Supports four toolchains: tsc, esbuild, vite, webpack
- npm package @paretools/build, stdio transport
Community signal: 128 GitHub stars.
What problem does it solve?
Frontend and TS build failures arrive as huge unstructured logs that agents parse poorly and slow your ship loop.
Who is it for?
Solo builders on Vite, webpack, esbuild, or tsc who want the agent to fix compile errors from structured output.
Skip if: Teams needing managed remote builds only, or stacks without those four toolchains on the machine.
What do I get? / Deliverables
Agents receive compact diagnostic JSON they can map to files and lines, so fix cycles after build commands stay short.
- Typed JSON diagnostic lists from supported build tool runs
- Agent-ready error locations and messages for compile/bundle fixes
Recommended MCP Servers
Journey fit
How it compares
Local bundler/compiler MCP wrapper, not a hosted CI dashboard or a code-review methodology skill.
Common Questions / FAQ
Who is io.github.Dave-London/pare-build for?
It is for developers shipping TS/JS apps who use tsc, esbuild, Vite, or webpack locally and want MCP agents to consume build errors as JSON.
When should I use io.github.Dave-London/pare-build?
Use it when a build fails during ship prep or integration testing and you want the agent to iterate on diagnostics without full log pastes.
How do I add io.github.Dave-London/pare-build to my agent?
Install @paretools/build via npm, configure stdio MCP in your client, and ensure the relevant build CLI is installed in the project you open.