Skip to main content
Glama

Related Servers

Alternatives to mcp-linux-tools

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI clients to operate Linux servers over SSH through user-opened, time-limited sessions without exposing passwords, providing tools for system status, logs, file reads/writes, and shell command execution with read-only and blocked-command safeguards.
      6
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to inspect and safely operate a Linux VPS through typed DevOps tools governed by YAML allowlists, read-only defaults, dry-run plans, secret redaction, and tamper-evident auditing.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI-controlled administration of remote Linux hosts and containers, including bounded shell execution, persistent PTY sessions, durable jobs/tasks, hardened filesystem access, process/service control, and resumable transfers.
      -
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI tools to perform server operations such as log inspection, system monitoring, code management, Nginx and certificate management, with support for local and remote SSH modes and built-in security controls.
      23
      72 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Gives AI agents safe, bounded, non-blocking access to Linux sysadmin inspection tasks, including CPU, RAM and disk healthchecks, memory-safe log tailing with regex filtering, and user-level systemd service and timer auditing. All operations run without sudo or unrestricted root shells, avoiding interactive pager hangs and context window flooding.
      4
      132 PyPI
      1
      MIT

    TDQS

    A3.7/5.0

    Scored across 29 tools

    Disambiguation3/5

    Most tools have clearly distinct purposes, but several boundaries overlap: reload_service and restart_service both perform a reload by default, and wp_cli overlaps with wp_cache_flush, wp_plugin_list, and wp_user_list while execute_shell_command overlaps with python_run, git_command, and mysql_query. The detailed descriptions help an agent choose, but the redundancy still creates moderate selection risk.

    Naming Consistency3/5

    Names are consistently lowercase snake_case, but the verb/noun ordering is mixed: verb-first names like read_file and create_directory sit alongside noun-first names like cron_add, service_status, and wp_plugin_list, plus get_* info tools. This is readable and predictable within subsystems, but there is no single global naming convention.

    Tool Count2/5

    With 29 tools, the set exceeds the 25+ threshold and feels heavy for its scope. Several tools are redundant, notably reload_service versus restart_service, wp_cli versus the specialized wp_* helpers, and execute_shell_command versus python_run, git_command, and mysql_query. A tighter set of around 20 tools would be clearer.

    Completeness4/5

    Core Linux administration workflows are covered: service status/reload/restart, directory and file reading, log inspection, WP-CLI operations, cron lifecycle management, SQL queries, git, and generic shell execution. Minor gaps exist, such as no dedicated file write/delete or explicit service start/stop, but execute_shell_command provides a workaround for those cases.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data