Skip to main content
Glama
jaenster

TypeScript LSP MCP

by jaenster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to TypeScript LSP MCP

No user-submitted related servers found.

    Related Servers

    • ts-language-mcp

      jgauffin
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to interact with TypeScript projects through compiler-level code intelligence, providing tools for navigation, type information, diagnostics, refactoring, and semantic search.
      29
      202 npm
      3
      Apache 2.0

    • type-atlas

      tyler-mitchell
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to navigate TypeScript, Markdown, and JSON with editor-grade features such as definitions, references, diagnostics, and code actions via the Model Context Protocol, using the local TypeScript project for each file.
      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.
      829 npm
      MIT

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

    • ts-mcp

      happydave
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to navigate and edit TypeScript/JavaScript source by named declarations, reading symbols, imports, diagnostics, and replacing code via the TypeScript AST.
      -
    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

    B3.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct LSP feature (type-checking, completions, definitions, diagnostics, hover, references, type queries, type tests, type tracing). There is no overlap or ambiguity between tools.

    Naming Consistency4/5

    Most tools follow a 'get' + noun pattern (getCompletions, getDefinition, etc.), with two exceptions: 'checkInlineCode' uses 'check' and 'runTypeTests' uses 'run'. This minor inconsistency prevents a perfect score.

    Tool Count5/5

    9 tools is an appropriate size for a TypeScript LSP server. It covers essential features without being bloated or too sparse.

    Completeness4/5

    The tools cover core LSP operations (diagnostics, hover, definition, references, completions, type queries) and even include niche features (type tracing, type tests). Missing common operations like code actions, rename, or formatting, but the set is largely complete for its apparent purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources