Clj Kondo MCP

🚀 clj-kondo MCP Server

A Model Context Protocol (MCP) server that provides clj-kondo checking for Clojure/ClojureScript/EDN files. It's suitable for Claude coding and desktop environments where there's no built-in checking functionality. You may consider editing your CLAUDE.md file to request post-edit checks.

🚀 Quick Start

The clj-kondo MCP Server offers a convenient way to perform clj-kondo checks on Clojure files. Here's how you can get started quickly:

Quick Installation

npx clj-kondo-mcp

Or configure it in your IDE:

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

Manual Installation

1. Install clj-kondo: Ensure you have clj-kondo installed and available in your system's PATH. Check the platform-specific installation instructions.

2. Install dependencies:

npm install

3. Build the server:

npm run build

✨ Features

• Clojure File Checking: Invoke clj-kondo checks on Clojure files via MCP tools.
• Full clj-kondo Analysis Support: Support all clj-kondo analysis features.
• Optional Explicit Configuration Directory: Optionally specify an explicit configuration directory.

📦 Installation

Quick Install

npx clj-kondo-mcp

IDE Configuration

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

Manual Install

1. Install clj-kondo and ensure it's in your system's PATH. Refer to the installation guide for your platform.
2. Install dependencies:

npm install

3. Build the server:

npm run build

💻 Usage Examples

Running the Server

node build/index.js

MCP Tool Invocation

The server provides a tool:

lint_clojure - Check Clojure/ClojureScript/EDN content

Parameters:

{
  "file": "/absolute/path/to/file.clj", // Must be an absolute path, can be a file, directory, or classpath
  "configDir": "/absolute/path/to/config/dir", // Optional, must be an 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") - All .clj, .cljs, and .cljc files will be checked recursively.
• A classpath string - All Clojure files in the classpath will be checked.
  • For Leiningen projects: Use the output of lein classpath.
  • For deps.edn projects: Use the output of clojure -Spath.

⚠️ Important Note

Since the MCP server runs as a separate process, the file and configDir parameters must be absolute paths. Relative paths will not work.

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

For more information on clj-kondo configuration, refer to the official documentation.

📚 Documentation

Configuration

Add the following 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