arch-mcp-server
Related Servers
Alternatives to arch-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables an AI agent to drive a remote Linux machine over the LAN through a single TCP connection, exposing tools for shell commands, jobs, interactive PTYs, file read/write/search/transfer, process and service management, networking, packages, and power control, with optional multi-host switching. Operates without SSH or any Linux-side installation beyond one stdlib-only Python daemon, using a state-free binary protocol.MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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.1MIT
- AlicenseBqualityCmaintenanceEnables an agent to oversee and operate a fleet of Linux servers over the system ssh and Tailscale — inspecting host status, auditing configuration, tracking drift and reading history across many machines. Every mutating operation runs as a dry-run plan first and only applies after explicit confirmation of that exact plan, rolling out one host at a time with a local journal.63MIT
- FlicenseNot gradedqualityCmaintenanceControls 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.-
- AlicenseAqualityBmaintenanceEnables AI clients to operate Linux servers over SSH through user-opened, time-limited sessions without exposing passwords, providing tools for system status, logs, file reads/writes, and shell command execution with read-only and blocked-command safeguards.64MIT
- AlicenseAqualityBmaintenanceLets 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.10MIT
TDQS
Scored across 12 tools
Each tool targets a distinct resource or question: host identity (sys_info), health snapshot (sys_status), capabilities (host_capabilities), disks (fs_usage), processes (proc_list), services (svc_list/svc_status/svc_failed), logs (log_query/log_errors), packages (pkg_status) and ports (net_ports). The aggregate-vs-detail pairs (sys_status vs fs_usage/proc_list, log_query vs log_errors, svc_list vs svc_status) are explicitly framed as summary versus drill-down, so an agent can choose correctly.
All names are lower snake_case and follow a predictable domain-prefix + operation pattern (sys_, host_, fs_, proc_, svc_, log_, pkg_, net_). Within each domain the suffix consistently distinguishes list/status/query variants, so related tools sort and read together.
Twelve tools is well within the sweet spot and each covers a distinct area of host inspection. No tool feels redundant or padded; the grouping (health, systemd, logs, packages, network) is coherent for a server admin MCP.
The surface is comprehensive for read-only diagnostics: identity, health, capabilities, disk, process, service, log, package and port visibility are all present with no obvious dead ends. Minor gaps remain for a sysadmin domain (e.g. service start/stop/restart, package install/update actions, disk SMART or network interface detail), but those are arguably out of scope for a monitoring-focused server.