Skip to main content
Glama
Windows Diagnostics MCP Server

Windows Diagnostics MCP Server

by jackalterman

Related Servers

Alternatives to Windows Diagnostics MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to safely query and manage Windows services, processes, event logs, and system information, with write actions disabled by default.
      6
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Exposes Windows system information and control tools including hardware stats, network details, and process monitoring. It enables AI applications to retrieve real-time data about CPU, memory, drives, and active system processes.
      12
      GPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to perform comprehensive Windows system health diagnostics, security checks, developer workflows, and maintenance tasks via 85 tools with actionable recommendations, over MCP and OpenAI-compatible HTTP.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to gather read-only Windows stability evidence — display-driver timeouts, live dumps, bug checks, WHEA and Kernel-Power events, driver inventory, sensor, process, memory and disk state — through eight fixed, non-elevated collector tools. This lets an agent correlate a crash on one incident timeline without any ability to modify the system.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to retrieve structured information about the local Windows machine, including system specifications, resource health, developer tools, and AI environment, all through a secure, read-only interface.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to analyze Windows crash dumps by providing structured data on exceptions, threads, modules, and source context, with safe patch, build, and test execution.
      5
      MIT

    TDQS

    B3.2/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific diagnostic areas like startup programs, BSOD events, registry health, and system uptime. However, some overlap exists between 'analyze_system_stability' and 'get_system_diagnostics', which could cause confusion as both provide system-wide assessments.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern throughout, such as 'analyze_startup_programs', 'get_bsod_events', and 'scan_security_risks'. The only minor deviation is 'find_orphaned_entries', which uses 'find' instead of a more common verb like 'scan' or 'get', but overall naming is highly predictable.

    Tool Count5/5

    With 11 tools, the count is well-scoped for a Windows diagnostics server, covering various aspects like registry analysis, system events, security, and stability. Each tool appears to serve a specific diagnostic function without redundancy, making the set appropriately sized for the domain.

    Completeness4/5

    The tool set provides comprehensive coverage for Windows diagnostics, including registry health, system events, security risks, and component scans. A minor gap is the lack of tools for real-time monitoring or automated repair actions, but core diagnostic workflows are well-covered without dead ends.