Skip to main content
Glama
uyuni-project

Uyuni MCP Server

Official

Related Servers

Alternatives to Uyuni MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      B
      maintenance
      Enables deploying and managing infrastructure via natural language, including project/domain management, compute nodes, image deployment, and CI/CD integration.
      70
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to manage VAST Data storage infrastructure, including views, quotas, snapshots, and network configurations, through natural language commands.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables natural language management of CheckMK monitoring environments, including host/service monitoring, downtime scheduling, problem acknowledgement, and configuration management through LLM interfaces.
      GPL 3.0
    • A
      license
      A
      quality
      D
      maintenance
      MCP server that bridges AI assistants with the SUSE Linux ecosystem, enabling safe access to openSUSE Wiki, OBS, and repositories for system management.
      22
      1
      GPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to Linode cloud infrastructure, enabling the management of compute instances, databases, and networking resources through natural language. It provides a comprehensive suite of tools for resource orchestration, monitoring, and account management using stdio, SSE, or HTTP transports.
      34 npm
      21
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Your 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.
      5
      14
      MIT

    TDQS

    A4/5.0

    Scored across 18 tools

    Disambiguation4/5

    The tools have overlapping purposes, especially around updates (multiple tools for checking updates on individual systems and fleet), but descriptions clearly differentiate them by context (compact vs paginated, fleet vs individual). Some ambiguity remains for agents unfamiliar with the specific use cases.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., find_systems_by_name, get_system_details, list_systems, summarize_fleet_updates). No deviations or mixed conventions.

    Tool Count5/5

    18 tools is well-scoped for the domain of system management (systems, groups, updates, events, actions, activation keys). Each tool serves a clear purpose without unnecessary duplication.

    Completeness3/5

    The tool set covers reading and querying (systems, updates, events, groups, activation keys) comprehensively, but lacks tools for performing actions (e.g., applying updates, rebooting, modifying groups). This may be intentional for a read-only server, but it leaves gaps for full lifecycle management.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive