Skip to main content
Glama
ChromiaProject

Chromia LSP MCP

Official
by ChromiaProject
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Chromia LSP MCP

No user-submitted related servers found.

    Related Servers

    • karellen-lsp-mcp by karellen

      karellen-lsp-mcpofficial

      karellen
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides LLM clients with structured code intelligence through LSP servers, enabling queries for definitions, references, call hierarchies, and more.
      3
      Apache 2.0

    • 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.
      7 npm
      192
      MIT

    • VSCode Language Server MCP

      aaddrick
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Exposes VSCode's Language Server Protocol features through MCP, enabling AI assistants to perform language-aware operations like symbol navigation, reference tracking, safe renaming, type information retrieval, and hover documentation across codebases.
      -

    • lsp-mcp

      OpticLM
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to connect to Language Server Protocol servers as a headless editor, exposing LSP capabilities like diagnostics, rename, and formatting through MCP tools and resources.
      40 npm
      MIT

    • universal-lsp

      developerz-ai
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to query language intelligence over MCP, including definitions, references, symbols, and code relationship graphs across many languages, all in one native process with no external language servers.
      Apache 2.0
    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

    A4.1/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool addresses a distinct LSP operation, but save_document and open_document have identical descriptions, creating potential confusion about their respective roles. Hover, completions, code actions, diagnostics, and lifecycle tools are otherwise clearly separated.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern with get_ for queries and open/save/close for document management. Minor inconsistencies exist: start_lsp lacks 'server' while restart_lsp_server includes it, and get_info_on_location is more verbose than sibling get_ tools.

    Tool Count5/5

    10 tools appropriately cover server lifecycle, document lifecycle, and core LSP queries without redundancy or bloat. This is well within the ideal 3-15 range for a focused MCP server.

    Completeness4/5

    The tool set covers the essential LSP workflow: start server, open documents, retrieve diagnostics, hover info, completions, and code actions. However, common LSP features like go-to-definition, find references, formatting, and rename are absent, leaving notable gaps for a full language server experience.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources