A side-by-side look at the Kubectl MCP Server and Relayer MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kubectl MCP Server for cloud platforms work as a local process; choose Relayer MCP 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 Kubectl MCP Server when
You need dedicated capabilities in the Cloud Platforms domain.
No tool names declared yet. Check the project README from the listing page.
Relayer MCP 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.
Kubectl MCP Server is categorized under Cloud Platforms and uses a local stdio subprocess. Relayer MCP belongs to Cloud Platforms and uses a local stdio subprocess. Pick Kubectl MCP Server for cloud platforms work and Relayer MCP 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.
Kubectl MCP Server is listed as free. Auth: other. Relayer MCP has no declared pricing — check the project's own site. Auth: no auth required. 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 rohitg00-kubectl-mcp-server and xns-cloud-relayer-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kubectl MCP Server has a quality signal of 53/100 (Good) with 3 views, 0 installs and 962 GitHub stars. Relayer MCP has 55/100 (Good) with 0 views, 0 installs and 3 GitHub stars.