Skip to main content
Glama
Sign In
InfraMCP

SSH MCP Server

by InfraMCP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to SSH MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-windows-server

      mukul975
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to control Windows systems through natural language commands, providing 200+ automation tools for system control, file operations, web automation, and more.
      60
      MIT

    • jcas-mcp

      johnnyclem
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to control macOS applications through AppleScript and JavaScript for Automation, including arbitrary script execution and pre-built app command shortcuts. It also supports safe mode, command previews, search, and registry extension via JSON manifests.
      28
      MIT

    • @qirabot/mcp

      qirabot
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to control mobile and desktop devices with natural language, including running automation tasks, taking screenshots, and managing devices.
      6
      5 npm
      MIT

    • TermPipe MCP

      wbind-core
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants with direct terminal access to execute commands, manage files, and run persistent REPL sessions. It features automated installation scripts that educate AI assistants on its capabilities for seamless integration.
      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

    C2.5/5.0

    Scored across 15 tools

    Disambiguation2/5

    Five of fifteen tools are explicit 'Legacy compatibility' duplicates of newer tools with near-identical descriptions (get_running_processes vs ssh_get_running_processes, execute_ssh vs ssh_execute_ssh, execute_sudo vs ssh_execute_sudo, cache_credentials vs ssh_setup_credentials). An agent must guess whether the legacy or ssh_-prefixed variant is the intended entry point, and the descriptions offer no behavioral difference to disambiguate.

    Naming Consistency2/5

    All names are snake_case, but two competing prefix schemes coexist (bare verb_noun vs ssh_-prefixed), and verb ordering flips between pairs like execute_ssh and ssh_execute_ssh. The result is a set where the same action is spelled two different ways, which undermines predictability.

    Tool Count3/5

    Fifteen tools is within a reasonable range for an SSH/remote-admin server, and the functional surface (execute, sudo, credentials, system info, processes, disk, services, puppet) is sensibly scoped. However, roughly a third of the count is pure legacy duplication, so the effective tool set is ~10 padded out with redundant entries.

    Completeness4/5

    Core remote-admin workflows are covered: command execution, privileged execution, credential lifecycle (setup/clear/cache), system info, processes, disk, services, and Puppet dry-run. Gaps exist around file transfer/scp and host inventory listing, but agents can work around these via the execute tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources