Uyuni MCP Server

The Uyuni MCP Server is a Model Context Protocol (MCP) server implementation that bridges the gap between Large Language Models (LLMs) and the Uyuni configuration and infrastructure management solution.

This project allows AI agents or MCP-compliant clients (such as Gemini CLI or Claude Desktop) to securely interact with your Uyuni server. The Uyuni MCP server enables users to manage their Linux infrastructure using natural language. Instead of navigating the web UI or writing complex API scripts, you can simply ask your AI assistant to perform tasks like getting system details, checking for updates, or scheduling maintenance.

Key Capabilities This server exposes a suite of tools that allow LLMs to:

• Inspect Infrastructure: Retrieve lists of active systems and view system information.
• Manage Updates: Identify systems with pending security updates or CVEs and schedule patch applications.
• Execute Actions: Schedule patches, system updates and reboots.

It is designed to be run as a container remotely (HTTP) or locally (stdio), offering a streamlined way to integrate AI-driven automation into your system administration workflows.

Table of Contents

• Tool List
• Getting Started
  • Configuring the Server
  • Running the Server
• Security
  • OAuth 2.0
  • Best Practices
• Feedback
• License
• Disclaimer

Tool List

• list_systems: Fetches a list of active systems from the Uyuni server, returning their names and IDs.
• get_system_details: Gets details of the specified system.
• get_system_event_history: Gets the event/action history of the specified system.
• get_system_event_details: Gets the details of the event associated with the especified server and event ID.
• find_systems_by_name: Lists systems that match the provided hostname.
• find_systems_by_ip: Lists systems that match the provided IP address.
• get_system_updates: Checks if a specific system has pending updates (relevant errata).
• check_all_systems_for_updates: Checks all active systems for pending updates.
• list_systems_needing_update_for_cve: Finds systems requiring a security update for a specific CVE identifier.
• list_systems_needing_reboot: Fetches a list of systems from the Uyuni server that require a reboot.
• get_unscheduled_errata: Lists applicable and unscheduled patches for a system.
• list_activation_keys: Retrieves a list of available activation keys for bootstrapping new systems.
• list_all_scheduled_actions: Fetches a list of all scheduled, in-progress, completed, or failed actions.
• list_system_groups: Fetches a list of system groups from the Uyuni server.
• list_group_systems: Lists the systems in a system group.
• schedule_pending_updates_to_system: Checks for pending updates on a system, schedules all of them to be applied.
• schedule_specific_update: Schedules a specific update (erratum) to be applied to a system.
• add_system: Bootstraps and registers a new system with Uyuni using an activation key.
• remove_system: Decommissions and removes a system from Uyuni management.
• schedule_system_reboot: Schedules a reboot for a specified system.
• cancel_action: Cancels a previously scheduled action, such as an update or reboot.
• create_system_group: Creates a new system group in Uyuni.
• add_systems_to_group: Adds systems to a system group.
• remove_systems_from_group: Removes systems from a system group.

Getting Started

To use the Uyuni MCP Server, follow these two main steps:

1. Configuring the Server: Set up the connection details for your Uyuni instance.
2. Running the Server: Choose one of the provided methods to launch the server (e.g., as a container or a local script) and configure your MCP client how to connect to and interact with the server.

Configuring the Server

Cre

... View full README on GitHub