Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

RHEL 10.3 ships a supported MCP server

Written November 13, 2026

Red Hat's MCP server for RHEL is now generally available in 10.3 and 9.9 — installed by dnf, governed by default, ready for agents.

What changed

The Model Context Protocol (MCP) server for Red Hat Enterprise Linux has moved from Developer Preview to general availability. Red Hat's announcement calls the move a milestone and describes the result as a production-ready foundation that connects AI assistants directly to RHEL system data. The server ships in both RHEL 10.3 and RHEL 9.9, the two releases Red Hat shipped on November 11.

It arrives the way RHEL software usually arrives. Red Hat packages the MCP server as an RPM in the RHEL Extensions repository, so you install it with standard dnf commands, alongside goose, the open source AI command-line agent Red Hat points to as a pairing. There is no separate download portal and no agent-specific installer.

What an assistant can do with it

MCP is an open standard that lets local AI tools query system diagnostics and configuration data. Put plainly, the assistant stops guessing from pasted fragments. Red Hat's developer write-up says the MCP server analyzes system journals and application logs, extracts error traces, and summarizes failures in plain English.

The more useful half is historical. The server connects directly to on-disk archives from Performance Co-Pilot (PCP), so an assistant can parse past performance metrics instead of only looking at the machine's current state. Red Hat's example is a memory spike that happened overnight: the data an administrator would otherwise dig out of dashboard charts by hand is already on disk, and the assistant can work through it. That suits the intermittent fault, the one that never performs on demand while someone watches.

How access is governed

The server runs locally, on the machine, under standard user permissions. Red Hat's developer article draws the consequence directly: because it runs that way, your source code and credentials stay protected on your machine. An assistant paired through the server works with the rights of the account it runs under, not with a new privileged path into the host. You can pair it with goose or with your usual IDE.

That framing matters for how a cautious team rolls it out. Start on one host, under an ordinary account, with log and journal questions. The permission model is the one your administrators already manage, which makes the first deployment a package decision rather than a new access review.

What did not graduate

One neighbouring piece is still a preview. The RHEL command-line assistant can now run in a self-managed way, using customer-hosted inference, so guidance and operational context stay inside air-gapped or disconnected perimeters. Red Hat labels that self-managed mode Developer Preview, and its hosted path remains available for connected estates. A team that needs the assistant itself inside a disconnected perimeter is still building on preview footing, even though the MCP server underneath is now supported.

For context only: RHEL 10.3 also moves sealed images for image mode to general availability. That is a separate integrity feature and has nothing to do with agent access.

What to do

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Patch your MCP reference servers now