OpenShift MCP Server

What OpenShift MCP Server MCP server does

OpenShift MCP Server MCP server connects MCP clients to an OpenShift or Kubernetes cluster through the oc command-line interface. It gives an AI assistant tools for logging in, discovering API resources, reading schemas, inspecting objects, and managing resource lifecycles.

The available operations cover common administrative and application workflows. An assistant can retrieve, create, apply, delete, patch, and describe resources such as pods, deployments, services, and routes. It can also deploy an application from a Git repository with an S2I build, change replica counts, retrieve logs, and install operators through OLM, Helm, or manifests.

Read-only MCP resources provide cluster information, project details, and application templates. Prompts supply troubleshooting and monitoring guidance, while log sampling can identify patterns and add context to pod log analysis.

How it works

Each MCP tool maps to an OpenShift CLI operation and returns the resulting cluster information or command outcome to the client. Authentication supports either an access token or username and password. API discovery tools can list resources by API group or namespace scope, and the explanation tool can document a resource or a nested field.

The server offers STDIO for direct local client integration and HTTP/SSE for remote or web-oriented connections. The HTTP mode starts a local HTTP server, which can be reached through an MCP remote connection using the documented SSE endpoint.

Setup and configuration

OpenShift MCP Server MCP server requires Node.js 18 or newer, an installed and configured oc executable, and access to an OpenShift cluster. From a source checkout, install dependencies and build the TypeScript project before starting it.

For a local MCP client, configure the server with Node as the command and point its arguments to dist/index.js. The documented configuration accepts OPENSHIFT_CONTEXT for the OpenShift context and OPENSHIFT_NAMESPACE for the default namespace.

Use npm start for STDIO operation, or npm run start:http for HTTP/SSE. The repository also documents npm test, npm run dev, and npm run build for development workflows.

Tools and capabilities

The server exposes these tool groups:

• Authentication: oc_login.
• Discovery and schemas: oc_api_resources, oc_explain.
• Resource operations: oc_get, oc_create, oc_apply, oc_delete, oc_patch, and oc_describe.
• Application operations: oc_new_app, oc_scale, and oc_logs.
• Operator installation: oc_install_operator.

oc_new_app supports deployment from Git repositories with S2I builds. oc_scale handles deployments, deployment configurations, ReplicaSets, and StatefulSets. oc_logs retrieves logs from pods, deployments, and builds with filtering options.

Limitations and notes

OpenShift MCP Server MCP server depends on the local oc CLI and the permissions of the connected cluster identity. It does not replace cluster access controls or provide access without a configured OpenShift connection.

The README identifies OpenShift 4.x and Kubernetes 1.25+ as supported platform versions. Destructive and mutating operations, including deletion, patching, applying manifests, scaling, and operator installation, should be used with the appropriate namespace and cluster permissions. HTTP/SSE is available for remote access, but the documented setup starts the service locally and exposes its SSE endpoint.