Skip to main content
Glama
powershell-mcp
by IMRRD

Related Servers

Alternatives to powershell-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to securely manage and execute commands on remote Windows servers via WinRM, including PowerShell execution, system information retrieval, and service management.
      6
      18 PyPI
      6
      MIT
    • 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
      Not graded
      quality
      B
      maintenance
      Enables coding agents to work on Windows through persistent PowerShell sessions, surgical file editing, code search, background job execution, and web research while avoiding context-heavy GUI automation.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to operate Windows through persistent PowerShell sessions, dual-channel desktop perception, element-level UIA, CDP browser control, verified actions, and failure self-healing.
      33
      1
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to execute PowerShell commands, manage files, inspect projects, run Git operations, and monitor system information on Windows through a local MCP server.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to operate and monitor Windows workspaces through native tools for filesystem operations, PowerShell execution, background tasks, Windows services, GPU telemetry, PDF generation, and a built-in web gateway/dashboard.
      24 npm
      2
      MIT

    TDQS

    B3.2/5.0

    Scored across 20 tools

    Disambiguation3/5

    Several tools overlap around execution: run_powershell, run_program, and start_execution all run local code/executables; ssh_exec/winrm_exec overlap with start_remote_batch for remote commands; read_execution_output and read_output_log both page output. Descriptions do distinguish shell vs direct, durable vs one-shot, and single vs batch, but an agent must carefully choose and misselection is plausible.

    Naming Consistency3/5

    All names are snake_case, but the pattern is mixed: verb_noun (run_powershell, list_services, start_execution), noun_verb (ssh_exec, sftp_upload), noun-only (system_info, runtime_capabilities), and status suffixes (remote_batch_status, execution_status). Still readable, but not a predictable convention throughout.

    Tool Count3/5

    20 tools sits in the heavy 16-25 band for a server whose core purpose could be served by fewer primitives. The remote batch, local execution lifecycle, and output-log management families each add surface area, and while most tools earn a role, the set feels over-expanded for the apparent scope.

    Completeness4/5

    Coverage is broad: local shell/direct execution, service inspection/control, system info, SSH/WinRM/SFTP remote operations, batch lifecycle, local execution lifecycle, and output log read/delete. Minor gaps such as remote file listing or richer service configuration exist but are workaroundable via run_powershell or ssh_exec.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data