原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

OpenShift MCP Server

作者:sanjaypsachdev版本 1.2.0i★ –i在你的电脑上运行
注册名称io.github.sanjaypsachdev/mcp-server-openshift

安装

概览

作者提供的说明(英文原文)

OpenShift/Kubernetes cluster management via the oc CLI for MCP clients

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 开发者工具

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 需要你自己填写: OPENSHIFT_CONTEXT, OPENSHIFT_NAMESPACE

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "openshift": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-openshift"
      ],
      "env": {
        "OPENSHIFT_CONTEXT": "your-value",
        "OPENSHIFT_NAMESPACE": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add openshift --env OPENSHIFT_CONTEXT=your-value --env OPENSHIFT_NAMESPACE=your-value -- npx -y mcp-server-openshift

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "openshift": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-openshift"
      ],
      "env": {
        "OPENSHIFT_CONTEXT": "your-value",
        "OPENSHIFT_NAMESPACE": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "openshift": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-openshift"
      ],
      "env": {
        "OPENSHIFT_CONTEXT": "your-value",
        "OPENSHIFT_NAMESPACE": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • OPENSHIFT_CONTEXT env
    Default OpenShift/Kubernetes context
  • OPENSHIFT_NAMESPACE env
    Default namespace/project

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 sanjaypsachdev 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“开发者工具”中的其他服务器比较i

  • 星标数多于此分类中其他 1385 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1385 个服务器的 28% 更新
  • 基础检查结果等于或优于此分类中其他 1385 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

OpenShift MCP Server 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(1.2.0)于4个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js, Docker。

有什么可以替代它?

同一分类中有:GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

作者:github

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

电脑或云端★ 34,245MIT3天前更新
安装

Desktop Commander

作者:wonderwhy-er

MCP server for terminal commands, file operations, and process management

在你的电脑上运行★ 10,225MIT15天前更新
安装

Cloudflare MCP

作者:cloudflare

Cloudflare MCP servers

在云端运行★ 4,446Apache-2.014个月前更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

OpenShift MCP Server

A Model Context Protocol (MCP) server that provides AI assistants with comprehensive OpenShift/Kubernetes cluster management capabilities through the oc command-line interface.

Demo Video

Watch the oc-new-app tool deploy a complete Spring Boot application from GitHub to OpenShift:

https://github.com/user-attachments/assets/f4bace3f-755b-462f-8a8a-680e4dc02129

Features

  • Cluster Information: Access comprehensive cluster status, nodes and configuration via MCP resources
  • Resource Description: Describe any resource with multiple output formats including human-readable summaries
  • Complete Resource Management: Create, read, update, delete, and patch all OpenShift/Kubernetes resources
  • Application Deployment: Deploy applications from Git repositories with S2I builds and automatic route creation
  • Operator Management: Install operators via OLM, Helm, or direct manifests
  • Cluster Operations: Scaling, monitoring, troubleshooting and management
  • Build Operations: Start and monitor OpenShift builds
  • Scaling Operations: Scale deployments, replicasets and statefulsets
  • Logging: Retrieve logs from pods and builds
  • Multi-Transport Support: STDIO and HTTP/SSE transports for different integration scenarios
  • Comprehensive Testing: 99 unit tests ensuring production reliability
  • Rich Error Handling: Detailed troubleshooting guidance and actionable error messages
  • Troubleshooting Prompts: Interactive troubleshooting guides for common OpenShift scenarios
  • Log Sampling: Sample and analyze pod logs with intelligent pattern detection and context

Prerequisites

  • Node.js 20+
  • OpenShift CLI (oc) installed and configured
  • Access to an OpenShift cluster

Installation

git clone https://github.com/sanjaypsachdev/mcp-server-openshift.git

cd mcp-server-openshift npm install npm run build

Configuration

Add to your MCP client configuration:

Claude Desktop / Cursor
{

"mcpServers": { "openshift": { "command": "node", "args": ["/path/to/mcp-server-openshift/dist/index.js"], "env": { "OPENSHIFT_CONTEXT": "your-context-name", "OPENSHIFT_NAMESPACE": "your-default-namespace" } } } }

HTTP/SSE Transport (Remote Access)
# Start HTTP server

npm run start:http

Connect via MCP remote

npx -y mcp-remote http://localhost:3000/sse --transport sse-only

Tools

Authentication & Access
  • `oc_login` - Securely log into OpenShift clusters using token or username/password authentication
API Discovery & Documentation
  • `oc_api_resources` - List all available API resources in the cluster with categorization
  • `oc_explain` - Explain resource schemas, fields, and API documentation
Core Resource Management
  • `oc_get` - Get OpenShift resources (pods, deployments, services, routes, etc.)
  • `oc_create` - Create OpenShift resources from manifests or templates
  • `oc_apply` - Apply YAML manifests with validation and conflict resolution
  • `oc_delete` - Delete resources with safety checks and confirmation options
  • `oc_patch` - Patch resources using strategic merge, JSON merge, or JSON patch operations
  • `oc_describe` - Describe resources with multiple output formats
Application Lifecycle
  • `oc_new_app` - Deploy applications from Git repositories with S2I builds
  • `oc_scale` - Scale deployments, deploymentconfigs, replicasets, and statefulsets
  • `oc_logs` - Get logs from pods, deployments, builds with filtering options
Advanced Operations
  • `oc_install_operator` - Install operators via OLM, Helm, or direct manifests

Resources

MCP Resources provide read-only access to cluster information:

  • `openshift://cluster-info` - Comprehensive cluster status, nodes, namespaces, and events
  • `openshift://project-list` - Detailed project information with quotas and usage statistics
  • `openshift://app-templates` - Application deployment templates and patterns

Prompts

Interactive troubleshooting and operational guidance:

  • `troubleshoot-openshift-prompt` - Comprehensive OpenShift troubleshooting guide for all resource types and cluster issues
  • `monitoring-prompts` - Monitoring and observability guidance for different scenarios

Sampling

Intelligent log analysis and pattern detection:

  • Pod Logs Sampling - Automatic log sampling with error pattern detection and context analysis

Usage Examples

Login to Cluster
# Login with token (recommended)

oc_login with server: "https://api.cluster.example.com:6443", authMethod: "token", token: "sha256~your-token-here"

Login with username/password

oc_login with server: "https://api.cluster.example.com:6443", authMethod: "password", username: "developer", password: "your-password"

Discover API Resources
# List all available API resources

oc_api_resources

List resources for specific API group

oc_api_resources with apiGroup: "apps"

List only namespaced resources

oc_api_resources with namespaced: true

Explain a resource schema

oc_explain with resource: "deployment"

Explain specific field

oc_explain with resource: "pod", field: "spec.containers"

Deploy Application
# Deploy Node.js app from GitHub

oc_new_app with gitRepo: "https://github.com/sclorg/nodejs-ex.git"

Scale Application
# Scale deployment to 3 replicas

oc_scale with name: "my-app", replicas: 3

Patch Resource
# Update deployment labels

oc_patch with resourceType: "deployment", name: "my-app", patch: '{"metadata":{"labels":{"environment":"production"}}}'

Troubleshoot Issues
# Get pod troubleshooting guidance

Use prompt: troubleshoot-openshift-prompt Arguments: issueType: "pod", resourceName: "my-app-12345", namespace: "my-project"

Get deployment troubleshooting guidance

Use prompt: troubleshoot-openshift-prompt Arguments: issueType: "deployment", resourceName: "my-app", namespace: "my-project"

Get general cluster troubleshooting guidance

Use prompt: troubleshoot-openshift-prompt Arguments: issueType: "cluster", symptoms: "nodes not ready"

Development

# Setup

npm install

Build

npm run build

Test

npm test

Start (STDIO)

npm start

Start (HTTP)

npm run start:http

Development mode

npm run dev

Transport Modes

STDIO (Default)
  • Direct MCP client integration
  • Lower latency
  • Recommended for local development
HTTP/SSE
  • Remote access capability
  • Web integration friendly
  • Container deployment ready

Architecture

src/

├── index.ts # Main server entry point ├── tools/ # Tool implementations ├── resources/ # MCP resources ├── prompts/ # Interactive prompts ├── sampling/ # Log sampling and analysis ├── models/ # Zod validation schemas └── utils/ # OpenShift CLI wrapper

Security

Authentication Security
  • Token Authentication: Preferred method for automation and production use
  • Password Authentication: Available but token authentication is recommended
  • HTTPS Enforcement: All cluster connections must use HTTPS
  • URL Validation: Server URLs validated to prevent SSRF attacks
  • Private IP Blocking: Prevents connections to internal/metadata services
Operational Security
  • RBAC Compliance: Respects OpenShift RBAC permissions
  • No Credential Storage: Credentials are not stored or transmitted by the server
  • User Permissions: Executes with the same permissions as the authenticated user
  • Input Validation: Comprehensive validation of all inputs and parameters
  • Secure Defaults: Conservative security settings by default
Best Practices
  • Use Service Account Tokens: For automation and CI/CD pipelines
  • Regular Token Rotation: Rotate authentication tokens regularly
  • TLS Certificate Validation: Always validate TLS certificates in production
  • Least Privilege: Use accounts with minimal required permissions
  • Session Management: Use oc logout to clear credentials when done

License

MIT License - see LICENSE file for details.

问 PopNx