Skip to main content
Glama

Related Servers

Alternatives to Lean LSP MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables AI coding agents to perform Lean 4 formal verification, navigate project symbols offline, and inspect C FFI bindings.
      5
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with language-aware code analysis through the Language Server Protocol, enabling tasks like getting code insights and diagnostics.
      8 npm
      192
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to access Language Server Protocol operations such as hover, definitions, references, and rename through typed MCP tools.
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Exposes 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 npm
      MIT

    TDQS

    A3.8/5.0

    Scored across 22 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow