Clj-kondo FAQs

Question 1

What file types can Clj-kondo MCP lint?

Accepted Answer

Clj-kondo MCP can lint .clj, .cljs, and .edn files, allowing for comprehensive code quality checks across your Clojure projects.

Question 2

What are the parameters for the 'lint_clojure' tool call?

Accepted Answer

The 'lint_clojure' tool call accepts parameters like 'file' (the absolute path to the file, directory, or classpath to lint), 'configDir' (optional absolute path to a clj-kondo configuration directory), and 'level' (optional, sets the linting level to 'warning' or 'error').

Question 3

How does Clj-kondo MCP handle configuration?

Accepted Answer

By default, Clj-kondo MCP uses clj-kondo which automatically looks for configuration in the `.clj-kondo` directory in the current and parent directories. This can be overridden by explicitly specifying the 'configDir' parameter.

Question 4

How do I configure Clj-kondo MCP?

Accepted Answer

Configuration typically involves adding the server to your MCP settings file (e.g., cline_mcp_settings.json) and specifying the command and arguments to run the server. Example configurations are provided in the tool documentation.

Question 5

What is Clj-kondo MCP?

Accepted Answer

Clj-kondo MCP is a Model Context Protocol (MCP) server that provides clj-kondo linting capabilities for Clojure, ClojureScript, and EDN files. It's designed to integrate with environments like Claude where native linting is unavailable.

Clj-kondo

Clj-kondo

Key Features

Use Cases

Key Features

Use Cases