Skip to main content
Glama
oOo0oOo

Lean LSP MCP

by oOo0oOo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Lean LSP MCP

No user-submitted related servers found.

    Related Servers

    • LSP MCP

      jonrad
      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.
      6 npm
      191
      MIT

    • Deixis

      jolars
      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

    • lsp-mcp-server

      garretpremo
      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,077 npm
      MIT

    • code-intel

      claudin-io
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to perform local hybrid code search and code intelligence across a workspace, including semantic and full-text search, symbol lookup, file outlines, and caller analysis.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 23 tools

    Disambiguation3/5

    The LSP-oriented tools (goal, term_goal, hover, diagnostics, code_actions) are clearly separated, but there is a dense cluster of five Mathlib/lemma-search tools (loogle, leansearch, leanfinder, local_search, state_search) plus hammer_premise that overlap in purpose and could easily be misselected. Descriptions help, but the boundaries among 'search by signature', 'search by meaning', and 'find lemmas for goal' are subtle.

    Naming Consistency4/5

    All tools share a consistent lean_ snake_case prefix and mostly use noun phrases describing the returned information. However, a few action-style names (lean_build, lean_run_code, lean_get_widgets) and service/product names (lean_loogle, lean_leansearch) break the pure resource-noun pattern.

    Tool Count3/5

    At 23 tools the count sits in the heavy range for an MCP server, even though each tool maps to a real Lean/LSP feature. Several search and goal-analysis tools could plausibly be consolidated, so the set feels somewhat over-scoped rather than tightly curated.

    Completeness4/5

    The surface covers a broad Lean proof-development workflow: diagnostics, goals, hover docs, completions, code actions, library search, execution, verification, profiling, and widgets. Minor gaps exist, such as no way to apply the resolved code-action edits or perform workspace-wide symbol search, but most workflows do not dead-end.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources