kubectl-mcp-server for Cursor: Setup & Config

What you can do with kubectl-mcp-server in Cursor

A broad Kubernetes operations surface for assistant-led diagnostics, Helm work, and resource analysis.

• Investigate a crashed pod using logs and events.
• Review RBAC and secret-security findings.
• Identify idle workloads and oversized resource requests.

Before you start: kubectl-mcp-server in Cursor

• Node.js 14+ for the npx method
• kubectl installed and configured
• Access to a Kubernetes cluster

The README recommends this npx launch for MCP clients. Python installation instead requires Python 3.9+. Optional UI features have a separate dependency extra. Docker can use stdio or --transport sse. The tool list here is a selection of explicitly named README operations, not the entire catalog.

kubectl-mcp-server Cursor configuration

1. Choose Cursor configuration scope

   For kubectl-mcp-server, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

2. Add kubectl-mcp-server to Cursor

   Use the kubectl-mcp-server entry below in mcpServers. Keep kubectl-mcp-server's documented stdio connection fields and your other Cursor entries.

3. Check kubectl-mcp-server in Cursor

   kubectl-mcp-server: Enable in Cursor’s MCP settings; inspect tools.

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

kubectl-mcp-server tools available to Cursor

kubectl-mcp-server's stored tool list documents 23 tools; compare it with Cursor's connected tool list, because the stored list is not a live check.

get_pods

Find get_pods under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

List pods for a Kubernetes namespace.

get_logs

Find get_logs under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

get_pod_events

Find get_pod_events under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

diagnose_pod_crash

Find diagnose_pod_crash under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

create_deployment

Find create_deployment under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

scale_deployment

Find scale_deployment under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

kubectl_rollout

Find kubectl_rollout under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

diagnose_network_connectivity

Find diagnose_network_connectivity under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

check_dns_resolution

Find check_dns_resolution under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

audit_rbac_permissions

Find audit_rbac_permissions under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

check_secrets_security

Find check_secrets_security under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

helm_list

Find helm_list under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

install_helm_chart

Find install_helm_chart under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Install an application from a Helm chart.

helm_rollback

Find helm_rollback under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Return a Helm release to an earlier revision.

get_current_context

Find get_current_context under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Report the selected Kubernetes context.

switch_context

Find switch_context under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Select another configured Kubernetes context.

list_contexts

Find list_contexts under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

List configured Kubernetes contexts.

get_resource_recommendations

Find get_resource_recommendations under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Suggest resource settings based on workload analysis.

get_idle_resources

Find get_idle_resources under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Find resources that appear idle.

get_cost_analysis

Find get_cost_analysis under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Analyze cluster resource costs.

get_overprovisioned_resources

Find get_overprovisioned_resources under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Identify workloads with excessive resource allocation.

delete_resource

Find delete_resource under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Delete a selected Kubernetes resource.

show_cluster_overview_ui

Find show_cluster_overview_ui under kubectl-mcp-server in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Present an optional interactive cluster overview.

kubectl-mcp-server: full stored tool descriptions

Troubleshooting kubectl-mcp-server in Cursor

• Cursor must find npx kubectl-mcp-server (Node.js/npm) for kubectl-mcp-server. Enable the project/user entry in MCP settings and inspect its tools.
• kubectl-mcp-server uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: Needs kubectl configuration and working cluster access.
• Known limitation: The tool catalog includes destructive resource operations.
• Known limitation: Interactive dashboards require optional dependencies.
• General Cursor troubleshooting lives in the /clients/cursor guide.

Frequently asked questions