clojure-mcp

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.

Depending on your LLM client, ClojureMCP can either:

- Provide acomplete set of Clojure aware code assistance toolsfor desktop chat apps like Claude Desktop, or
- Fill in Clojure-specific gaps forCLI assistantsthat already have great file editing and shell tools (such as REPL integration + Clojure-aware edits).
- Install ClojureMCP (clojure -Ttools install-latest ...).
- Register it as an MCP server in your LLM client.

If you're using a CLI assistant, you'll usually prefer to keep the CLI's native file editing tools and use ClojureMCP mainly for REPL integration (and as an editing fallback).

If you're using a desktop chat app, you'll typically use the full ClojureMCP toolchain.

- Clojure REPL Connection- which repairs delimiters prior to evaluation
- Clojure Aware editing- Using parinfer, cljfmt, and clj-rewrite
- Optimized set of tools for Clojure Development

Install ClojureMCP using the Clojure tools installer:

clojure -Ttools install-latest :lib io.github.bhauman/clojure-mcp :as mcp

This installs ClojureMCP globally, makingclojure -Tmcp startavailable from any directory.

CLI coding assistants (Claude Code, Codex, Gemini CLI) already have great inline-diff editing and shell tools.

Consider adding ClojureMCPwith the:cli-assistprofile if you want:

- Structural editing fallback- clojure-mcp-light can repair parens after an edit succeeds, but can't help when the find/replace match string doesn't match the code (happens <5% of the time, but can throw off the LLM). Structural editing targets forms by type and name, avoiding this problem.
- First-class REPL tool- LLMs tend to use MCP tools more readily than CLI commands, which may lead to more frequent REPL usage.

Adding ClojureMCP to clojure-mcp-light can provide an enhanced Clojure development experience for CLI assistants.

# Claude Code claude mcp add clojure-mcp -- clojure -Tmcp start :config-profile :cli-assist # OpenAI Codex codex mcp add clojure-mcp -- clojure -Tmcp start :config-profile :cli-assist # Google Gemini CLI gemini mcp add clojure-mcp clojure -Tmcp start :config-profile :cli-assist

Prefer clojure-mcp's editing/reading tools?If you let the agent drive and care less about the native inline diff, swap:cli-assistfor:cli-assist-full. It makesread_file,clojure_edit,clojure_edit_replace_sexp, andparen_repairfirst-class (instead of fallbacks) and instructs the assistant to doallClojure-file edits through them — which sidesteps the host editor's "file modified since read" conflict without any permission configuration. (Power users who want a hard guarantee can additionally add Claude Codepermissions.denyrules like"Edit(//.clj)"so the native editor can't touch Clojure files at all.)

clojure -Tmcp start :config-profile :cli-assist

{"jsonrpc":"2.0","method":"notifications/tools/list_changed"} {"jsonrpc":"2.0","method":"notifications/tools/list_changed"} {"jsonrpc":"2.0","method":"notifications/resources/list_changed"} {"jsonrpc":"2.0","method":"notifications/prompts/list_changed"}

chat-session-resume*: Restores context from a previous conversation

- Reads the PROJECT_SUMMARY.md file
- Callsclojure_inspect_projectfor current project state
- Retrieves the previous session summary from scratch pad
- Provides a brief 8-line summary of where things left off
- Accepts an optionalchat_session_keyparameter (defaults to"chat_session_summary")
- At the end of a productive conversation, invoke thechat-session-summarizeprompt
- The assistant will store a comprehensive summary in the scratch pad
- This summary persists across sessions thanks to the scratch pad's global state
- When continuing work, invoke thechat-session-resumeprompt
- The assistant will load all relevant context and provide a brief summary
- You can then continue where you left off with full context

You can maintain multiple parallel conversation contexts by using custom keys:

# For feature development chat-session-summarize with key "feature-auth-system" # For bug fixing chat-session-summarize with key "debug-memory-leak" # Resume specific context chat-session-resume with key "feature-auth-system"

This enables switching between different development contexts while maintaining the full state of each conversation thread.