Lean LSP MCP
Related Servers
Alternatives to Lean LSP MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI coding agents to perform Lean 4 formal verification, navigate project symbols offline, and inspect C FFI bindings.51Apache 2.0
- AlicenseBqualityDmaintenanceMCP server for agentic interaction with the Lean theorem prover via LSP, providing tools for understanding, analyzing, and interacting with Lean projects.2121MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI-driven formal proof search in Lean 4 by submitting theorems with sorry placeholders and running parallel LLM agents whose proposed edits are verified by the Lean compiler until a machine-checked proof is produced. Also provides Mathlib theorem search and job/attempt management tools.1MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with language-aware code analysis through the Language Server Protocol, enabling tasks like getting code insights and diagnostics.8 npm192MIT
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to access Language Server Protocol operations such as hover, definitions, references, and rename through typed MCP tools.2Apache 2.0
- AlicenseNot gradedqualityDmaintenanceExposes type-aware code navigation and fast file search to AI agents via language servers, enabling definitions, references, symbols, and file lookup without reading entire codebases.1,908 npmMIT
TDQS
Scored across 22 tools
Most tools target distinct LSP operations (goals, hover, diagnostics, references, completions, widgets, build), and descriptions clarify their scope. However, there is a cluster of search tools (lean_loogle, lean_leanfinder, lean_leansearch, lean_local_search, lean_hammer_premise), and the two natural-language search tools lean_leanfinder and lean_leansearch are genuinely easy to confuse.
Every tool follows the same lean_ prefix with snake_case verb/noun naming (lean_build, lean_hover_info, lean_file_outline, lean_get_widgets). The convention is uniform throughout with no deviations.
22 tools is on the heavy side, but the Lean LSP domain legitimately encompasses many distinct operations (search, diagnostics, goals, widgets, profiling, verification). Each tool maps to a real capability, though the multiple search variants push it past ideal scope.
The surface covers the core Lean development lifecycle: build, diagnostics, hover, goals, term goals, search, references, completions, code actions, run code, and widgets. Minor gaps exist (e.g. no rename/format operations), but agents can work around these for most workflows.