fedora-agents
Related Servers
Alternatives to fedora-agents
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables 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.292GPL 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to interact with the Linux desktop through desktop notifications, interactive dialogs, shell command execution, and privileged command execution.14 npm5MIT
- AlicenseNot gradedqualityDmaintenanceEnables remote Linux VM management via SSH with automatic safety checks for destructive commands, supporting password authentication and sudo operations.1MIT
- FlicenseNot gradedqualityAmaintenanceLets AI agents manage local virtual machines: create macOS and Linux VMs on Apple silicon and WSL distros on Windows, start/stop, clone, back up, and run commands inside them.4,006-
- AlicenseAqualityAmaintenanceYour sysadmin co-pilot — an AI that administers Linux through typed, approval-gated, Ed25519-audited actions instead of shell strings. Reference implementation of the LACS standard.512MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage Proxmox VE clusters, LXC containers, snapshots, services, and Tailscale mesh status.1MIT
TDQS
Scored across 19 tools
Each tool targets a distinct resource and action, with the vm_* and backup_* prefixes clearly separating the two domains. Minor overlap exists between backup_create with vm-snapshot type and vm_snapshot, but the descriptions are clear enough to avoid major confusion.
Tool names mostly follow a consistent resource_action pattern in snake_case, such as vm_start, vm_destroy, backup_create, and backup_restore. Small deviations like vm_snapshot using a noun instead of a verb and the bare `help` tool prevent a perfect score.
With 19 tools, the server is on the heavier side but covers two related domains: VM lifecycle/export and backup management. Each tool earns its place, so the count is reasonable even if slightly above the ideal sweet spot.
The VM workflow is well covered with status, start, stop, destroy, exec, copy, snapshot, clone, verify, export, and import. The backup workflow is also complete with create, list, restore, verify, clean, and status, leaving no obvious dead ends for the stated purpose.