lint_clojure
Lint Clojure/ClojureScript/EDN content using clj-kondo
LABSCO SUMMARY
The linter runs where the code already is, so the agent reads findings instead of asking you to paste them.
One tool, and it reports rather than edits — nothing in the surface applies a fix, so the correction stays a decision you or the agent make afterwards. Because configDir is a parameter, the same server answers for repositories with different clj-kondo settings without being reconfigured between them.
What it is
A single-tool wrapper around clj-kondo, the Clojure static analyser, taking a file to check and returning what it found.
What you get
- clj-kondo linting of Clojure, ClojureScript and EDN content through lint_clojure.
- A level parameter on the call, so the same file can be read for everything or narrowed to the severities you care about.
- A configDir parameter, so the project's own clj-kondo configuration governs the run rather than the defaults.
Requirements
Nothing to supply — no account, no key. A Clojure, ClojureScript or EDN file the server can reach by path, and a clj-kondo configuration directory if the project keeps one.
Setup effort
One command — npx clj-kondo-mcp
USE CASES
01
Catching Clojure lint errors before the REPL does
The file is checked in place by path, with the project's own clj-kondo configuration directory supplied on the call so the findings match what CI would report.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"clj-kondo-mcp": {
"command": "npx",
"args": [
"clj-kondo-mcp"
]
}
}
}npx
TERMINAL
npx clj-kondo-mcp
