Build runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 19 Aug 2026.
Structured build tool output (tsc, generic commands) as typed JSON diagnostics.
What the code does
We read the source, 23 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const output = execFileSync(resolver, [cmd], {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Build
same job, measured the same wayStructured Go tool output (build, test, vet) as typed JSON diagnostics.
Pare Go ג€” Structured Go tool output (build, test, vet, fmt, mod) as typed JSON diagnostics.
Pare Build ג€” Structured build output (tsc, esbuild, vite, webpack) as typed JSON diagnostics.
Structured linting output (ESLint, format-check) as typed JSON diagnostics.
Structured Python tool output (ruff, mypy, pip-audit, pip-install) as typed JSON.
Pare Python ג€” Structured Python tool output (ruff, mypy, pip, uv, black, pytest) as typed JSON.
Structured Rust cargo operations (build, test, clippy) as typed JSON.
Structured Docker operations (ps, images, logs, build) as typed JSON.
Build — questions
Answers built from our own checks of this server.