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
      C
      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

    A3.5/5.0

    Scored across 19 tools

    Disambiguation4/5

    Each tool targets a distinct resource or action, with clear separation across logs, network, processes, services, files, and hardware. Minor overlap exists between get_hardware_information and get_cpu_information, and between get_journal_logs and get_service_logs, but descriptions mostly disambiguate them.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern, using get_, list_, or read_ appropriately. This makes the tool surface predictable and easy to navigate.

    Tool Count4/5

    19 tools is slightly above the ideal 3-15 range, but the scope of a Linux system server justifies covering logs, network, processes, services, files, disks, and hardware. The count is manageable and each tool has a clear purpose.

    Completeness4/5

    The tool set covers most common read-only Linux administration tasks: system info, logs, processes, services, networking, files, and disk usage. It lacks write or lifecycle operations like creating files, managing processes, or restarting services, but the consistent read-only design suggests that is intentional.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week