Back to MCP directory
publicPublicdnsLocal runtime

clj-kondo-MCP

一种提供 clj-kondo 检查功能的 Model Context Protocol 服务器,适用于 Clojure/ClojureScript/EDN 文件,对于像 Claude 代码和桌面环境这种缺乏内置检查功能的环境非常有用。

article

README

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

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
help

Runtime guide

cloud

Hosted runtime

Hosted servers run from a provider-managed environment. You usually connect the MCP client to the hosted endpoint or follow the provider's authorization flow, without keeping a local process alive

  1. Open provider connection page
  2. Authorize or copy endpoint
  3. Connect from your MCP client
terminal

Local runtime / other methods

Local servers run on your own machine or infrastructure. You normally copy the server_config into your MCP client, install the required package, and provide env variables from env_schema when needed

  1. Copy server_config
  2. Install required package
  3. Fill env variables and restart client