Clojure MCP Server

If you already use Clojure MCP, the clojure mcp mcp server is the piece that lets your assistant work with it directly. ClojureMCP is an MCP server that connects an LLM client (like Claude Code or Claude Desktop) to your Clojure project. It provides REPL tools and Clojure-aware editing tools designed to handle Clojure's parentheses and formatting reliably.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• read_file — Smart file reader with pattern-based exploration for Clojure files
• grep — Fast content search using regular expressions
• glob_files — Pattern-based file finding
• clojure_edit — Structure-aware editing of Clojure forms
• clojure_edit_replace_sexp — Modify expressions within functions
• file_edit — Edit files by replacing text strings
• file_write — Write complete files with safety checks
• dispatch_agent — Launch agents with read-only tools for complex searches
• architect — Technical planning and implementation guidance
• scratch_pad — Persistent workspace for structured data storage
• code_critique — Interactive code review and improvement suggestions
• Prerequisites — The Prerequisites tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: ANTHROPIC_API_KEY, OPENAI_API_KEY, GEMINI_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Clojure - Java (JDK 17 or later) - Optional but HIGHLY recommended: ripgrep for better grep and glob_files performance

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Clojure MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Clojure MCP's toolset — read_file, grep, glob_files and 9 more — is a fair guide to whether it matches your workflow. It is maintained by bhauman; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.