developer-tools

Shadow-CLJS Build Monitor

bigsy

by bigsy

Shadow-CLJS Build Monitor tracks ClojureScript builds in real time, showing statuses, warnings, errors, and file-specifi

Monitors ClojureScript builds in real-time, providing detailed status information including compilation status, warnings, errors, and file-specific details for verifying build success after code changes.

github stars

3

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

Real-time build monitoringWorks with existing Shadow-CLJS setup

best for

  • / ClojureScript developers using Shadow-CLJS
  • / Verifying code changes compile without errors
  • / Debugging build failures during development

capabilities

  • / Check last Shadow-CLJS build status
  • / Report compilation warnings and errors
  • / Show which files were compiled
  • / Display build duration and metrics

what it does

Monitors Shadow-CLJS build status in real-time and reports compilation results, warnings, and errors. Helps verify that ClojureScript code changes compile successfully.

about

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.

how to install

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.

license

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.

readme

shadow-cljs-mcp

npm version

A Model Context Protocol (MCP) server that monitors shadow-cljs builds and provides real-time build status updates.

Installation

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.

Overview

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.

LLM Integration

Adding to Your LLM Notes

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

Example Tool Response

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
  }
}

Usage Notes

  • LLMs should call get_last_build_status after each ClojureScript file edit
  • Compilation errors will be shown in detail for easy debugging
  • Successful builds show which files were compiled and how long they took
  • Make sure shadow-cljs is running before starting this server

Requirements

  • Running shadow-cljs instance (defaults to localhost:9630 if not configured otherwise)

FAQ

What is the Shadow-CLJS Build Monitor MCP server?
Shadow-CLJS Build Monitor is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for Shadow-CLJS Build Monitor?
This profile displays 67 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.4 out of 5—verify behavior in your own environment before production use.

Use Cases

Extended AI Capabilities

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

Context Enhancement

Provide Claude with access to relevant context and data

Example

Load project documentation, access knowledge bases, query databases

Get more accurate, context-aware responses

Workflow Automation

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

Implementation Guide

Prerequisites

  • Claude Desktop 0.7.0+ or Cursor IDE with MCP support
  • Basic understanding of MCP architecture and capabilities
  • Access credentials for integrated services (if required)
  • Willingness to experiment and iterate on configuration

Time Estimate

15-60 minutes depending on server complexity

Installation Steps

  1. 1.Install MCP server: npm install -g [package-name] or via GitHub
  2. 2.Add server configuration to ~/.claude/mcp.json
  3. 3.Provide required credentials and configuration
  4. 4.Restart Claude Desktop to load new server
  5. 5.Test basic functionality with simple prompts
  6. 6.Explore capabilities and experiment with use cases
  7. 7.Document successful patterns for reuse

Troubleshooting

  • MCP server not loading: Check config syntax, verify installation
  • Connection errors: Check network, firewall, credentials
  • Feature not working: Read server docs, check required parameters
  • Performance issues: Monitor resource usage, check for network latency
  • Conflicts with other servers: Check port assignments, namespace collisions

Best Practices

✓ Do

  • +Read server documentation thoroughly before setup
  • +Start with simple use cases to validate functionality
  • +Test in non-production environment first
  • +Monitor resource usage and performance
  • +Keep servers updated for bug fixes and new features
  • +Document configuration for team members
  • +Use environment variables for sensitive configuration

✗ Don't

  • Don't grant overly permissive access to MCP servers
  • Don't skip reading security considerations in docs
  • Don't expose sensitive data without proper controls
  • Don't run untrusted MCP servers without code review
  • Don't ignore error messages—investigate root cause

💡 Pro Tips

  • Combine multiple MCP servers for powerful workflows
  • Create custom MCP servers for your specific needs
  • Share successful configurations with team
  • Use MCP inspector for debugging
  • Join MCP community for tips and troubleshooting

Technical Details

Architecture

Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.

Protocols

  • Model Context Protocol (MCP)
  • JSON-RPC 2.0
  • stdio or HTTP transport

Compatibility

  • Claude Desktop
  • Cursor IDE
  • Custom MCP clients

When to Use This

✓ 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.

Integration

  • Tool composition: Chain multiple MCP tools in workflows
  • Context augmentation: Provide AI with relevant external data
  • Action delegation: Let AI execute tasks on external systems
  • Bidirectional sync: Keep AI context and external systems in sync

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.

List & Promote Your MCP Server

Share your MCP server with the developer community

GET_STARTED →
MCP server reviews

Ratings

4.467 reviews
  • Alexander Bhatia· Dec 24, 2024

    Shadow-CLJS Build Monitor is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Charlotte Okafor· Dec 20, 2024

    Shadow-CLJS Build Monitor has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Arjun Gill· Dec 12, 2024

    We wired Shadow-CLJS Build Monitor into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

  • Jin Iyer· Nov 15, 2024

    Shadow-CLJS Build Monitor has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Alexander Nasser· Nov 11, 2024

    Shadow-CLJS Build Monitor is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Emma Abbas· Nov 3, 2024

    According to our notes, Shadow-CLJS Build Monitor benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.

  • Emma Martin· Oct 22, 2024

    Shadow-CLJS Build Monitor has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Nikhil Harris· Oct 6, 2024

    According to our notes, Shadow-CLJS Build Monitor benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.

  • Alexander Ndlovu· Oct 2, 2024

    We wired Shadow-CLJS Build Monitor into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

  • Alexander Abebe· Sep 25, 2024

    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

1 / 7