MCP SERVEROfficialConnect your AI assistant to Uyuni to inspect Linux systems, review security updates and plan maintenance.
Uyuni MCP Server gives an AI assistant access to the Linux infrastructure managed by your Uyuni instance. Administrators can ask about system inventory, pending patches, CVE exposure and maintenance activity without writing API queries. Optional write tools extend that access to scheduling updates and reboots, registering or removing systems, and managing system groups.
It runs locally over stdio or as a self-hosted HTTP service, using a container or Python process. You need a reachable Uyuni server and an account with permissions for the tasks you allow. Local deployments use Uyuni credentials; OAuth deployments require a shared identity provider and Uyuni OIDC support.
When a report gives you a hostname or IP address, find the matching Uyuni system and inspect its hardware, network and installed products. This gives you the system record and identifiers needed to investigate the intended machine.
Toolsfind_find_get_
When a CVE needs attention, identify systems requiring its security update and inspect their pending advisories. You get an affected-system list and the update information needed to assess remediation.
Toolslist_query_
Before a maintenance window, compare pending update counts across the fleet and examine the patches applicable to individual systems, including those not yet scheduled. With write tools enabled, the assistant can schedule all pending updates for a system or a specific advisory.
Toolssummarize_check_summarize_get_query_get_
After patching, identify machines that still require a reboot and review scheduled or in-progress actions. With write tools enabled, you can schedule reboots or cancel previously scheduled actions as maintenance plans change.
Toolslist_list_
When an update or other action has not completed as expected, review its status and the affected system’s event history. Event details provide timestamps and results to help you investigate what happened.
Toolslist_get_get_
When expanding the fleet, review the activation keys available to your account. With write tools enabled and an SSH private key configured, the assistant can bootstrap and register a new system using an activation key.
Toolslist_
When a machine is being decommissioned, locate its Uyuni record before removing it from management. Removal requires write tools to be enabled and changes the system’s registration in Uyuni.
Toolsfind_find_get_
When you need to review or reorganize a managed group, inspect existing groups and their member systems. With write tools enabled, the assistant can create groups and add or remove members to reflect the intended organization.
Toolslist_list_list_
Showing all 18 Captured 23 August 2026; excludes the optional write tools.
find_systems_by_ipLook up systems by IP address and get their names, IDs and matching IP addresses.
find_systems_by_nameFind systems by hostname, including a partial hostname, and see their names and IDs. Multiple matches let you identify the intended system before requesting its details.
get_system_detailsInspect one system’s CPU, network, installed products, last boot time and identifiers.
list_activation_keysView the activation keys available to the current user, with their descriptions, for bootstrapping new systems.
list_group_systemsSee the names and IDs of systems belonging to a named group.
list_system_groupsBrowse system groups with their descriptions, IDs and system counts.
list_systemsBrowse active Uyuni systems by name and ID in a paginated list. The IDs identify systems for further inspection with other tools.
check_all_systems_for_updatesFind active systems with pending updates across the fleet, with optional update details and CVEs for each system. Results are paginated; summarize_fleet_updates provides counts when individual update details are unnecessary.
get_system_updatesSee a compact list of one system’s pending updates with counts. CVE details are omitted by default; choose query_system_updates for pagination and optional CVE details.
get_unscheduled_errataFind patches that apply to a system but have not been scheduled.
list_systems_needing_update_for_cveIdentify systems requiring a security update for a specific CVE, with each affected system listed once by name and ID.
query_system_updatesBrowse one system’s pending updates in pages, with optional CVE details and filtering by advisory type. For counts without individual update entries, choose summarize_system_updates.
summarize_fleet_updatesCompare pending update counts across systems in a paginated fleet summary. Use check_all_systems_for_updates when you also need individual update details.
summarize_system_updatesGet pending update counts for one system without individual update entries. Optional filters narrow the counts to security, product enhancement or bug fix advisories.
get_system_event_detailsInspect a specific system event’s status, timestamps and results. The event ID comes from get_system_event_history.
get_system_event_historyReview a system’s events from newest to oldest, including their type, status, summary and completion information. An optional date filter narrows the history; get_system_event_details provides more information about one event.
list_all_scheduled_actionsReview actions that are scheduled, in progress, completed or failed. Results are paginated and can be filtered by exact action type or scheduler.
list_systems_needing_rebootFind systems that require a reboot and see their names, IDs and reboot status.
No matching results.
Use this server in an app or editor you already know.
Let your MCP client start and stop the server in a local Docker container.
Have Docker available on the computer running your MCP client. Create an environment file and set UYUNI_SERVER to your Uyuni instance’s URL. For local authentication, set UYUNI_USER and UYUNI_PASS to a Uyuni account with only the permissions it needs. Use stdio for UYUNI_MCP_TRANSPORT.
Keep UYUNI_MCP_SSL_VERIFY enabled and UYUNI_MCP_WRITE_TOOLS_ENABLED false for the initial connection. Enabling write tools permits changes such as applying updates and removing systems. Keep the environment file out of version control.
Bootstrapping systems with add_system also needs UYUNI_SSH_PRIV_KEY, formatted as one line with literal \n sequences between the original lines, and UYUNI_SSH_PRIV_KEY_PASS for its passphrase. These settings are not needed just to connect.
For a client that accepts an mcpServers configuration, add this entry to its MCP configuration. Replace /path/to/uyuni-config.env with your environment file’s absolute path and VERSION with your chosen release tag or latest. Follow your client’s documentation for the configuration location and how to load the change.
{
"mcpServers": {
"mcp-server-uyuni": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"--env-file", "/path/to/uyuni-config.env",
"ghcr.io/uyuni-project/mcp-server-uyuni:VERSION"
]
}
}
}Check the result
Check that the container exposes tools
The Inspector check requires Node.js 22.19.0 or newer. Replace ./mcp.json with the path to a JSON file containing the configured mcpServers block above, including your actual environment-file path and image tag. The Inspector reads this file without changing it, starts the server, requests its tools and exits.
A tool count and exit code 0 indicate that the Inspector could start the server and list its tools. This does not confirm that your AI tool has loaded it or that a Uyuni operation succeeds.
npx @modelcontextprotocol/inspector --cli --config ./mcp.json --server mcp-server-uyuni --method tools/listCheck the connection in your AI tool
Use your MCP client’s documented connection status and logs to confirm that it has loaded mcp-server-uyuni. Check that the environment file it uses points to the intended Uyuni instance and account.
Uyuni server configuration and container setupMCP Inspector requirementsInspector CLI commands and exit codesInspector configuration filesChecking connections in your MCP client