Build
Let your coding agent run TypeScript and generic build commands and read failures as clean JSON instead of messy terminal walls.
Overview
io.github.Dave-London/build is a Build-phase MCP server that turns tsc and generic build command output into typed JSON diagnostics for coding agents.
What is this MCP server?
- Normalizes tsc and arbitrary shell build commands into typed JSON diagnostics
- Surfaces file, line, and message fields agents can act on without regex-parsing stderr
- stdio MCP transport via npm package @paretools/build (v0.8.0)
- Part of the Dave-London Pare toolchain alongside cargo, docker, and git servers
- Pairs with agent-driven fix-and-rebuild loops in monorepos and small SaaS backends
- Server version 0.8.0 per server.schema.json
- npm identifier @paretools/build with stdio transport
- Source repository github.com/Dave-London/Pare
Community signal: 128 GitHub stars.
What problem does it solve?
Agents choke on unstructured compiler stderr, so you end up copy-pasting tsc errors by hand instead of letting the model fix them in one pass.
Who is it for?
Solo builders iterating on TypeScript or multi-command local builds inside Claude Code, Cursor, or Codex who want machine-readable compile errors.
Skip if: Teams that only need interactive terminal builds with no agent in the loop, or projects that never run tsc or scripted compile steps locally.
What do I get? / Deliverables
After you register the server, build failures arrive as parseable JSON so your agent can locate files, apply fixes, and re-run builds without you mediating every error line.
- Typed JSON diagnostic objects from tsc or configured build commands
- Agent-ready error locations and messages for automated fix loops
Recommended MCP Servers
Journey fit
Compile-and-fix loops belong in the Build phase when you are turning code into something that actually runs. tsc and backend-oriented compile steps map to backend work: types, modules, and production bundles—not landing copy or launch SEO.
How it compares
MCP build-output bridge, not a full CI platform or a replace-the-terminal task skill.
Common Questions / FAQ
Who is io.github.Dave-London/build for?
It is for indie and solo developers who use AI coding agents and want TypeScript or generic build failures exposed as structured data the model can trust.
When should I use io.github.Dave-London/build?
Use it during local backend and compile-fix cycles when tsc or custom build scripts fail and you want the agent to read diagnostics without manual copy-paste.
How do I add io.github.Dave-London/build to my agent?
Install the npm package @paretools/build, configure stdio MCP in your client, point it at the published server entry, and ensure Node and your project’s build scripts are available on the machine.