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

    • 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

    B3.3/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools have clearly distinct resource+action targets; lifecycle verbs (start/stop/restart/reload/enable/disable/mask/unmask) are distinct, and listing tools split by domain (units, timers, jobs, sessions, failed units). Minor overlap exists between unit_status_tool and unit_show_tool, and between system_status_tool and failed_units_tool, but descriptions clarify their boundaries.

    Naming Consistency4/5

    Almost all names follow a consistent snake_case <subject>_<action>_tool pattern (unit_start_tool, timer_list_tool, journal_query_tool), which is predictable. Small deviations like list_jobs_tool and hostinfo_tool break the pattern slightly but remain readable and unambiguous.

    Tool Count4/5

    21 tools is on the heavier side but each maps to a real systemd operation: unit lifecycle, journal querying, timers, jobs, failed units, system/host/session status. No obvious redundant tool; scope is broad but coherent for a systemd administration server.

    Completeness4/5

    Strong lifecycle coverage: list/status/show/start/stop/restart/reload/enable/disable/mask/unmask, plus file write/remove, daemon-reload, journal, timers, jobs, failed units, and system/host/session status. Minor gaps like reset-failed, unit kill, or journal maintenance exist but core admin workflows are covered.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources