Skip to main content
Glama

Related Servers

Alternatives to Linux MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server for Linux and macOS system administration, diagnostics, and troubleshooting, supporting remote SSH execution and multi-host management.
      Apache 2.0
    • 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
      D
      maintenance
      This MCP server provides read-only Linux system diagnostics tools for inspecting system information, processes, and log snapshots. It enables AI models to analyze Linux system health, troubleshoot issues, and review security through workflow prompts and HTTP transport with API key authentication.
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      A secure, read-only MCP server for AI-powered system monitoring. It provides real-time OS metrics, config discovery, and safe log tailing to enable autonomous infrastructure audits without shell access risks.
      4
      1
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables read-only Linux system diagnostics and troubleshooting on local and remote RHEL-based systems via SSH, including services, processes, logs, network, and storage analysis.
      20
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A secure SSH-based MCP server for diagnosing remote servers. It allows AI agents to execute read-only commands and read files automatically, while requiring user confirmation for write operations.
      MIT

    TDQS

    B3.2/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools have clearly distinct targets (network, disk, processes, services, files, PCP metrics). Minor overlap exists: get_hardware_information explicitly includes CPU details while get_cpu_information is separate, and get_service_logs / get_journal_logs / read_log_file all retrieve logs, though descriptions differentiate the sources.

    Naming Consistency5/5

    All tools follow a strict snake_case verb_noun pattern (get_*, list_*, read_*), with a consistent pcp_* prefix grouping the PCP subsystem tools. No mixing of conventions or casing.

    Tool Count4/5

    23 tools is on the heavier side but the domain (comprehensive Linux system diagnostics) legitimately spans many subsystems. Nearly every tool earns its place, though a few informational getters (CPU, memory, hardware, system) could plausibly be consolidated.

    Completeness4/5

    Broad read-oriented coverage across CPU, memory, disk, network, processes, services, logs, files, and PCP performance with sensible PCP gating. Gaps are limited to write/action operations (e.g. restart service, kill process, file search), which is acceptable if the server is intentionally read-only.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week