Skip to main content
Glama
Bigsy

shadow-cljs-mcp

by Bigsy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to shadow-cljs-mcp

No user-submitted related servers found.

    Related Servers

    • clj-kondo MCP Server

      Bigsy
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that provides clj-kondo linting capabilities for Clojure/ClojureScript/EDN files, useful for environments like Claude code and desktop that lack built-in linting.
      1
      2 npm
      4
      MIT

    • MCP Rewatch

      brennancheung
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI coding assistants like Claude Code to manage long-running development processes, solving the problem where Claude Code cannot see output from processes like 'npm run dev' that don't exit immediately.
      3 npm
      2
      Apache 2.0

    • Codebase MCP Server

      cmaujean
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that analyzes application codebases with real-time file watching, providing AI assistants like Claude with deep insights into project structure, code patterns, and architecture.
      MIT

    • Xcode MCP Server

      PolarVista
      A
      license
      B
      quality
      F
      maintenance
      A Model Context Protocol server that enables AI assistants to build and test Xcode projects directly through a standardized interface, with capabilities for running tests, monitoring progress, and accessing logs in real-time.
      18
      146 npm
      53
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.

    Naming Consistency5/5

    The single tool name 'get_last_build_status' follows a clear verb_noun pattern, and there are no other tools to create inconsistency. The naming is straightforward and predictable.

    Tool Count2/5

    A single tool is too few for a server's purpose, as it severely limits functionality and suggests an incomplete or overly narrow scope. This makes the server feel thin and underdeveloped.

    Completeness2/5

    The server is severely incomplete for a build tool domain. It only provides status checking, with no tools for initiating builds, managing configurations, handling dependencies, or other essential operations, creating significant gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources