Skip to main content
Glama
johannschiffer

SysFlow MCP

by johannschiffer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to SysFlow MCP

No user-submitted related servers found.

    Related Servers

    • linux-diag-mcp

      ErenOzgu
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets an AI assistant inspect a Linux machine through ten fixed read-only tools covering load, memory, disks, processes, ports, interfaces, systemd units, the journal, and allowlisted log files. All output is size-capped, control-character-stripped and secret-redacted, and nothing in the package can write to the system.
      MIT

    • Enterprise Infrastructure &

      Maneesh-Rajbhar
      A
      license
      A
      quality
      C
      maintenance
      Provides read-only access to host system metrics (CPU, memory, disk), Docker container health/logs, and sandboxed log file analysis via MCP tools, enabling AI agents to monitor enterprise infrastructure safely.
      3
      MIT

    • mcp-linux-tools

      gerard-kanters
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to perform controlled Linux system administration tasks like reading logs, managing services, cron jobs, WordPress, and executing sandboxed Python code, with strict security constraints.
      29
      2
      GPL 2.0

    • 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
      -
    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.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a clearly distinct area: system resources, log tailing, systemd services, and systemd timers. The service and timer tools are related but their descriptions make the boundary explicit.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: check_system_resources, tail_logs, inspect_systemd_services, inspect_systemd_timers. There are no mixed conventions or vague standalone verbs.

    Tool Count4/5

    Four tools are focused and each has a clear purpose, but the set is somewhat thin for a general system diagnostics server. Additional common operations could reasonably be expected.

    Completeness4/5

    Core diagnostic areas are covered: resources, logs, services, and timers. Minor gaps exist around process listing, network status, or journal-specific queries, but agents can work around them with the provided tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources