MCP Server Kubernetes vs MCP Oci
A side-by-side look at the MCP Server Kubernetes and MCP Oci MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server Kubernetes for cloud platforms work as a local process; choose MCP Oci for cloud platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Server Kubernetes when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You want tools like
cleanup, kubectl_get, kubectl_describe.
Choose MCP Oci when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_compartments, list_regions, search_resources.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 65/100 · Great | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,607 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 23 | 8 |
| Full listing | View MCP Server Kubernetes | View MCP Oci |
Tools & capabilities
MCP Server Kubernetes tools 23
cleanupCleanup all managed resourceskubectl_getGet or list Kubernetes resources by resource type, name, and optionally namespacekubectl_describeDescribe Kubernetes resources by resource type, name, and optionally namespacekubectl_applyApply a Kubernetes YAML manifest from a string or filekubectl_deleteDelete Kubernetes resources by resource type, name, labels, or from a manifest filekubectl_createCreate Kubernetes resources using various methods (from file or using subcommands)kubectl_logsGet logs from Kubernetes resources like pods, deployments, or jobskubectl_scaleScale a Kubernetes deploymentkubectl_patchUpdate field(s) of a resource using strategic merge patch, JSON merge patch, or JSON patchkubectl_rolloutManage the rollout of a resource (e.g., deployment, daemonset, statefulset)kubectl_contextManage Kubernetes contexts - list, get, or set the current contextkubectl_reconnectReconnect to the Kubernetes API server by recreating all API clients. Use this after cluster upgrades (e.g., EKS control plane upgrades that rotate ENIs/IPs) to force fresh DNS resolution and new TCP connections.- +11 more on the listing page
MCP Oci tools 8
list_compartmentsList compartments in the tenancy (recursively). Compartments outside the allowlist are filtered out.list_regionsList the regions this tenancy is subscribed to.search_resourcesSearch tenancy resources using OCI Resource Search. Provide either a structured query (e.g. "query instance resources where displayName =~ 'prod'") or free text.list_compartment_resourcesEnumerate every resource in a compartment (via Resource Search).get_resourceFetch detailed attributes for a resource by type and OCID. Known types (Vcn, Subnet, Instance) return full attributes; others return the identifier. Secrets are redacted.generate_terraformGenerate a Terraform (HCL) resource block for a single OCI resource by type and OCID. Fetches the resource's attributes and maps them to the matching oci_* resource.generate_compartment_terraformDiscover every resource in a compartment and emit a Terraform module (provider variables + one block per resource) to reproduce it. Unrecognised types become annotated skeletons.build_dependency_graphDiscover a compartment's resources and return a node/edge dependency graph plus a suggested provisioning order (dependencies first).
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Server Kubernetes
{
"mcpServers": {
"flux159-mcp-server-kubernetes": {
"command": "npx",
"args": [
"-y",
"mcp-server-kubernetes"
]
}
}
}
MCP Oci
{
"mcpServers": {
"mcp-oci": {
"command": "npx",
"args": [
"-y",
"@dockndevai/mcp-oci"
]
}
}
}
Frequently asked questions
MCP Server Kubernetes is categorized under Cloud Platforms and uses a local stdio subprocess. MCP Oci belongs to Cloud Platforms and uses a local stdio subprocess. Pick MCP Server Kubernetes for cloud platforms work and MCP Oci for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Server Kubernetes has no declared pricing — check the project's own site. MCP Oci has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add flux159-mcp-server-kubernetes and mcp-oci as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server Kubernetes has a quality signal of 65/100 (Great) with 0 views, 0 installs and 1,607 GitHub stars. MCP Oci has 61/100 (Good) with 3 views, 0 installs and 1 GitHub stars.