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.
      3
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Provides AI agents with language-aware code analysis through the Language Server Protocol, enabling tasks like getting code insights and diagnostics.
      3 npm
      192
      MIT
    • A
      license
      Not graded
      quality
      B
      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
      B
      quality
      B
      maintenance
      Enables coding agents to drive HOL4's built-in hol lsp language server against individual SML script files, exposing proof diagnostics, goal states, evaluation, hover, definitions, symbols and completions as concise text tools. It manages server lifecycle, file syncing, proof-waiting, 1-based Unicode-aware positions, and detection of cheat usage.
      11
      BSD 3-Clause

    TDQS

    B3.4/5.0

    Scored across 22 tools

    Disambiguation3/5

    Most tools target distinct Lean/LSP operations, but there are four search-related tools (local_search, leanfinder, leansearch, loogle) plus related position-inspection tools (goal, term_goal, hover_info, declaration_file). Descriptions help distinguish them, but the overlap creates real misselection risk for an agent.

    Naming Consistency4/5

    All tool names use a consistent lean_ snake_case prefix. The underlying pattern is mostly noun/feature-based rather than strictly verb_noun, with minor awkwardness in lean_leanfinder and lean_leansearch, but overall naming is predictable.

    Tool Count3/5

    The domain is broad enough to justify many capabilities, but 22 tools is a heavy surface for an MCP server. It sits in the borderline 16-25 range and could likely be consolidated or grouped without losing much functionality.

    Completeness4/5

    The tool set covers the main Lean proof workflow: inspection, search, diagnostics, goal state, code actions, verification, profiling, and widgets. Gaps remain for full LSP coverage, such as rename/formatting operations, but core proof-development needs are well supported.

    Maintenance

    ActivityActive
    ResponsivenessSyncing