Skip to main content
Glama
lin037

MCP Diagnostics

by lin037
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to MCP Diagnostics

No user-submitted related servers found.

    Related Servers

    • Diagnostics MCP Server

      Maaz0313-png
      A
      license
      Not graded
      quality
      B
      maintenance
      An HTTP MCP server providing AI agents with real-time access to all VS Code diagnostics (TypeScript, ESLint, Prettier, etc.) via 5 powerful tools including workspace health scoring.
      1
      MIT

    • Locus

      paladini
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that gives AI coding agents codebase navigation intelligence, enabling symbol lookup, reference finding, type inspection, and diagnostics through tools like locate, refs, hover, diagnostics, status, and rename.
      569 npm
      MIT

    • squiggles

      carldaws
      A
      license
      A
      quality
      A
      maintenance
      MCP server that lets your coding agent see the squiggles — LSP diagnostics, navigation, refactoring, and each server's custom superpowers
      21
      532 npm
      5
      MIT

    • TS Hover MCP

      zachsents
      A
      license
      Not graded
      quality
      B
      maintenance
      A standalone MCP server that provides TypeScript type inference and hover information using tsgo, enabling AI agents to get type details, diagnostics, references, and more without needing an editor.
      6 npm
      1
      MIT

    • mcdev-mcp

      use-ai-for-mc
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that empowers AI coding agents to work effectively with Minecraft mod development, providing static analysis of decompiled source code and runtime interaction with a running Minecraft instance.
      31
      97 npm
      14
      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.5/5.0

    Scored across 4 tools

    Disambiguation3/5

    The tools have overlapping purposes that could cause confusion. getDiagnosticsForFile and getDiagnosticsForPath both retrieve diagnostics for a single file, with the latter described as more flexible and recommended, creating ambiguity about when to use each. However, getDiagnostics and getDiagnosticsSummary serve clearly distinct purposes (all files vs. summary statistics), which helps mitigate some confusion.

    Naming Consistency5/5

    All tool names follow a consistent camelCase pattern with a clear verb_noun structure (getDiagnostics, getDiagnosticsForFile, getDiagnosticsForPath, getDiagnosticsSummary). The naming is predictable and readable throughout the set, with no deviations in style or convention.

    Tool Count5/5

    With 4 tools, the count is well-scoped for a diagnostics server. Each tool appears to serve a specific and necessary function (e.g., retrieving all diagnostics, per-file diagnostics, and summaries), making the set focused and manageable without being overly sparse or bloated.

    Completeness4/5

    The tool surface covers core diagnostics retrieval operations comprehensively, including all files, per-file, and summary views. A minor gap exists in the lack of tools for managing or clearing diagnostics (e.g., reset or update functions), but agents can likely work with the provided read-only operations for most use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources