Skip to main content
Glama
Sign In
fedora-agents

fedora-agents

by amineutron
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to fedora-agents

No user-submitted related servers found.

    Related Servers

    • PVE

      zyx1121
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to manage Proxmox VMs and LXC containers, host port forwarding, internal dnsmasq DNS, and Caddy sites through natural language, including diff previews and rollback-aware reloads.
      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

    • nido-mcp

      Josepavese
      A
      license
      B
      quality
      A
      maintenance
      Nido is a local QEMU VM manager. Install it on your computer from https://github.com/Josepavese/nido and run nido mcp via stdio, or use npx -y nido-mcp@latest mcp with QEMU installed locally. It manages VMs on that same computer; a server hosted by Glama cannot access your local VM inventory.
      6
      2
      MIT

    • servidor-mcp

      Daniel-Riv
      A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      6
      1
      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.3/5.0

    Scored across 19 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources