← Back to directory
P

Pare Build

Community
Structured build output as typed JSON diagnostics
GitHub source repository ↗
★ 138 Stars Category · Dev Tools Popular Source revision 57e1980e8375
49FMRS · D
Reliability
7/20
Security and permissions
7/20
Maintenance
12/20
Documentation
11/20
Setup experience
12/20

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.

Read the FMRS scoring method →

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.

Tools

The tool list has not been reviewed yet.

Setup

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"].

Fit and risk

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

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

Troubleshooting

  1. Check Node.js version >= 20
  2. Ensure npx is available or use absolute path
  3. Verify MCP client config for stdio transport correctly
  4. If connection timeouts, increase client initTimeout

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

Supported clients

Supported clients have not been confirmed yet.