{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-clj-kondo-mcp","slug":"clj-kondo-mcp","name":"clj-kondo-MCP","type":"mcp","url":"https://github.com/Bigsy/clj-kondo-MCP","page_url":"https://unfragile.ai/clj-kondo-mcp","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-clj-kondo-mcp__cap_0","uri":"capability://tool.use.integration.clojure.code.linting.via.mcp.protocol","name":"clojure code linting via mcp protocol","description":"Exposes clj-kondo linting capabilities through the Model Context Protocol (MCP), allowing AI models and tools to invoke static analysis on Clojure code without direct subprocess management. Implements MCP server transport layer that wraps clj-kondo's analysis engine, translating linting results into structured JSON responses that conform to MCP resource and tool schemas for seamless integration with Claude, other LLMs, and MCP-compatible clients.","intents":["I want my AI assistant to lint Clojure code in real-time as part of a conversation or workflow","I need to integrate clj-kondo analysis into an MCP-based agent without managing subprocess calls directly","I want to expose Clojure linting as a standardized tool that any MCP client can consume"],"best_for":["Clojure developers using Claude or other MCP-compatible AI models","Teams building MCP servers that need Clojure code quality checks","AI agents that need to validate Clojure syntax and style during code generation workflows"],"limitations":["Limited to clj-kondo's rule set — cannot enforce custom linting rules not supported by clj-kondo","Requires clj-kondo binary to be installed and available in PATH; no pure-JVM fallback","MCP protocol overhead adds latency compared to direct clj-kondo CLI invocation","No built-in caching of lint results across multiple invocations — each request re-analyzes code"],"requires":["clj-kondo binary installed (any recent version)","Node.js 16+ (for MCP server runtime)","MCP-compatible client (Claude, or custom MCP client implementation)"],"input_types":["Clojure source code (text)","File paths or directory paths","clj-kondo configuration (EDN format)"],"output_types":["Structured linting diagnostics (JSON)","Line/column error positions","Rule violation messages with severity levels"],"categories":["tool-use-integration","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-clj-kondo-mcp__cap_1","uri":"capability://code.generation.editing.real.time.clojure.syntax.and.style.validation","name":"real-time clojure syntax and style validation","description":"Performs on-demand static analysis of Clojure code to detect syntax errors, style violations, and common mistakes using clj-kondo's rule engine. Parses Clojure source text, applies configurable linting rules (unused variables, incorrect function arity, deprecated APIs, etc.), and returns diagnostics with precise line/column positions and severity levels (error, warning, info). Configuration is read from .clj-kondo/config.edn if present, allowing per-project customization.","intents":["I want to validate Clojure code syntax before execution to catch errors early","I need to enforce team style guidelines and catch common mistakes in generated Clojure code","I want to identify unused variables, incorrect function calls, and deprecated API usage"],"best_for":["Clojure developers integrating linting into AI-assisted coding workflows","Teams using Claude or MCP clients to generate or review Clojure code","Agents that need to validate generated Clojure before execution"],"limitations":["Cannot perform semantic analysis beyond clj-kondo's rule set (e.g., no type checking without external tools)","Linting speed depends on clj-kondo's performance; large files may incur multi-second latency","Configuration must be manually placed in .clj-kondo/config.edn; no programmatic rule override in MCP calls","Does not provide auto-fix suggestions — only reports violations"],"requires":["clj-kondo binary installed and in PATH","Clojure source code as text input","Optional: .clj-kondo/config.edn in project root for custom rules"],"input_types":["Clojure source code (text/string)","File paths (for batch linting)"],"output_types":["Diagnostic objects with line, column, message, severity","Summary counts of errors/warnings"],"categories":["code-generation-editing","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-clj-kondo-mcp__cap_2","uri":"capability://tool.use.integration.mcp.tool.schema.exposure.for.clojure.linting","name":"mcp tool schema exposure for clojure linting","description":"Registers clj-kondo linting as a callable MCP tool with a defined JSON schema, allowing MCP clients (like Claude) to discover, invoke, and handle linting requests as first-class tool calls. Implements MCP's tools/list and tools/call handlers, translating tool invocation parameters (code text, file paths) into clj-kondo subprocess calls and marshaling results back as structured JSON responses. Enables natural language requests like 'lint this code' to be routed to the linting engine without explicit model prompting.","intents":["I want Claude or another MCP client to automatically lint code when I ask it to review or generate Clojure","I need linting to be discoverable as a tool in the MCP ecosystem so clients can invoke it autonomously","I want to avoid manual prompt engineering to get models to use linting — it should be a native capability"],"best_for":["MCP client developers integrating Clojure support","Teams using Claude with MCP servers for code review workflows","Builders creating AI agents that need autonomous code quality checks"],"limitations":["Tool schema is static — cannot dynamically adjust parameters based on clj-kondo version","MCP clients must support tool calling; older or minimal clients may not invoke tools","No built-in rate limiting or request queuing — high-volume linting requests may overwhelm the server","Tool discovery is one-time at connection; adding new linting modes requires server restart"],"requires":["MCP-compatible client with tool-calling support","clj-kondo binary installed","Node.js 16+ for MCP server"],"input_types":["Tool invocation parameters (code text, file paths, optional config overrides)"],"output_types":["MCP tool result JSON with diagnostics array","Error responses with MCP error codes"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-clj-kondo-mcp__cap_3","uri":"capability://code.generation.editing.configurable.linting.rule.application","name":"configurable linting rule application","description":"Respects project-level .clj-kondo/config.edn configuration files to customize which linting rules are enabled, disabled, or configured with specific parameters. Reads configuration from the project directory, merges it with clj-kondo's defaults, and applies the resulting rule set during analysis. Supports rule-level configuration such as severity overrides, exclusion patterns, and rule-specific options (e.g., max function arity warnings).","intents":["I want to enforce team-specific Clojure style guidelines without modifying the linter itself","I need to suppress certain linting rules for legacy code while enforcing others for new code","I want to customize rule severity (e.g., treat unused variables as warnings instead of errors)"],"best_for":["Teams with established Clojure coding standards","Projects migrating to stricter linting gradually","Organizations needing per-project linting customization"],"limitations":["Configuration must be manually created and maintained in .clj-kondo/config.edn","No programmatic rule override via MCP tool parameters — configuration is file-based only","Changes to config.edn require server restart to take effect (no hot-reload)","Complex rule configurations may be difficult to debug if clj-kondo validation fails"],"requires":[".clj-kondo/config.edn file in project root (optional; uses defaults if absent)","Valid EDN syntax in configuration file","clj-kondo binary that supports the configuration version"],"input_types":["EDN configuration file"],"output_types":["Applied rule set (implicit in linting results)"],"categories":["code-generation-editing","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-clj-kondo-mcp__cap_4","uri":"capability://automation.workflow.batch.file.and.directory.linting","name":"batch file and directory linting","description":"Accepts file paths or directory paths as input and performs linting on multiple Clojure files in a single MCP call. Recursively traverses directories, identifies .clj, .cljs, and .cljc files, and returns aggregated diagnostics for all files with file-level grouping. Enables efficient bulk analysis of codebases without requiring separate tool calls per file.","intents":["I want to lint an entire Clojure project or directory in one operation","I need to generate a comprehensive linting report for code review across multiple files","I want to check a codebase for violations before committing or deploying"],"best_for":["Code review workflows that need full-codebase analysis","CI/CD pipelines integrating Clojure linting checks","Agents analyzing large Clojure projects for quality metrics"],"limitations":["Batch linting latency scales with codebase size; large projects may take 10+ seconds","No built-in result streaming — entire result set is buffered before returning","Directory traversal respects .gitignore if present, but no other filtering options","No progress reporting during batch analysis — clients must wait for completion"],"requires":["File system access to read Clojure source files","clj-kondo binary installed","Valid file or directory paths"],"input_types":["File paths (string)","Directory paths (string)"],"output_types":["Aggregated diagnostics grouped by file","Summary statistics (total errors, warnings, files analyzed)"],"categories":["automation-workflow","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-clj-kondo-mcp__cap_5","uri":"capability://data.processing.analysis.structured.diagnostic.output.with.severity.levels","name":"structured diagnostic output with severity levels","description":"Returns linting results as structured JSON with detailed diagnostic objects including file path, line number, column number, rule name, message, and severity level (error, warning, info). Each diagnostic is a discrete object with all metadata needed for programmatic handling, enabling clients to filter, sort, or aggregate violations by severity, rule type, or file. Severity levels align with LSP (Language Server Protocol) conventions for compatibility with IDE tooling.","intents":["I want to programmatically filter linting results by severity (e.g., show only errors, not warnings)","I need to aggregate linting violations by rule type to identify patterns","I want to integrate linting results into a dashboard or report with sortable/filterable diagnostics"],"best_for":["Developers building linting dashboards or reports","CI/CD systems that need to parse and act on linting results","Agents that need to prioritize fixes based on severity"],"limitations":["Severity levels are fixed by clj-kondo; cannot customize severity per rule via MCP","No built-in grouping or aggregation — clients must implement their own sorting/filtering logic","Diagnostic objects are flat; no hierarchical structure for related violations","Column numbers may be approximate for multi-byte characters in some edge cases"],"requires":["JSON parsing capability in client","Understanding of diagnostic schema (file, line, column, rule, message, severity)"],"input_types":["Clojure source code"],"output_types":["JSON array of diagnostic objects","Each diagnostic: {file, line, column, rule, message, severity}"],"categories":["data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":25,"verified":false,"data_access_risk":"high","permissions":["clj-kondo binary installed (any recent version)","Node.js 16+ (for MCP server runtime)","MCP-compatible client (Claude, or custom MCP client implementation)","clj-kondo binary installed and in PATH","Clojure source code as text input","Optional: .clj-kondo/config.edn in project root for custom rules","MCP-compatible client with tool-calling support","clj-kondo binary installed","Node.js 16+ for MCP server",".clj-kondo/config.edn file in project root (optional; uses defaults if absent)"],"failure_modes":["Limited to clj-kondo's rule set — cannot enforce custom linting rules not supported by clj-kondo","Requires clj-kondo binary to be installed and available in PATH; no pure-JVM fallback","MCP protocol overhead adds latency compared to direct clj-kondo CLI invocation","No built-in caching of lint results across multiple invocations — each request re-analyzes code","Cannot perform semantic analysis beyond clj-kondo's rule set (e.g., no type checking without external tools)","Linting speed depends on clj-kondo's performance; large files may incur multi-second latency","Configuration must be manually placed in .clj-kondo/config.edn; no programmatic rule override in MCP calls","Does not provide auto-fix suggestions — only reports violations","Tool schema is static — cannot dynamically adjust parameters based on clj-kondo version","MCP clients must support tool calling; older or minimal clients may not invoke tools","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.22,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:02.371Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=clj-kondo-mcp","compare_url":"https://unfragile.ai/compare?artifact=clj-kondo-mcp"}},"signature":"mIscAcnP43hNJ1HD2kVOfx3ZS3jxO9HnH3PgCWV6ey1nZWQFBjqQ8A8OLkpR774sYKttFp2Nl8ToyXdBgsPaDg==","signedAt":"2026-06-22T09:57:30.108Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/clj-kondo-mcp","artifact":"https://unfragile.ai/clj-kondo-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=clj-kondo-mcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}