Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y @dockndevai/[email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
OPENSHIFT_SERVER=<value> OPENSHIFT_TOKEN=<secret> OPENSHIFT_USERNAME=<value> OPENSHIFT_PASSWORD=<secret> OPENSHIFT_CA_CERT=<value> OPENSHIFT_MODE=<value> claude mcp add io.github.dockndevai-mcp-openshift -- npx -y @dockndevai/mcp-openshift@0.2.0รันในเทอร์มินัล
{ "mcpServers": { "io.github.dockndevai-mcp-openshift": { "command": "npx", "args": [ "-y", "@dockndevai/[email protected]" ], "env": { "OPENSHIFT_SERVER": "<value>", "OPENSHIFT_TOKEN": "<secret>", "OPENSHIFT_USERNAME": "<value>", "OPENSHIFT_PASSWORD": "<secret>", "OPENSHIFT_CA_CERT": "<value>", "OPENSHIFT_MODE": "<value>" } } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
A safe-by-default Model Context Protocol server for . 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.
Safe-by-default MCP for OpenShift / Kubernetes: projects, pods, logs, deployments, routes.
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.
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:
OPENSHIFT_MODE — read-only (default) → read-write → admin. Tools above the mode aren't registered.OPENSHIFT_NAMESPACE_ALLOWLIST / OPENSHIFT_PROTECTED_NAMESPACES — confine writes to named namespaces; system namespaces (kube-*, openshift, openshift-*, default) are readable but never mutable.OPENSHIFT_ALLOW_APPLY — creating/updating resources needs this flag on top of read-write, plus a human confirmation.OPENSHIFT_ALLOW_DELETE — deletes need admin mode plus this flag, plus confirmation.OPENSHIFT_DRY_RUN — sends writes with Kubernetes dryRun=All: validated and admission-checked, but nothing persists.OPENSHIFT_AUDIT_LOG — a JSON audit line per guarded op on stderr; Secret values are redacted from all output.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
# list the tools without a live cluster:
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
Safe-by-default MCP for OpenShift / Kubernetes: projects, pods, logs, deployments, routes.
{ "mcpServers": { "io.github.dockndevai-mcp-openshift": { "command": "npx", "args": [ "-y", "@dockndevai/[email protected]" ], "env": { "OPENSHIFT_SERVER": "<value>", "OPENSHIFT_TOKEN": "<secret>", "OPENSHIFT_USERNAME": "<value>", "OPENSHIFT_PASSWORD": "<secret>", "OPENSHIFT_CA_CERT": "<value>", "OPENSHIFT_MODE": "<value>" } } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ผู้เผยแพร่ระบุตัวแปรสภาพแวดล้อมเหล่านี้: OPENSHIFT_SERVER, OPENSHIFT_TOKEN, OPENSHIFT_USERNAME, OPENSHIFT_PASSWORD, OPENSHIFT_CA_CERT, OPENSHIFT_MODE
MCP Openshift ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-09 Safe-by-default MCP for OpenShift / Kubernetes: projects, pods, logs, deployments, routes.