In-depth architectural comparison of the Kops and Hub MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Kops
Cloud Platforms · Local stdio
Quality: 39/100 (Fair) | Auth: No auth required
Hub MCP
Cloud Platforms · Local stdio
Quality: 80/100 (Excellent) | Auth: API Key required
Verdict Summary: Choose Kops if you need specialized Cloud Platforms tools running via a local process. Choose Hub MCP if your workspace requires Cloud Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Kops when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Hardcoded read-only verbs: get, describe, logs, events, Structured JSON output optimized for AI reasoning, Cluster triage tool for quick health checks.
Read-only kubectl for Claude Code: returns structured JSON, hardcoded safe verbs (no mutation path even with malicious input), Secret/ConfigMap values never returned, plus one-shot cluster triage & inventory.
Official MCP server to interact with Docker Hub, providing access to repositories, hub search and Docker Hardened Images
Kops is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Hub MCP belongs to Cloud Platforms using local stdio subprocess. Select Kops when you need capabilities focused on cloud platforms and Hub MCP when you require tools for cloud platforms.