Data as of
Kubernetes MCP Server for Windsurf: Setup & Config
Windsurf: Give MCP assistants direct Kubernetes and OpenShift API access.
What you can do with Kubernetes in Windsurf
Choose it for direct Kubernetes API access with native distribution and configurable operational limits.
- Investigate pod logs, events, and resource consumption with an assistant.
- Inspect Kubernetes and OpenShift resources in read-only mode.
- Work across kubeconfig-defined clusters from one MCP connection.
Before you start: Kubernetes in Windsurf
- Access to a Kubernetes cluster
- Usable kubeconfig or in-cluster credentials
- Node.js and npm for this npx option
- An MCP-compatible client
This is the documented Claude Desktop and Cursor launch, without the help-only flag from the input hint. Native binaries do not require Node.js or Python. Review read-only mode, toolsets, and resource restrictions before granting production access.
Kubernetes Windsurf configuration
Choose Windsurf configuration scope
For Kubernetes MCP Server, open macOS/Linux: ~/.codeium/windsurf/mcp_config.json Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json. Merge into mcpServers; remote endpoints use serverUrl.
Add Kubernetes MCP Server to Windsurf
Use the kubernetes-mcp-server entry below in mcpServers. Keep Kubernetes MCP Server's documented stdio connection fields and your other Windsurf entries.
Check Kubernetes MCP Server in Windsurf
Kubernetes MCP Server: Refresh MCP in Windsurf settings and inspect Cascade’s tools.
Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
{
"mcpServers": {
"kubernetes-mcp-server": {
"command": "npx",
"args": [
"-y",
"kubernetes-mcp-server@latest"
],
"env": {}
}
}
}Troubleshooting Kubernetes in Windsurf
- Check npx kubernetes-mcp-server@latest (Node.js/npm) on the machine running Windsurf's MCP integration for Kubernetes MCP Server; refresh MCP and inspect Cascade's tools.
- Kubernetes MCP Server uses stdio here: Windsurf must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
- Known limitation: Requires access credentials for a Kubernetes cluster.
- Known limitation: Write-capable operations need deliberate restrictions for production use.
- Known limitation: Exact tool identifiers are not stated in the supplied README excerpt.
- General Windsurf troubleshooting lives in the /clients/windsurf guide.
Kubernetes MCP Server — details. Windsurf guide