Skip to main content
Glama
crunchtools

io.github.crunchtools/systemd

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to io.github.crunchtools/systemd

No user-submitted related servers found.

    Related Servers

    • journalmcp

      hilliersmmain
      A
      license
      A
      quality
      B
      maintenance
      Provides read-only access to systemd units, failed units, timers, unit status and files, journal entries, boots, and system summaries through eight queries. Enables inspection and triage of systemd services without granting write access or shell execution.
      8
      MIT

    • systemd-mcp

      ArkTechNWA
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides AI assistants with safe, read-only access to Linux systemd services, including status monitoring, log querying, and dependency analysis, with optional granular permissions for service management actions.
      2
      -

    • os-control-mcp

      88plug
      F
      license
      Not graded
      quality
      B
      maintenance
      Controls a Linux host through structured interfaces like systemd, journald, and D-Bus for service management, journal queries, power operations, and more, with safety guards to prevent accidental damage.
      -

    • mcp-systemctl

      rileylsmith1997
      F
      license
      A
      quality
      D
      maintenance
      An MCP server that reports on and manages systemd services using systemctl and journalctl, enabling service listing, status, logs, and control operations.
      5
      -

    • Remote Host MCP

      0ozzzii
      F
      license
      Not graded
      quality
      A
      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.
      -
    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.6/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool maps to a distinct systemd action or query target, so an agent can reliably distinguish start/stop/restart/reload, enable/disable, mask/unmask, and status/show. The few similar-sounding tools like unit_status_tool and unit_show_tool are clearly differentiated by curated status versus full property dump.

    Naming Consistency4/5

    All tool names are snake_case and consistently end in _tool, with most unit operations following a clear unit_<action> pattern. However, the set mixes verb-first names like list_jobs_tool and daemon_reload_tool with noun-first names like timer_list_tool and system_status_tool, creating minor inconsistency.

    Tool Count3/5

    21 tools is on the heavy side for an MCP server, though systemd's broad lifecycle and query surface naturally requires many discrete operations. The count is borderline but not excessive enough to feel bloated, since most tools represent genuinely different systemd commands.

    Completeness4/5

    The toolset covers the core systemd workflow well: writing/removing unit files, enabling/disabling/masking, starting/stopping/reloading, checking status, querying the journal, and inspecting failed units/timers/jobs. Minor gaps exist such as reading the raw unit file content and tailing journal logs, but agents can accomplish most administrative tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources