MCP K8s Ro vs MCP K8s
A side-by-side look at the MCP K8s Ro and MCP K8s MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP K8s Ro for cloud platforms work; choose MCP K8s for cloud platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP K8s Ro when
- You need dedicated capabilities in the Cloud Platforms domain.
- You have the keys it needs:
KUBECONFIG. - You want tools like
k8s_list_resources, k8s_describe_resource, k8s_list_resource_types.
Choose MCP K8s when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: other.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 45/100 · Fair | 59/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | KUBECONFIG | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 151 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 7 | Not listed |
| Full listing | View MCP K8s Ro | View MCP K8s |
Tools & capabilities
MCP K8s Ro tools 7
k8s_list_resourcesList any resource type by name — pods, deployments, CRDs, etc. Accepts optional namespace filter. Returns name, status, readiness, restarts, node, IP, and more depending on resource kind.k8s_describe_resourceReturn the full YAML of a single resource. Secret data is masked.k8s_list_resource_typesList all available resource types via the discovery API. Accepts optional API group filter.k8s_get_logsFetch pod logs. Supports container selector, tail lines, and `--previous` for crashed containers.k8s_get_eventsList Kubernetes events for a namespace or the whole cluster, sorted by most recent.k8s_top_podsCPU and memory usage per pod, with per-container breakdown. Requires metrics-server.k8s_top_nodesCPU and memory usage per node, with percentage of allocatable capacity. Requires metrics-server.
MCP K8s tools
No tool names declared yet. Check the project README from the listing page.
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 K8s Ro
No confirmed install command for MCP K8s Ro yet — follow the setup steps linked from its listing page rather than a guessed package name.
MCP K8s
{
"mcpServers": {
"silenceper-mcp-k8s": {
"url": "http://localhost:8080/sse"
}
}
}
Frequently asked questions
MCP K8s Ro is categorized under Cloud Platforms and uses an install path we have not confirmed yet. MCP K8s belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick MCP K8s Ro for cloud platforms work and MCP K8s 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 K8s Ro has no confirmed install command yet — follow its own setup instructions.
MCP K8s Ro has no declared pricing — check the project's own site. MCP K8s is listed as free. Auth: other. 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 mcp-k8s-ro and silenceper-mcp-k8s as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP K8s Ro has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. MCP K8s has 59/100 (Good) with 3 views, 0 installs and 151 GitHub stars.