MCP Server Uyuni
UnclaimedEnabling LLMs to interact with Uyuni
Install
docker run --env-file /path/to/uyuni-config.env -p 8080:8080 ghcr.io/uyuni-project/mcp-server-uyuni:latestSet up this server
More in Developer Tools
Browse the full directoryUnclaimed listing
Is this your MCP server?
This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.
Claim this serverSecurity profile
Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works
27 of 27 tools
Documented tools (27)
From project documentation. A server handshake does not verify each tool’s description or behavior.
add_system
Bootstraps and registers a new system with Uyuni using an activation key.
add_systems_to_group
Adds systems to a system group.
cancel_action
Cancels a previously scheduled action, such as an update or reboot.
check_all_systems_for_updates
Checks all active systems for pending updates.
create_system_group
Creates a new system group in Uyuni.
find_systems_by_ip
Lists systems that match the provided IP address.
find_systems_by_name
Lists systems that match the provided hostname.
get_system_details
Gets details of the specified system.
get_system_event_details
Gets the details of the event associated with the especified server and event ID.
get_system_event_history
Gets the event/action history of the specified system.
get_system_updates
Checks if a specific system has pending updates (relevant errata).
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_group_systems
Lists the systems in a system group.
list_system_groups
Fetches a list of system groups from the Uyuni server.
list_systems
Fetches a list of active systems from the Uyuni server, returning their names and IDs.
list_systems_needing_reboot
Fetches a list of systems from the Uyuni server that require a reboot.
list_systems_needing_update_for_cve
Finds systems requiring a security update for a specific CVE identifier.
query_system_updates
Returns paginated pending updates for a specific system with optional CVE expansion and optional advisorytypes filter.
remove_system
Decommissions and removes a system from Uyuni management.
remove_systems_from_group
Removes systems from 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.
schedule_system_reboot
Schedules a reboot for a specified system.
summarize_fleet_updates
Returns low-token paginated summary of systems with pending updates.
summarize_system_updates
Returns low-token summary counts for pending updates of a specific system (optional advisorytypes filter).
Tool change history
FAQ
Questions about MCP Server Uyuni MCP Server
- How do I connect MCP Server Uyuni MCP Server to Claude?
- The listing records `docker run --env-file /path/to/uyuni-config.env -p 8080:8080 ghcr.io/uyuni-project/mcp-server-uyuni:latest` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Desktop as compatible clients.
- Is MCP Server Uyuni MCP Server free?
- The listed licence is Apache-2.0. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
- What can MCP Server Uyuni MCP Server do?
- MCP Server Uyuni MCP Server documents 27 tools to the agent, including add_system, add_systems_to_group, cancel_action. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.