Kubernetes MCP Server

✓ verified

Inspect and manage Kubernetes clusters via your kubeconfig.

Don't have ToolPiper? We'll take you to the download.

Open repository →

Publisher

Containers (Red Hat)

License

Apache-2.0

Transport

Local subprocess

Tools

5

What this server does

This server gives the assistant the read and write surface of kubectl, scoped to whatever your current kubeconfig context allows. List pods, read logs, get and list any resource kind, inspect events, and apply changes. It uses your existing kubeconfig, so it already respects your RBAC: the assistant can do exactly what your current context can do, no more. Point your context at a staging cluster while you get comfortable. Pair it with a Grafana or Prometheus server to correlate a crashlooping pod with its metrics.

Tools included

  • pods_list

    List pods across namespaces.

  • pods_log

    Read logs from a pod.

  • resources_get

    Get any Kubernetes resource by kind and name.

  • resources_list

    List resources of a given kind.

  • events_list

    List recent cluster events.

The authoritative list comes from the server's tools/list at runtime. This catalog entry may lag the upstream until the next ToolPiper release.

Install in ToolPiper

ToolPiper handles the JSON configuration. Click Install, fill in any required tokens, and the server is ready in your chat.

Don't have ToolPiper? We'll take you to the download.

Install in another client

Install in another MCP client (Claude Desktop, Cursor, Continue, Cline)

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json.

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

Example prompts

  • "List the pods in the payments namespace and flag any that are not Running."

  • "Show me the last 100 log lines from the api deployment."

  • "What events fired in the default namespace in the last hour?"

Security notes

The server inherits your kubeconfig and its RBAC, so it can do whatever your current context permits, including writes and deletes if your role allows them. Switch to a read-only or staging context before connecting, and treat a production-admin context as live ammunition. There is no separate token to manage; the kubeconfig file on disk is the credential.

Related tools