get_last_build_status
Get the status of the last shadow-cljs build including any warnings or errors. Call this after making edits to ClojureScript files to verify if the build succeeded or failed.
LABSCO 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
USE CASES
01
Confirming an edit actually compiled
After changing a ClojureScript file, the last build's outcome is read back with its warnings and errors, so a broken namespace surfaces immediately rather than at the next page reload.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"shadow-cljs-mcp": {
"command": "npx",
"args": [
"shadow-cljs-mcp"
]
}
}
}npx
TERMINAL
npx shadow-cljs-mcp
