Skip to main content
Glama
Bigsy

clj-kondo MCP Server

by Bigsy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to clj-kondo MCP Server

No user-submitted related servers found.

    Related Servers

    • shadow-cljs-mcp

      Bigsy
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that monitors shadow-cljs builds and provides real-time build status updates for ClojureScript projects, allowing LLMs to verify build status after making code changes.
      1
      18 npm
      3
      MIT

    • 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

    • Tafa MCP Server

      N3uraX
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready Model Context Protocol server that provides comprehensive file system management capabilities for seamless integration with Claude Desktop.
      1
      MIT

    • MCP Tools

      ZbigniewTomanek
      A
      license
      Not graded
      quality
      D
      maintenance
      A custom Model Context Protocol server that gives Claude Desktop and other LLMs access to file system operations and command execution capabilities through standardized tool interfaces.
      23
      Apache 2.0

    • YanceLint MCP Server

      xihe-lab
      A
      license
      A
      quality
      D
      maintenance
      Enables AI coding assistants like Claude Code to perform real-time code linting and get violation summaries from tools such as ESLint, Stylelint, P3C, and Checkstyle via a local server.
      3
      9 npm
      Apache 2.0
    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

    A3.8/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a single, clear purpose that is distinct by default.

    Naming Consistency5/5

    A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The naming follows a clear verb_noun pattern (lint_clojure).

    Tool Count2/5

    A single tool is too few for a server's purpose, as it limits functionality and suggests an incomplete or overly narrow scope. Typically, servers benefit from multiple tools to cover various operations within their domain.

    Completeness2/5

    The server only provides linting, which is a significant gap for a tool named after clj-kondo, as it might be expected to support other related operations like configuration management or analysis. The surface is severely incomplete for a comprehensive Clojure tooling server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources