Skip to main content
Glama
clj-kondo MCP Server

clj-kondo MCP Server

by Bigsy

clj-kondo MCP Server npm version

A Model Context Protocol (MCP) server that provides clj-kondo linting capabilities for Clojure/ClojureScript/EDN files. Handy for Claude code and desktop where there are no built in linting capabilities. You may want to consider editing your CLAUDE.md asking it to lint after editing.

Features

  • Lint Clojure files via MCP tool calls

  • Supports all clj-kondo analysis capabilities

  • Optional explicit configuration directory support

Related MCP server: shadow-cljs-mcp

Installation

Quick Install

npx clj-kondo-mcp

or IDE config

{
  "mcpServers": {
    "clj-kondo": {
      "command": "npx",
      "args": ["clj-kondo-mcp"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

Manual Installation

  1. Install clj-kondo: Make sure you have clj-kondo installed and available on your system PATH. See the installation instructions for your platform.

  2. Install dependencies:

npm install
  1. Build the server:

npm run build

Usage

Running the Server

node build/index.js

MCP Tool Calls

The server provides one tool:

lint_clojure - Lint Clojure/ClojureScript/EDN content

Parameters:

{
  "file": "/absolute/path/to/file.clj", // Must be absolute path - can be a file, directory, or classpath
  "configDir": "/absolute/path/to/config/dir", // Optional, must be absolute path if provided
  "level": "warning" // Optional, defaults to error level
}

The file parameter accepts:

  • A single file path (e.g. "/path/to/src/my_file.clj")

  • A directory path (e.g. "/path/to/src") - will lint all .clj, .cljs and .cljc files recursively

  • A classpath string - will lint all Clojure files in the classpath

    • For Leiningen projects: Use output of lein classpath

    • For deps.edn projects: Use output of clojure -Spath

Note: Both file and configDir parameters must be absolute paths since the MCP server runs as a separate process. Relative paths will not work correctly.

By default, clj-kondo will automatically look for configuration in the .clj-kondo directory in the current and parent directories. You can override this by specifying the configDir parameter to point to a specific configuration directory.

For more information about clj-kondo configuration, see the official documentation.

Configuration

Add to your MCP settings file (for Cline, located at ~/Library/Application Support/Code - Insiders/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json):

{
  "mcpServers": {
    "clj-kondo": {
      "command": "npx",
      "args": ["clj-kondo-mcp"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

For manual builds, use:

{
  "mcpServers": {
    "clj-kondo": {
      "command": "node",
      "args": ["build/index.js"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

Build

npm run build

Watch Mode

npm run dev

Available Tools

1 tool
lint_clojureA

Lint Clojure/ClojureScript/EDN content using clj-kondo

Inputs: file (required), configDir, level.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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 recent community issues

    Related MCP Connectors

    Related MCP Servers

    • 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
    • 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
      23 npm
      3
      MIT
    • 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
    • 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