GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
Safe-by-default MCP for OpenShift / Kubernetes: projects, pods, logs, deployments, routes.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
OPENSHIFT_SERVER, OPENSHIFT_TOKEN, OPENSHIFT_USERNAME, OPENSHIFT_PASSWORD, OPENSHIFT_CA_CERT, OPENSHIFT_MODEValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"openshift": {
"command": "npx",
"args": [
"-y",
"@dockndevai/mcp-openshift"
],
"env": {
"OPENSHIFT_SERVER": "your-value",
"OPENSHIFT_TOKEN": "your-value",
"OPENSHIFT_USERNAME": "your-value",
"OPENSHIFT_PASSWORD": "your-value",
"OPENSHIFT_CA_CERT": "your-value",
"OPENSHIFT_MODE": "your-value"
}
}
}
}Run this in your terminal
claude mcp add openshift --env OPENSHIFT_SERVER=your-value --env OPENSHIFT_TOKEN=your-value --env OPENSHIFT_USERNAME=your-value --env OPENSHIFT_PASSWORD=your-value --env OPENSHIFT_CA_CERT=your-value --env OPENSHIFT_MODE=your-value -- npx -y @dockndevai/mcp-openshiftFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"openshift": {
"command": "npx",
"args": [
"-y",
"@dockndevai/mcp-openshift"
],
"env": {
"OPENSHIFT_SERVER": "your-value",
"OPENSHIFT_TOKEN": "your-value",
"OPENSHIFT_USERNAME": "your-value",
"OPENSHIFT_PASSWORD": "your-value",
"OPENSHIFT_CA_CERT": "your-value",
"OPENSHIFT_MODE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"openshift": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@dockndevai/mcp-openshift"
],
"env": {
"OPENSHIFT_SERVER": "your-value",
"OPENSHIFT_TOKEN": "your-value",
"OPENSHIFT_USERNAME": "your-value",
"OPENSHIFT_PASSWORD": "your-value",
"OPENSHIFT_CA_CERT": "your-value",
"OPENSHIFT_MODE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
OPENSHIFT_USERNAME envOPENSHIFT_CA_CERT envOPENSHIFT_MODE envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account dockndevai, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: OPENSHIFT_SERVER, OPENSHIFT_TOKEN, OPENSHIFT_PASSWORD
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 40 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A safe-by-default Model Context Protocol server for OpenShift / Kubernetes. It lets an agent explore and operate a cluster — projects, pods and logs, deployments and deploymentconfigs, routes, services, builds, imagestreams, and any resource by kind — and, in higher modes, scale workloads, restart deployments, apply manifests, and delete.
Connect with a token from the web console you already use, or your username/password against the cluster's local identity provider.
Part of the dockndevai MCP server suite — one governance model across all of them.
Starts read-only (see Safe by default); higher-capability tools are only registered when you raise the mode.
| Tool | For | Needs mode |
|---|---|---|
whoami | confirm the authenticated identity | read-only |
list_projects | projects/namespaces you can see | read-only |
list_resources | list any kind (± namespace, label selector) | read-only |
get_resource | one resource with full spec/status | read-only |
pod_logs | a pod's container logs | read-only |
list_events | recent events in a namespace | read-only |
scale | set replicas on a Deployment/DeploymentConfig | read-write |
rollout_restart | restart a Deployment | read-write |
apply_resource | create/update from a manifest (SSA) | read-write + OPENSHIFT_ALLOW_APPLY |
delete_resource | delete a resource | admin + OPENSHIFT_ALLOW_DELETE |
npx -y @dockndevai/mcp-openshift
You need your cluster's API URL and a credential. The quickest, since you use the browser console:
In the OpenShift web console, click your username (top-right) → Copy login command → Display Token. Copy the value after
--token=(sha256~…) and the URL after--server=.
Then set OPENSHIFT_SERVER + OPENSHIFT_TOKEN. (Console tokens are short-lived; grab a fresh one when it expires, or use username/password below, which re-logs in automatically.)
{
"mcpServers": { "openshift": { "command": "npx", "args": ["-y", "@dockndevai/mcp-openshift"], "env": { "OPENSHIFT_SERVER": "https://api.cluster.example.com:6443", "OPENSHIFT_TOKEN": "sha256~...", "OPENSHIFT_MODE": "read-only" } } } }
See docs/CLIENTS.md for Claude Code / Cursor / Codex / VS Code / Windsurf, and .env.example for every variable.
Auth mode is chosen automatically (override with OPENSHIFT_AUTH):
OPENSHIFT_TOKEN (bearer). From the console (above) or oc whoami -t.OPENSHIFT_USERNAME + OPENSHIFT_PASSWORD against the cluster's built-in OAuth server (HTPasswd / LDAP / any challenge-capable local IdP). The server runs the same request-token flow oc login -u … -p … uses, caches the token at ~/.mcp-openshift/token.json (0600), and re-logs in on expiry. The password is sent only to your cluster's OAuth endpoint and is never logged or written to disk.TLS: clusters usually use a private CA — set OPENSHIFT_CA_CERT to the CA bundle, or (dev only) OPENSHIFT_INSECURE_TLS=true to skip verification.
Enforced by src/security.ts — defence in depth on top of your account's cluster RBAC:
read-only (default) → read-write → admin. Tools above the mode aren't registered.kube-*, openshift, openshift-*, default) are readable but never mutable.dryRun=All: validated and admission-checked, but nothing persists.Optional AI risk guard. Set OPENSHIFT_GUARD_MODE=monitor|enforce to have apply_resource / delete_resource consult a local laya-guard daemon (pipx install laya-guard && laya-guard) that classifies the operation allow/confirm/block before it runs. Runs *after* the apply/delete gates; only tightens, never grants; fails closed.
There is a bundled skill, openshift-safe-operations, that teaches an agent how to authenticate (including from the browser console), the safety rules, and the standard triage/operate workflows. See also SECURITY.md.
npm install
npm run build
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' | OPENSHIFT_SERVER=https://x:6443 OPENSHIFT_TOKEN=x node dist/index.js npm test
MIT