Skip to main content
Glama
tufantunc

SSH MCP Server

by tufantunc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to SSH MCP Server

No user-submitted related servers found.

    Related Servers

    • SSH MCP Server

      vilasone455
      F
      license
      A
      quality
      D
      maintenance
      A local Model Context Protocol server that allows LLMs to securely execute shell commands on remote Linux and Windows systems via SSH connections.
      6
      25 npm
      2
      -

    • SSH MCP Server

      aaronckj
      A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that enables LLMs to execute shell commands on remote Linux and Windows systems via SSH with configurable timeout and authentication options.
      6,170 npm
      MIT

    • stela-mcp

      Sachin-Bhat
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server for secure local system operations, enabling shell command execution and file management via a standardized interface.
      14
      1
      Apache 2.0

    • SSH MCP Server

      mfangtao
      A
      license
      B
      quality
      C
      maintenance
      A server that enables remote command execution over SSH through the Model Context Protocol (MCP), supporting both password and private key authentication.
      1
      1 npm
      2
      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

    A3.7/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools are clearly distinct: read-command vs run-command vs privileged-command have clear boundaries (read-only vs arbitrary vs sudo). However, list-connections and list-sessions could be confused; both are about listing, but one lists profiles, the other sessions within a profile. The descriptions help, but the tool names are close.

    Naming Consistency3/5

    Tool names mix hyphenated (list-connections) and underscore conventions (open_session? Actually all are hyphenated). The naming pattern is verb-noun, e.g., list-connections, open-session, read-session-output, which is consistent. However, sftp-upload and sftp-download use a noun-verb pattern (sftp as noun, upload as verb) which is a minor deviation. Also, 'open-session' vs 'close-session' is symmetric, but 'read-session-output' is longer than others. Overall, mostly consistent but with a few deviations.

    Tool Count4/5

    11 tools is within the ideal range for an SSH MCP server. Each tool covers a distinct aspect: connection/session management, execution (read/run/privileged), signal, and file transfer. The count feels appropriate, neither sparse nor bloated.

    Completeness4/5

    The tool surface covers the main lifecycle: connection discovery, session management, command execution with safety tiers, signaling, and file transfer. Minor gaps exist: no explicit tool for listing files (though read-command can do it), no session cleanup aside from close-session, and no sftp directory operations. But agents can work around these with run-command/read-command.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources