MCP server
by bigsy
Shadow-CLJS Build Monitor tracks ClojureScript builds in real time, showing statuses, warnings, errors, and file-specifi
Monitors Shadow-CLJS build status in real-time and reports compilation results, warnings, and errors. Helps verify that ClojureScript code changes compile successfully.
Shadow-CLJS Build Monitor is a community-built MCP server published by bigsy that provides AI assistants with tools and capabilities via the Model Context Protocol. Shadow-CLJS Build Monitor tracks ClojureScript builds in real time, showing statuses, warnings, errors, and file-specifi It is categorized under developer tools. This server exposes 1 tool that AI clients can invoke during conversations and coding sessions.
You can install Shadow-CLJS Build Monitor in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Shadow-CLJS Build Monitor is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Shadow-CLJS Build Monitor is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Shadow-CLJS Build Monitor has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
We wired Shadow-CLJS Build Monitor into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Shadow-CLJS Build Monitor has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Shadow-CLJS Build Monitor is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
According to our notes, Shadow-CLJS Build Monitor benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Shadow-CLJS Build Monitor has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
According to our notes, Shadow-CLJS Build Monitor benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
We wired Shadow-CLJS Build Monitor into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Shadow-CLJS Build Monitor has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
showing 1-10 of 67
A Model Context Protocol (MCP) server that monitors shadow-cljs builds and provides real-time build status updates.
Add the following to your Cline/Cursor/Claude whatever settings:
{
"mcpServers": {
"shadow-cljs-mcp": {
"command": "npx",
"args": [
"shadow-cljs-mcp"
],
"disabled": false,
"autoApprove": [],
"timeout": 60
}
}
}
With optional server location
{
"mcpServers": {
"shadow-cljs-mcp": {
"command": "npx",
"args": [
"shadow-cljs-mcp",
"--host",
"localhost",
"--port",
"9630"
],
"disabled": false,
"autoApprove": [],
"timeout": 60
}
}
}
The --host and --port arguments are optional. If not provided, the server will default to connecting to localhost:9630.
This MCP server connects to a running shadow-cljs instance and tracks build progress, failures, and completions. It provides an MCP tool that LLMs can use to verify build status after making changes to ClojureScript files.
Add the following to your LLM's notes file (e.g., CLAUDE.md, cursorrules.md):
After any edits to ClojureScript files, use the shadow-cljs-mcp server's get_last_build_status tool to verify the build succeeded:
<use_mcp_tool>
<server_name>shadow-cljs-mcp</server_name>
<tool_name>get_last_build_status</tool_name>
<arguments>
{}
</arguments>
</use_mcp_tool>
This will show:
- Build status (completed/failed)
- Which files were compiled
- Any errors or warnings
- Build duration and metrics
Successful build:
{
"status": "completed",
"resources": 317,
"compiled": 1,
"warnings": 0,
"duration": 0.609,
"compiledFiles": [
"path/to/your/file.cljs (505ms)"
]
}
Failed build:
{
"status": "failed",
"message": "Build failed",
"details": {
// Error information
}
}
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.