Kubernetes MCP Server for Claude Desktop: Setup & Config

What you can do with Kubernetes in Claude Desktop

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.
• Manage Helm releases through selected toolsets.

Before you start: Kubernetes in Claude Desktop

• 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 Claude Desktop configuration

1. Choose Claude Desktop configuration scope

   For Kubernetes MCP Server, open macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json. Merge under mcpServers via Settings → Developer → Edit Config when available.

2. Add Kubernetes MCP Server to Claude Desktop

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

3. Check Kubernetes MCP Server in Claude Desktop

   Kubernetes MCP Server: Fully quit and reopen Claude Desktop; check developer diagnostics.

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

Troubleshooting Kubernetes in Claude Desktop

• Fully quit and reopen Claude Desktop for Kubernetes MCP Server. If npx kubernetes-mcp-server@latest (Node.js/npm) is missing, check the desktop process's PATH, which may differ from your terminal.
• Kubernetes MCP Server uses stdio here: Claude Desktop 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 Claude Desktop troubleshooting lives in the /clients/claude-desktop guide.

Frequently asked questions