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