SSyncDev

Shadow Cljs MCP Server

A Model Context Protocol server for monitoring shadow-cljs builds

Local serverstdio

What is the Shadow Cljs MCP MCP server?

Shadow cljs mcp mcp server connects Shadow Cljs MCP to AI assistants that speak the Model Context Protocol. A Model Context Protocol server for monitoring shadow-cljs builds.

What Shadow Cljs MCP does

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

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.

Installing the shadow cljs mcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Requirements

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

Where it fits

Monitoring servers replace the paste-the-stack-trace ritual with an assistant that reads the real event, with all its surrounding context intact. Shadow Cljs MCP sits in that group. Worth comparing against the other monitoring security servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • Maintained by Bigsy.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the shadow cljs mcp mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

How to install the Shadow Cljs MCP MCP server

{
  "mcpServers": {
    "shadow-cljs-mcp": {
      "command": "npx",
      "args": [
        "shadow-cljs-mcp"
      ],
      "disabled": false,
      "autoApprove": [],
      "timeout": 60
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

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

Frequently asked questions

It connects Shadow Cljs MCP to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Shadow Cljs MCP directly.

Alternatives to the Shadow Cljs MCP MCP server

Chrome DevTools

Official

Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.

Browser AutomationTypeScript★ 48.4k

Grafana

Official

Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.

Monitoring & ObservabilityGo★ 1.7k

Sentry

Official

Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.

Monitoring & ObservabilityRemoteTypeScript★ 400

Deep Web Research

Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.

Monitoring & ObservabilityTypeScript★ 84

Playwright Cdp

Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol

Browser Automation★ 51

Sequential Thinking Tools

Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.

Monitoring & Observability★ 29