Skip to main content
Glama
shuakami

mcp-ssh

by shuakami
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-ssh

No user-submitted related servers found.

    Related Servers

    • SSH MCP Server

      uarlouski
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to securely execute commands, transfer files, and manage port forwarding on remote servers via SSH.
      132 npm
      37
      Apache 2.0

    • SSH MCP Server

      zibdie
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to securely connect to and manage remote servers via SSH, supporting command execution, file transfers via SFTP, and multi-server management with both password and SSH key authentication.
      9
      77 npm
      2
      MIT

    • ssh-mcp-server

      ZachFlint
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to securely execute remote SSH commands, perform file transfers, and monitor system status through a standardized interface. It features robust security controls including command whitelisting, blacklisting, and credential isolation to prevent unauthorized operations.
      10
      9 npm
      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/5.0

    Scored across 23 tools

    Disambiguation5/5

    Tools target distinct operations: connection lifecycle, file transfers (single/batch), background execution, tunnels, and terminal sessions. No two tools have overlapping purposes, making selection unambiguous.

    Naming Consistency2/5

    Most tools follow camelCase (e.g., executeCommand, downloadFile), but two terminal tools use snake_case with a prefix (mcp_ssh_mcp_createTerminalSession, mcp_ssh_mcp_writeToTerminal), breaking consistency. This mixed convention reduces predictability.

    Tool Count5/5

    23 tools cover a broad SSH domain—connections, file transfers (single/batch), background tasks, tunnels, and terminal sessions—without redundant or excessive tools. Each tool serves a clear purpose.

    Completeness4/5

    Core SSH workflows (connect, execute, transfer, tunnel, terminal) are well covered. Minor gaps exist, such as no directory listing or file editing commands, but these are non-essential for typical SSH operations.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources