Summary
The build result becomes something the agent can read, so an edit gets checked instead of assumed.
One tool, and it reads rather than acts: it reports the last build's outcome with its warnings and errors, and does not compile, watch or restart anything. That makes it the step after an edit rather than a replacement for the build itself — something has to be building for there to be a last build to report.
What it is
A single-tool reader of shadow-cljs build state: the last build's outcome with whatever warnings and errors it produced.
What you get
- get_last_build_status, which reports whether the last shadow-cljs build succeeded or failed, including any warnings and errors it raised.
Requirements
Nothing to supply — no account, no key. A shadow-cljs build for it to report on, since the tool reads a build's status rather than starting one.
Setup effort
One command — npx shadow-cljs-mcp