Skip to main content
Glama
uzhaoy

winrm-mcp

by uzhaoy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to winrm-mcp

No user-submitted related servers found.

    Related Servers

    • win-mcp-server

      Chillwind132
      A
      license
      Not graded
      quality
      A
      maintenance
      A Windows MCP server for remote administration over WinRM/NTLM, enabling management of files, services, registry, events, certificates, processes, network, and more on AD-joined Windows hosts from MCP clients.
      1
      MIT

    • winvm-mcp

      Gabriel-Lacorte
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives an LLM full control over a VMware-hosted Windows VM: lifecycle, snapshots, remote execution, file transfer, and kernel debugging.
      MIT

    • kd-mcp

      uzhaoy
      A
      license
      B
      quality
      D
      maintenance
      Controls kd.exe for KDNET kernel debugging on Windows, often paired with winrm-mcp for guest VM setup over WinRM.
      9
      MIT

    • Rikune

      Last-emo-boy
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for reverse engineering Windows executables and related binary formats, offering static analysis, Ghidra-assisted function recovery, plugin-driven tooling, and optional isolated Windows runtime execution.
      3 npm
      241
      MIT

    • Aragorn

      alfarom256
      A
      license
      Not graded
      quality
      D
      maintenance
      A direct kernel debugger MCP server for Windows security research that connects to VM kernels via kdnet using DbgEng COM interfaces. It exposes over 60 tools for memory inspection, breakpoint management, and coordinated execution control between the host and target VM.
      3
      Do What The F*ck You Want To Public
    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 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: shell session management, file transfer, debugging, reboot, process execution, health check, and command execution. No overlap between tools; an agent can easily differentiate.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun or verb_preposition_noun pattern, all lowercase with underscores. Examples: close_shell, copy_from_guest, run_ps. No mixing of styles.

    Tool Count5/5

    With 12 tools covering shell sessions, file transfer, debugging, reboot, process execution, command execution, and health check, the count is well-scoped for a WinRM remote management server. Each tool earns its place.

    Completeness4/5

    The tool surface covers core WinRM operations: shell management, file transfer, debugging, reboot, process execution, and health check. Minor gaps exist (e.g., no tool to list running processes or manage services), but the set is complete for its primary use case.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources