Ocm MCP Server

You can run the ocm-mcp server in a container using Podman or Docker. Make sure you have a valid OCM token, which you can obtain by logging into https://console.redhat.com/openshift/token:. Exposed over MCP by the ocm mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Configuration

You will need 4 environment variables: ACCESS_TOKEN_URL, OCM_CLIENT_ID, OCM_OFFLINE_TOKEN, MCP_TRANSPORT. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the ocm mcp mcp server does with a few real requests.

When to reach for it

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by redhat-ai-tools; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.