Skip to main content
Glama
AndyLiner13

ts-mcp-server

by AndyLiner13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ts-mcp-server

No user-submitted related servers found.

    Related Servers

    • mcp-refactor-typescript

      Stefan-Nitu
      A
      license
      A
      quality
      B
      maintenance
      A TypeScript/JavaScript refactoring MCP server that uses the TypeScript compiler to perform safe, type-aware code transformations such as renaming, extracting functions, and organizing imports across your codebase.
      4
      323 npm
      12
      MIT

    • ts-lsp-mcp

      trophygeek
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides TypeScript 7 native language server capabilities (go to definition, find references, hover types, diagnostics) to coding agents, using the Go-based tsc compiler for fast and accurate semantic analysis.
      210 npm
      1
      MIT

    • lsp-intelligence

      perilevy
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing 29 tools across 5 layers for semantic TypeScript/JavaScript code intelligence, enabling AI agents to find references, trace impacts, guard APIs, and explain errors without text-search false positives.
      12 npm
      1
      MIT

    • agent-workspace-mcp

      c0sc0s
      A
      license
      A
      quality
      D
      maintenance
      A TypeScript-aware MCP server that provides coding agents with repository discovery, code intelligence, and web project context for local codebases. It enables deep symbol navigation, diagnostic reporting, and structural analysis of monorepos without requiring full IDE integration.
      7
      11 npm
      1
      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.8/5.0

    Scored across 40 tools

    Disambiguation5/5

    Each tool targets a specific operation in the TypeScript language server, such as completions, diagnostics, navigation, or refactoring. Descriptions clearly differentiate closely related tools like definition vs. typeDefinition and references vs. fileReferences, minimizing confusion.

    Naming Consistency3/5

    Tool names are consistently camelCase but mix verb-started (getCodeFixes, organizeImports) and noun-started (completionInfo, definition) patterns. Some verbs like 'provide' and 'get' are used for similar operations, reducing predictability.

    Tool Count3/5

    With 40 tools, the count is high but reflects the complexity of a full TypeScript language server. Each tool serves a distinct purpose, but the number exceeds the typical 3-15 range for MCP servers, making it somewhat heavy.

    Completeness5/5

    The tool surface covers all major areas: autocomplete, diagnostics, formatting, navigation, refactoring, renaming, file operations, and symbol search. No obvious gaps exist for common TypeScript development workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources