Skip to main content
Glama
narmaku

Linux MCP Server

by narmaku
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Linux MCP Server

No user-submitted related servers found.

    Related Servers

    • Linux MCP Server

      narmaku
      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

    • Linux MCP Server

      rhel-lightspeed
      A
      license
      B
      quality
      A
      maintenance
      An MCP server for read-only Linux system administration and diagnostics on RHEL-based systems via SSH. It enables users to troubleshoot remote hosts by accessing system information, services, logs, and network configurations through natural language.
      23
      910 PyPI
      316
      Apache 2.0

    • incident-tool

      KyleCS0
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to diagnose Linux server incidents by collecting and structuring system diagnostics from multiple servers via SSH, with tools for finding incident clusters, gathering context (memory, CPU, swap, etc.), and running arbitrary commands.
      -

    • mcp-vpsobs

      0mandrock1
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only observability of a Linux host via MCP, exposing allowlisted systemd, docker, nginx, logs, disk, and cert info without shell access.
      MIT

    • homelab-mcp

      lstkhN
      A
      license
      B
      quality
      C
      maintenance
      Enables stdio MCP clients to gather read-only diagnostics and incident evidence from Linux homelabs, including health, disks, services, Docker containers, logs, and confirmation-required remediation proposals.
      10
      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

    A3.7/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes targeting specific Linux system components (CPU, memory, network, processes, services, logs, filesystems). However, there is some overlap between get_audit_logs, get_journal_logs, get_service_logs, and read_log_file which could cause confusion about which log retrieval tool to use in different scenarios.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern with snake_case throughout. The pattern is either 'get_[resource]' or 'list_[resource]' with clear, descriptive names that immediately indicate what each tool does.

    Tool Count4/5

    20 tools is slightly high but reasonable for a comprehensive Linux system monitoring server. The tools cover multiple system domains (hardware, processes, services, networking, storage, logs), and each appears to serve a specific purpose within this broad scope.

    Completeness4/5

    The toolset provides excellent read-only coverage of Linux system monitoring with tools for hardware, processes, services, networking, storage, and logs. Minor gaps exist in write/control operations (no service start/stop, process management, or configuration modification tools), but for a monitoring-focused server, the coverage is quite comprehensive.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources