clojure-mcp
MCP ServerFree** - Clojure development tools, direct access to the running program via REPL.
Capabilities11 decomposed
nrepl-connected live code evaluation with repair
Medium confidenceExecutes Clojure code directly against a running nREPL server with automatic error repair capabilities. Uses a multimethod-based tool system that sends code to the REPL, captures output/errors, and applies heuristic-based fixes (e.g., missing imports, syntax corrections) before re-evaluating. This enables AI assistants to iteratively refine code within the live development environment without round-tripping through file saves.
Implements bidirectional nREPL integration with automatic error repair heuristics, allowing AI to iteratively refine code within the live runtime context rather than treating evaluation as a one-shot operation. Uses multimethod dispatch to route tool calls directly to nREPL, enabling stateful evaluation across multiple tool invocations.
Differs from static code analysis tools by operating on live runtime state; more powerful than generic REPL clients because it couples evaluation with AI-driven error recovery and repair suggestions.
file-aware code editing with s-expression replacement
Medium confidenceProvides structured code editing via two complementary tools: clojure_edit for full-file transformations and clojure_edit_replace_sexp for surgical S-expression replacement. Uses tree-sitter or similar AST parsing to identify and replace specific S-expressions by pattern matching, preserving formatting and context. Integrates with file write safety checks to prevent accidental overwrites and validates syntax before persisting changes.
Combines full-file and S-expression-level editing via a unified multimethod interface, with safety checks that validate syntax and respect directory allowlists before persisting. Uses pattern-based S-expression matching to enable surgical edits without requiring full AST traversal.
More precise than line-based editing because it understands Clojure's S-expression structure; safer than direct file overwrites because it validates syntax and enforces access control via configuration.
multi-tool orchestration via multimethod dispatch system
Medium confidenceImplements a multimethod-based tool system where each tool registers implementations for five core multimethods: tool-name, tool-description, tool-input-schema, tool-execute, and tool-category. This architecture enables dynamic tool registration, composition, and execution without tight coupling between tools. Tools are discovered and invoked through a unified dispatch mechanism, allowing new tools to be added by implementing the multimethod interface.
Uses Clojure's multimethod system to enable dynamic tool registration and dispatch without requiring a central tool registry. Each tool is self-contained and implements a standard interface, allowing tools to be added/removed without modifying core server code.
More extensible than hardcoded tool lists because new tools can be added by implementing the multimethod interface; more flexible than plugin systems because tools are first-class Clojure functions.
project structure inspection and analysis
Medium confidenceAnalyzes Clojure project structure by inspecting the file system, reading deps.edn/project.clj, and querying the nREPL for loaded namespaces and dependencies. Exposes project metadata including source paths, dependencies, and namespace topology through a structured inspection tool. Enables AI assistants to understand project layout and make context-aware decisions about code generation and refactoring.
Combines static file analysis (deps.edn parsing) with dynamic nREPL introspection to build a complete project context model. Uses multimethod dispatch to route inspection requests to both file system and REPL backends, providing a unified view of project structure.
More comprehensive than static analysis alone because it includes runtime namespace state; more accurate than REPL-only inspection because it validates against declared dependencies in deps.edn.
configurable tool and prompt filtering with edn-based policy
Medium confidenceImplements a configuration system that reads .clojure-mcp/config.edn files to selectively enable/disable tools, prompts, and resources at runtime. Uses a multimethod-based tool registration system where each tool is registered conditionally based on configuration predicates (tool-id-enabled?, prompt-name-enabled?, etc.). Supports directory allowlisting to restrict file system access and feature flags for bash execution and scratch pad persistence.
Uses EDN-based declarative configuration to filter tools at registration time, rather than applying runtime guards. Integrates with the multimethod tool system to conditionally register tools based on configuration predicates, enabling zero-overhead filtering for disabled tools.
More flexible than hardcoded security policies because configuration is per-project; more efficient than runtime permission checks because filtering happens at tool registration, not invocation.
bash command execution with optional nrepl fallback
Medium confidenceExecutes shell commands via a bash tool that can route execution either directly to the OS shell or through nREPL's bash-over-nrepl capability (configurable via get-bash-over-nrepl). Captures stdout/stderr and exit codes, enabling AI assistants to run build tools, package managers, and system utilities. Respects directory allowlists to prevent arbitrary file system access.
Provides dual execution modes (native bash vs. nREPL-based) configurable per project, allowing flexibility in restricted environments. Integrates with the directory allowlist system to enforce file system access policies at the shell level.
More flexible than pure Clojure evaluation because it can invoke external tools; safer than unrestricted shell access because it respects configuration-based allowlists and can be disabled entirely.
file system operations with pattern-based search and safety checks
Medium confidenceProvides file read/write operations (read_file, file_write) with pattern-based search capabilities (grep, glob_files, LS). Uses ripgrep for efficient text search and respects directory allowlists to prevent unauthorized file access. Implements write safety checks to validate file paths and prevent overwrites of critical files. Supports reading files with pattern matching to extract specific sections.
Combines file I/O with pattern-based search via a unified tool interface, enforcing directory allowlists at the tool level rather than relying on OS-level permissions. Uses ripgrep for efficient text search while maintaining compatibility with fallback grep implementations.
More efficient than naive file scanning because it uses ripgrep for search; safer than unrestricted file access because it validates paths against configuration allowlists before any operation.
mcp server lifecycle management with factory-based tool registration
Medium confidenceImplements the core MCP server using a factory pattern where build-and-start-mcp-server coordinates startup with factory functions for tools, prompts, and resources. Uses the multimethod-based tool system to dynamically register tools at server initialization, with each tool implementing five core multimethods (tool-name, tool-description, tool-input-schema, tool-execute, etc.). Manages server lifecycle including initialization, tool registration, and shutdown.
Uses a factory pattern with multimethod dispatch to enable extensible tool registration without modifying core server code. Decouples tool implementation from server lifecycle, allowing tools to be added/removed via configuration and factory functions.
More modular than monolithic server implementations because tools are registered via factories; more flexible than static tool lists because registration is driven by configuration and factory functions.
prompt and resource management via mcp protocol
Medium confidenceExposes AI prompts and resources through the MCP protocol, allowing AI clients to discover and use context-specific prompts for Clojure development. Implements prompt filtering via configuration (prompt-name-enabled?) to selectively enable prompts per project. Resources are registered similarly, enabling AI assistants to access project-specific documentation or templates.
Integrates prompts and resources into the MCP protocol layer, allowing AI clients to discover and use them without additional API calls. Uses configuration-based filtering to selectively expose prompts per project.
More discoverable than hardcoded prompts because they're exposed via MCP; more flexible than static documentation because prompts can be customized per project via configuration.
scratch pad persistence and repl state management
Medium confidenceProvides optional scratch pad functionality (controlled via get-scratch-pad-load configuration) that persists REPL state across sessions. Enables AI assistants to maintain context and intermediate results across multiple interactions. Integrates with nREPL to save and restore namespace state, allowing long-running development sessions to preserve accumulated definitions and data.
Provides optional state persistence that integrates with nREPL's serialization capabilities, allowing REPL state to be saved and restored across sessions. Uses configuration flags to enable/disable persistence without code changes.
More convenient than manual state management because persistence is automatic; more flexible than ephemeral REPL sessions because state can be preserved across restarts.
code formatting and style enforcement via cljfmt integration
Medium confidenceIntegrates with cljfmt (Clojure code formatter) to enforce consistent code style across generated and edited code. Uses configuration (get-cljfmt) to enable/disable formatting. Applies formatting rules to code before writing to files, ensuring that AI-generated code adheres to project style guidelines. Supports custom cljfmt configuration files.
Integrates cljfmt as a post-processing step for code generation and editing, ensuring that all AI-generated code is automatically formatted before being written to files. Uses configuration flags to enable/disable formatting per project.
More automatic than manual formatting because it's applied to all generated code; more consistent than ad-hoc style enforcement because it uses cljfmt's standardized rules.
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with clojure-mcp, ranked by overlap. Discovered automatically through the match graph.
Files
** - Enables agents to quickly find and edit code in a codebase with surgical precision. Find symbols, edit them everywhere.
Mistral Code Enterprise
Your AI coding copilot powered by state-of-the-art Mistral coding models
serena
A powerful MCP toolkit for coding, providing semantic retrieval and editing capabilities - the IDE for your agent
NVIDIA: Nemotron 3 Super
NVIDIA Nemotron 3 Super is a 120B-parameter open hybrid MoE model, activating just 12B parameters for maximum compute efficiency and accuracy in complex multi-agent applications. Built on a hybrid Mamba-Transformer...
elisp-dev-mcp
** - elisp (Emacs Lisp) development support tools, running in Emacs.
Qwen2.5-Coder 32B
Alibaba's code-specialized model matching GPT-4o on coding.
Best For
- ✓Clojure developers using AI assistants for REPL-driven development
- ✓Teams building AI agents that need to validate code changes in real-time
- ✓Interactive development workflows where immediate feedback is critical
- ✓AI-assisted refactoring workflows requiring precise code manipulation
- ✓Developers who need to apply targeted changes across multiple files
- ✓Teams using AI agents for code generation that must integrate with existing codebases
- ✓Developers building custom extensions to clojure-mcp
- ✓Teams that need tool-specific customization
Known Limitations
- ⚠Repair heuristics are limited to common patterns; complex semantic errors require manual intervention
- ⚠Requires an active nREPL server — cannot evaluate code in isolation
- ⚠Error context is limited to REPL output; stack traces may be truncated for large errors
- ⚠S-expression matching relies on pattern syntax; complex nested structures may be ambiguous
- ⚠Formatting preservation is best-effort; some whitespace normalization may occur
- ⚠No built-in merge conflict resolution for concurrent edits
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
About
** - Clojure development tools, direct access to the running program via REPL.
Categories
Alternatives to clojure-mcp
Are you the builder of clojure-mcp?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →