Skip to main content
Glama
Sign In
InfraMCP

Win MCP Server

by InfraMCP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Win MCP Server

No user-submitted related servers found.

    Related Servers

    • powershell-mcp

      IMRRD
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to run PowerShell commands and manage Windows services without intrusive console windows, while also supporting remote execution via SSH and WinRM.
      20
      394 npm
      1
      MIT

    • winadm-mcp

      technothatch
      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

    • connect-to-server-mcp

      vstlmkh
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to securely connect to and manage remote servers via SSH, with tools for running commands, file operations, log inspection, service management, and system monitoring under configurable access controls and audit logging.
      12
      5 npm
      1
      MIT

    • Ops MCP Server

      twine003
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to execute shell/PowerShell commands, manage files, run git and Django operations, and control IIS or systemd services on remote Windows or Linux machines over HTTP.
      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

    B3.2/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a distinct role: credentials setup/clear, targeted system queries, and PowerShell execution. The only overlap is that win_execute_powershell could also retrieve system, service, or disk information, but the dedicated getters are clearly named and scoped.

    Naming Consistency5/5

    All tools share a consistent win_ prefix followed by a verb_noun pattern such as win_get_system_info or win_execute_powershell. The convention is predictable throughout.

    Tool Count5/5

    Six tools is well-scoped for basic remote Windows host management. Each tool covers a distinct operational need without excessive fragmentation.

    Completeness4/5

    The surface covers command execution, system information, services, disk space, and credential lifecycle. Minor gaps exist around service/process mutation and file transfer, though arbitrary PowerShell execution provides a workaround.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources