clj-kondo MCP Server
Bigsy/clj-kondo-MCP
Linting de Clojure/ClojureScript/EDN via MCP para Claude
Ver no GitHubServidor MCP que integra capacidades de linting do clj-kondo para arquivos Clojure/ClojureScript/EDN ao Claude. Permite análise estática e detecção de erros em código Clojure através de chamadas de ferramentas MCP, ideal para ambientes onde linting nativo não está disponível.
Instalação
npx convez-ai Bigsy/clj-kondo-MCP1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Validar código Clojure em tempo real durante desenvolvimento assistido por Claude
- Detectar problemas de estilo e erros em projetos ClojureScript
- Integrar análise estática clj-kondo em workflows de IA sem dependências locais
- Configurar linting customizado para bases de código Clojure complexas
Veredito

Ferramenta especializada e bem-implementada para ecossistema Clojure. Resolve um problema real (falta de linting nativo no Claude) com integração limpa via MCP. Útil apenas para equipes que trabalham com Clojure/ClojureScript.
README
A tradução para o português deste README ainda está na fila.
clj-kondo MCP Server 
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
-
Install clj-kondo: Make sure you have clj-kondo installed and available on your system PATH. See the installation instructions for your platform.
-
Install dependencies:
npm install
- 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
- For Leiningen projects: Use output of
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