Skip to main content
Glama
emyk

windows-debug-mcp

by emyk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to windows-debug-mcp

No user-submitted related servers found.

    Related Servers

    • procmem

      cutlerbenjamin1-cmd
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for Windows process memory inspection/editing and crash dump analysis, enabling live memory scanning, patching, pointer resolution, disassembly, and offline dump examination via structured tool calls.
      MIT

    • Linux MCP Server

      ahmedadan
      A
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server for Linux and macOS system administration, diagnostics, and troubleshooting, supporting remote SSH execution and multi-host management.
      Apache 2.0

    • EndpointRead-MCP

      nelladath
      A
      license
      B
      quality
      B
      maintenance
      A read-only MCP server for Microsoft Intune and Entra ID that enables list, get, search, and reporting operations for tenant visibility, audits, troubleshooting, and health reporting without write actions. It includes authentication helpers, report exports, and metadata discovery tools.
      36
      1
      MIT

    • DeviceLens MCP

      Dark-Hunt3r1
      A
      license
      A
      quality
      B
      maintenance
      A local, detection-first Windows MCP server that groups Device Manager interfaces into physical devices, provides explanations, and enables read-only inspection and update auditing without modifying any devices or drivers.
      10
      GPL 3.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/5.0

    Scored across 35 tools

    Disambiguation5/5

    Each tool targets a specific diagnostic area with minimal overlap. For example, get_crash_history, get_reliability_history, and list_crash_dumps serve different purposes (event analysis, reliability timeline, dump file listing). Tools like read_registry_key and read_registry_value are clearly distinct by scope. The descriptions further clarify boundaries.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern using prefixes like get_, list_, read_, inspect_, query_, verify_, and collect_. No mixing of camelCase or inconsistent verb styles, making the set predictable for an agent.

    Tool Count4/5

    35 tools is on the higher side, but the domain of Windows debugging is broad, covering hardware, software, events, performance, and settings. The count is justified given the need for specialized tools, though some agents might find it slightly heavy. It remains within a reasonable scope without being overwhelming.

    Completeness5/5

    The tool surface covers the full lifecycle of diagnostic tasks: system overview, hardware status, software inventory, event logs, crash analysis, performance monitoring, and configuration inspection. It includes both high-level summaries and detailed queries, with no obvious gaps for the stated purpose of diagnosing crashes, stutter, and performance issues.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources