MCP Server Kubernetes for Windsurf: Setup & Config

What you can do with MCP Server Kubernetes in Windsurf

An existing-context Kubernetes bridge spanning diagnostics, resource changes, Helm, and tracing.

• Apply manifests and manage deployment rollouts from an assistant.
• Trace assistant-driven cluster operations through an OTLP backend.

Before you start: MCP Server Kubernetes in Windsurf

• Node.js and npx
• kubectl on PATH
• A valid kubeconfig with cluster access
• Helm v3 on PATH for Helm operations

Loads the standard kubeconfig and current kubectl context by default. Set ALLOW_ONLY_NON_DESTRUCTIVE_TOOLS to true to disable designated destructive operations; this still permits creation and updates. Telemetry is optional and off by default.

MCP Server Kubernetes Windsurf configuration

1. Choose Windsurf configuration scope

   For MCP Server Kubernetes, open macOS/Linux: ~/.codeium/windsurf/mcp_config.json Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json. Merge into mcpServers; remote endpoints use serverUrl.

2. Add MCP Server Kubernetes to Windsurf

   Use the mcp-server-kubernetes entry below in mcpServers. Keep MCP Server Kubernetes's documented stdio connection fields and your other Windsurf entries.

3. Check MCP Server Kubernetes in Windsurf

   MCP Server Kubernetes: Refresh MCP in Windsurf settings and inspect Cascade’s tools.

{
  "mcpServers": {
    "mcp-server-kubernetes": {
      "command": "npx",
      "args": [
        "mcp-server-kubernetes"
      ],
      "env": {}
    }
  }
}

MCP Server Kubernetes tools available to Windsurf

MCP Server Kubernetes's stored tool list documents 26 tools; compare it with Windsurf's connected tool list, because the stored list is not a live check.

cleanup

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for cleanup.

kubectl_get

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for kubectl_get.

kubectl_describe

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for kubectl_describe.

kubectl_apply

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for kubectl_apply.

kubectl_delete

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for kubectl_delete.

kubectl_create

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for kubectl_create.

kubectl_logs

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for kubectl_logs.

kubectl_scale

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for kubectl_scale.

Adjust deployment replica counts.

kubectl_patch

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for kubectl_patch.

Change resource fields through supported patch formats.

kubectl_rollout

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for kubectl_rollout.

Control rollouts for supported workload resources.

kubectl_context

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for kubectl_context.

List, inspect, or change the current Kubernetes context.

kubectl_reconnect

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for kubectl_reconnect.

Rebuild API clients to refresh network connections and DNS after cluster changes.

explain_resource

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for explain_resource.

Read documentation for a Kubernetes resource or field.

install_helm_chart

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for install_helm_chart.

upgrade_helm_chart

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for upgrade_helm_chart.

uninstall_helm_chart

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for uninstall_helm_chart.

node_management

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for node_management.

port_forward

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for port_forward.

stop_port_forward

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for stop_port_forward.

exec_in_pod

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for exec_in_pod.

Run an executable and argument array in a container without shell interpretation.

list_api_resources

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for list_api_resources.

Enumerate resource APIs supported by the cluster.

kubectl_generic

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for kubectl_generic.

Run a kubectl command using supplied arguments and flags.

ping

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for ping.

Check whether the connection remains responsive.

cleanup_pods

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for cleanup_pods.

Clean up pods in documented problematic or completed states.

helm_template_apply

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for helm_template_apply.

Use template-based Helm installation to work around authentication issues.

helm_template_uninstall

After refreshing MCP Server Kubernetes in Windsurf settings, check Cascade's tool list for helm_template_uninstall.

Use template-based Helm removal to work around authentication issues.

MCP Server Kubernetes: full stored tool descriptions

Troubleshooting MCP Server Kubernetes in Windsurf

• Check npx mcp-server-kubernetes (Node.js/npm) on the machine running Windsurf's MCP integration for MCP Server Kubernetes; refresh MCP and inspect Cascade's tools.
• MCP Server Kubernetes uses stdio here: Windsurf must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: Requires working cluster credentials and local kubectl.
• Known limitation: Non-destructive mode still allows resource changes.
• Known limitation: Secret masking does not cover log output.
• General Windsurf troubleshooting lives in the /clients/windsurf guide.

Frequently asked questions