Skip to main content
Glama
bhayanak
by bhayanak

Related Servers

Alternatives to SSH MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) SSH client server that provides autonomous SSH operations for GitHub Copilot and VS Code. Enable natural language SSH automation without manual prompts or GUI interactions.
      20
      2
      MIT
    • 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables AI assistants to manage SSH terminal sessions, execute commands, and automate server operations through natural language, with multi-tab support and session persistence.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to perform development operations on remote servers via SSH, including executing commands, managing files, and browsing directories.
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An SSH MCP server that enables users to connect to and manage remote servers directly from Claude Code. It provides tools to execute commands, monitor connection status, and dynamically manage server configurations through natural language.
      10
      137 npm
      6
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for remote Linux server administration via SSH, integrating with Claude Code to manage Ubuntu/Debian servers.
      2
      -

    TDQS

    A3.6/5.0

    Scored across 23 tools

    Disambiguation4/5

    Tools are generally well-differentiated by resource and action (e.g., request_approval vs approve_request vs list_pending_approvals form a clear workflow). However, with 23 granular tools, some operational overlap exists between transfer_file and sftp_* operations, and the background job suite requires careful reading to distinguish from standard command execution.

    Naming Consistency3/5

    While all tools use snake_case with clear verbs, the prefix conventions are inconsistent: SSH session tools use ssh_* (ssh_connect, ssh_list_sessions) but host operations use bare verbs (list_hosts, get_host_facts); SFTP operations use sftp_* while file transfer uses unprefixed transfer_file. This mixed convention forces agents to read carefully.

    Tool Count3/5

    At 23 tools, this falls into the borderline-heavy range (16-25). While the server covers a complex domain (governed SSH access with approval workflows, background jobs, and certificate management), the surface feels granular—session management alone uses four distinct tools, suggesting potential for consolidation (e.g., combining list/poll/cancel into a job management tool).

    Completeness3/5

    Core workflows for approvals, background jobs, and sessions are complete, but notable gaps exist: there are tools to add/remove SSH keys and issue/revoke certificates, but no corresponding list_ssh_keys or list_certs to inspect current state. Similarly, SFTP supports delete and list but lacks explicit upload/download (relying on the separate transfer_file tool).

    Maintenance

    ActivityInactive
    ResponsivenessNo issues