Shadow-cljs Mcp
About
Monitors shadow-cljs builds and provides real-time build status updates.
Details
- Author
- Bigsy
- Downloads
- 244
- Categories
- Developer Tools, Other
Jump to
- Provides a single get_last_build_status tool.
- Returns build status (completed/failed) and compiled files.
- Shows detailed error and warning information.
- Includes build duration and metrics.
- Defaults to connecting to localhost:9630.
- Requires a running shadow-cljs instance.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Shadow-cljs McpCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install by adding the server configuration to your MCP client settings (e.g., Cline, Cursor, Claude) using the npx command. Optionally provide --host and --port arguments if your shadow-cljs instance is not on localhost:9630. After each ClojureScript file edit, instruct your LLM to call the get_last_build_status tool to verify the build succeeded. Add the tool call example to your LLM’s notes file (e.g., CLAUDE.md, cursorrules.md).
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.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"shadow-cljs mcp": {
"shadow-cljs-mcp": {
"command": "npx",
"args": [
"shadow-cljs-mcp"
],
"disabled": false,
"autoApprove": [],
"timeout": 60
}
}
}
}McpServers
{
"shadow-cljs-mcp": {
"command": "npx",
"args": [
"shadow-cljs-mcp"
],
"disabled": false,
"autoApprove": [],
"timeout": 60
}
}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 } } }
{ "mcpServers": { "shadow-cljs-mcp": { "command": "npx", "args": [ "shadow-cljs-mcp", "--host", "localhost", "--port", "9630" ], "disabled": false, "autoApprove": [], "timeout": 60 } } }
The--hostand--portarguments are optional. If not provided, the server will default to connecting tolocalhost: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
{ "status": "completed", "resources": 317, "compiled": 1, "warnings": 0, "duration": 0.609, "compiledFiles": [ "path/to/your/file.cljs (505ms)" ] }
{ "status": "failed", "message": "Build failed", "details": { // Error information } }
- 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
- Running shadow-cljs instance (defaults to localhost:9630 if not configured otherwise)
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
Create crafted UI components inspired by the best 21st.dev design engineers.
Bring agent evaluations, observability, and synthetic test set generation directly into your IDE for free with Galileo's new MCP server
An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively .
MCP server for AI Diagram Maker — generate beautiful software engineering diagrams directly inside Cursor, Claude Desktop, Claude Code, or any MCP-compatible AI agent
ALAPI MCP Tools,Call hundreds of API interfaces via MCP
AI-powered SVG animation generator that transforms static files into animated SVG components using the Allyson platform
MCP server that gives AI assistants on-demand access to 1,500+ amCharts docs, ~300 code examples, and 1000+ class API references.
APIMatic MCP Server is used to validate OpenAPI specifications using APIMatic. The server processes OpenAPI files and returns validation summaries by leveraging APIMatic’s API.
One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth.
Build and deploy full-stack Next.js apps with 98 tools for React, AWS, and MongoDB
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
