Skip to main content
Glama
Sign In
ssh-winrm-mcp

ssh-winrm-mcp

by bigbatmanorg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to ssh-winrm-mcp

No user-submitted related servers found.

    Related Servers

    • jakubs-mcp-tools

      Jakub2841
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for infrastructure discovery and remote management, enabling SSH command execution, file transfer, log tailing, and machine/service inventory with a companion web dashboard.
      2
      MIT

    • mcp-ssh

      zhouxiangjing
      A
      license
      A
      quality
      D
      maintenance
      MCP server for remote Linux/Unix server management via SSH, enabling command execution, system monitoring, file operations, and diagnostics through natural language.
      34
      1
      MIT

    • ssh-admin

      AlperTk
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for managing SSH connections to remote servers, providing host registry, session pool, and secure command execution with read-only protection.
      37 npm
      Apache 2.0

    • reliable-ssh-mcp

      2667741708
      F
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that enables running structured commands and fleet operations on SSH hosts, supporting secure file transfer, persistent sessions, and bastion-based discovery.
      -
    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/5.0

    Scored across 30 tools

    Disambiguation4/5

    Most tools are cleanly separated by resource (profiles, sessions, jobs, inventory, files) and action. A few boundaries are fuzzy: remote_execute vs remote_session_execute vs remote_run_program vs remote_run_script all execute things, and the distinction relies on descriptions. But the one-shot vs persistent-session vs job split is coherent enough to guide selection.

    Naming Consistency3/5

    All tools share the snake_case remote_ prefix and are readable, but verb ordering is mixed: resource-first (remote_job_start, remote_profile_create, remote_session_open) alongside action-first (remote_execute, remote_run_program, remote_run_script, remote_test). The inconsistency is tolerable but not a clean pattern.

    Tool Count2/5

    Thirty tools is heavy for the scope and pushes well past the typical 3-15 sweet spot. Job, session, profile, and inventory lifecycles each add several tools, inflating the surface more than the core purpose requires.

    Completeness4/5

    Coverage is strong: full profile CRUD (list/get/create/update/delete/rename), session lifecycle, job lifecycle, file transfer, scripts, and inventory validation are all present. Minor gaps like bulk job cleanup or richer inventory editing exist but are workaroundable.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Resources