Monitors shadow-cljs builds and provides real-time build status updates.
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
}
}
Token-efficient access to OpenAPI/Swagger specs via MCP Resources
Set up and interact with your unstructured data processing workflows in Unstructured Platform
Generate images using Amazon Nova Canvas with text prompts and color guidance.
Integrates the Nmap network scanning tool with MCP, enabling network scanning capabilities within MCP-compatible environments.
A command-line interface wrapper for the Google Gemini API, enabling interaction with Gemini's Search and Chat tools.
Empowers LLMs with real-time network traffic analysis using tshark. Requires Wireshark's tshark to be installed.
Reference / test server with prompts, resources, and tools
A template for deploying a remote MCP server on Cloudflare Workers, customizable by defining tools in the source code.
Provides developers with continuous, project-centric context awareness. Requires a TursoDB database.
Query A/B test data using the Hackle API.