1. Conduid
  2. AI
  3. shadow-cljs
MCP server · AI

shadow-cljs

A Model Context Protocol server for monitoring shadow-cljs builds

Unclaimed ai
39Low

Scored 5 months ago · breakdown

About shadow-cljs

shadow-cljs is an MCP server published by git+Bigsy in the AI category: a Model Context Protocol server for monitoring shadow-cljs builds.

Install

Install
npx shadow-cljs-mcp
Claude Code
claude mcp add shadow-cljs-mcp -- npx -y shadow-cljs-mcp
npx
npx -y shadow-cljs-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about shadow-cljs

Powered by Claude · Grounded in docs

I know everything about shadow-cljs. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

4 checks have not been run yet.

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)

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About shadow-cljs

How do I install shadow-cljs?

Run npx shadow-cljs-mcp, then add the server to your MCP client's configuration.

Is shadow-cljs safe to use with an AI agent?

Its trust score is 39 out of 100 (low). It passes 1 of the 2 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is shadow-cljs still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.