Skip to main content
Glama

Related Servers

Alternatives to Linux MCP daemon

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      MCP server for Webmin system administration. 61 tools across 12 modules covering system monitoring, services, users, cron, packages, files, storage (SMART + LVM), security (Fail2ban), MySQL databases, Webmin ACL, and disk quotas. Four-tier safety framework with safe mode on by default. Python, MIT license, Docker and local deployment supported.
      61
      9
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Remote Linux operations via SSH, exposed as an MCP server, with tools for filesystem, systemd, Docker, network, and more, using per-user AD authentication and optional sudo elevation.
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Turns any Linux server into an AI-agent-accessible machine over HTTPS, allowing MCP clients like ChatGPT, Claude, and Grok to securely control files, run shell commands, inspect system state, query SQLite, and work with git behind a bearer token.
      74 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Self-hosted Linux server control integration that lets remote MCP clients authenticate through persistent OAuth and invoke file, patch, command, terminal, Git, and image tools. Clients can also subscribe to targeted, signed event notifications for experimental event-driven workflows.
      Apache 2.0

    TDQS

    A4.1/5.0

    Scored across 48 tools

    Disambiguation4/5

    Tools are grouped by domain prefixes (docker/, files/, disks/, etc.) and each has a clearly distinct purpose, with descriptions that explicitly cross-reference sibling tools to guide selection. Some overlap exists in listing tools (e.g., processes/list vs processes/top, multiple disk tools) but descriptions resolve ambiguity effectively.

    Naming Consistency4/5

    All names follow a consistent namespace/identifier pattern using lowercase and slashes (e.g., files/list, docker/containers, network/ping). The pattern mixes verb-style and noun-style identifiers, so it is not a pure verb_noun convention, but the structure is predictable throughout.

    Tool Count2/5

    48 tools is far above the typical 3–15 range and well into the 'too many' category. While the server covers a broad Linux administration domain, many tools are very granular (e.g., seven disk-related tools) and could be consolidated without losing functionality.

    Completeness2/5

    Significant lifecycle gaps exist: no file delete, move, or copy; no user creation/modification; no Docker container creation, image pull, or build; no package installation. These missing operations will cause agent failures for common administrative tasks, though read-heavy coverage and mutation via grants are present.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing