Skip to main content
Glama
Sign In
sysknife

sysknife

by lacs-project
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to sysknife

Related Servers

  • mcp-vps-toolkit

    mohammadhadijavidi
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI assistants to inspect and safely operate a Linux VPS through typed DevOps tools governed by YAML allowlists, read-only defaults, dry-run plans, secret redaction, and tamper-evident auditing.
    MIT

  • opsgate

    polymatx
    A
    license
    B
    quality
    B
    maintenance
    The safety gate between AI agents and your servers: 25 typed, policy-checked tools for services, logs, Docker, disk, ports and nginx, with human approval for changes and a hash-chained audit log.
    25
    1
    MIT

  • ServerOps MCP

    lowji194
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI clients to administer a Linux host through OAuth-secured, scope-controlled tools for diagnostics, filesystem and systemd operations, command execution, guarded networking, and managed project deployment with local owner approval.
    1
    MIT

  • Homelab MCP

    KeatonMeek
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables an OAuth-capable AI assistant to manage a self-hosted Linux server, starting with host-health and probe snapshots and optionally expanding to shell commands, bounded text-file reads/writes/moves, and asynchronous jobs through an owner-authenticated local broker. Configuration and credentials stay private on your own machine, with no hosted service or model API keys required.
    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.
    -

  • ssh-alias-mcp

    leehom0123
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI agents to SSH into Linux servers, run commands, deploy code, and manage servers via natural language, also doubles as a CLI for manual use.
    3
    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

B3.1/5.0

Scored across 58 tools

Disambiguation3/5

Most tools have tightly scoped, well-annotated purposes, but real overlaps exist: sysknife_list_installed_flatpaks and sysknife_ubuntu_list_flatpaks are near-identical, and the firewall family (get_firewall_state, get_firewall_backend_state, get_nftables_ruleset, ufw_status) plus the log family (collect_diagnostics, get_journal_log, get_service_logs) require careful reading to pick correctly. The plan/execute/doctor/audit_verify quartet is well separated by explicit cross-references.

Naming Consistency3/5

All tools share the sysknife_ prefix, but within that there are two competing conventions: noun-first read verbs (apt_history_list, app_armor_status, snap_list, ufw_status) mixed with verb-first names (get_disk_usage, list_users, get_firewall_state). A handful of top-level tools (plan, execute, doctor, history) break the pattern entirely, so an agent cannot reliably predict a name.

Tool Count2/5

58 tools is far beyond a comfortable surface for one server, and much of the bulk is per-domain read chatter (seven package-manager families, four container runtimes) that a generic plan/execute path could already reach. The count makes selection expensive and increases the chance of picking a near-duplicate.

Completeness4/5

Read coverage is genuinely broad across packages, services, networking, firewall, containers, and audit, and the plan/execute pair provides a generic mutation path so there are no dead ends. Gaps are narrower: no dedicated cron/scheduled-task detail beyond list_timers, no SELinux, and no per-service enable/disable tools outside the plan flow.

Maintenance

ActivityActive
ResponsivenessUsually handled

Resources