Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@axle-mcprepair the sorry statements in this Lean proof"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
axle-mcp
An MCP server that exposes the AXLE (Axiom Lean Engine) CLI as tools for AI assistants like Claude.
AXLE is a remote API for Lean 4 proof engineering — it can check, repair, simplify, extract, and transform Lean theorems without requiring a local Lean installation.
Tools
Tool | Description |
| List available Lean environments (versions + Mathlib) |
| Validate Lean code and report errors/warnings/info |
| Check that a candidate proof matches a formal statement |
| Split a file into one-theorem-per-unit with rich metadata |
| Auto-repair broken proofs (replaces |
| Remove redundant tactics and clean up proof steps |
| Find counterexamples to false theorems via property-based testing |
| Replace proof bodies with |
| Replace |
| Lift |
| Lift |
| Convert between |
| Rename declarations and update all references |
| Combine multiple Lean snippets into one file |
| Standardize Lean file formatting |
Requirements
Python 3.11+
mcpPython package (pip install mcp)The
axleCLI installed and accessible
Installation
1. Install dependencies
pip install mcp2. Clone this repo
git clone https://github.com/Vilin97/axle-mcp
cd axle-mcp3. Register with Claude Code
claude mcp add axle -s user \
-e AXLE_BIN=/path/to/axle \
-e AXLE_DEFAULT_ENVIRONMENT=lean-4.28.0 \
-- python /path/to/axle-mcp/server.py4. Register with Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"axle": {
"command": "python",
"args": ["/path/to/axle-mcp/server.py"],
"env": {
"AXLE_BIN": "/path/to/axle",
"AXLE_DEFAULT_ENVIRONMENT": "lean-4.28.0"
}
}
}
}Configuration
Environment variable | Default | Description |
|
| Path to the axle binary |
|
| Default Lean environment for all tools |
Usage examples
Once registered, Claude can use these tools directly. Some examples of what you can ask:
"Check if this Lean theorem compiles" →
axle_check"Repair the sorry'd proofs in this file" →
axle_repair_proofs"Turn this proof into a problem set by replacing proofs with sorry" →
axle_theorem2sorry"Does this theorem have a counterexample?" →
axle_disprove"Extract each theorem into its own self-contained snippet" →
axle_extract_theorems"Merge these two Lean files into one" →
axle_merge
Common parameters
Most tools accept these optional parameters:
environment— Lean environment to use (runaxle_environmentsto list available ones)names— comma-separated declaration names to process (default: all)indices— comma-separated 0-based indices to processtimeout— max execution time in seconds (default: 120)ignore_imports— ignore import mismatches between the code and the environment
How it works
Each MCP tool wraps the corresponding axle CLI command, passing Lean source code via stdin and returning the structured JSON response from the AXLE API. Tools that require multiple file arguments (verify-proof, merge) write temporary files automatically and clean them up after the call.
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.