MCP K8S Go

The MCP K8S server provides the following capabilities through prompts, resources, and tools:

• Contexts & Namespaces: List Kubernetes contexts and namespaces.
• Resource Management: List, get, create, and modify any Kubernetes resources (includes custom mappings for pods, services, and deployments).
• Cluster Inspection: List Kubernetes nodes and get Kubernetes events.
• Pod Operations: List pods, get pod logs, and run commands in a Kubernetes pod.

To test and browse the capabilities of the latest published version of the MCP K8S Go server, you can use the Model Context Protocol Inspector by running the following command:

npx @modelcontextprotocol/inspector npx @strowk/mcp-k8s

If you have npm installed, you can install the pre-built binaries globally:

npm install -g @strowk/mcp-k8s

To use it with Claude Desktop, add the following to your claude_desktop_config.json:

{
  "mcpServers": {
    "mcp_k8s": {
      "command": "mcp-k8s",
      "args": []
    }
  }
}

Alternatively, you can use npx in your configuration:

{
  "mcpServers": {
    "mcp_k8s": {
      "command": "npx",
      "args": [
        "@strowk/mcp-k8s"
      ]
    }
  }
}

To automatically install MCP K8S Go for Claude Desktop using mcp-get, run:

npx @michaellatman/mcp-get@latest install @strowk/mcp-k8s

To build the server from source, you must have Golang installed. Run:

go get github.com/strowk/mcp-k8s-go
go install github.com/strowk/mcp-k8s-go

Then, add this configuration to your claude_desktop_config.json:

{
  "mcpServers": {
    "mcp_k8s_go": {
      "command": "mcp-k8s-go",
      "args": []
    }
  }
}

To use MCP K8S with Claude Desktop, add the server configuration to your claude_desktop_config.json file.

By default, use the following configuration to allow access to all contexts with full permissions:

{
    "mcpServers": {
        "mcp_k8s": {
            "command": "mcp-k8s",
            "args": []
        }
    }
}

Once configured, Claude Desktop can access Kubernetes contexts as resources and perform tasks like listing pods, events, or reading logs.

The server is available as a multi-arch Docker image (linux/amd64 and linux/arm64).

To run it manually:

docker run -i -v ~/.kube/config:/home/nonroot/.kube/config --rm mcpk8s/server:latest

Note: Windows users using Git Bash may need to use //c/Users/<username>/.kube/config for the volume mount.

To use it with Claude Desktop, add this to claude_desktop_config.json:

{
  "mcpServers": {
    "mcp_k8s_go": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "-v",
        "~/.kube/config:/home/nonroot/.kube/config",
        "--rm",
        "mcpk8s/server:latest"
      ]
    }
  }
}

Install the MCP K8S server globally using npm to make the mcp-k8s command available in your terminal.

After installation, verify it works by checking the version:

mcp-k8s --version

npm install -g @strowk/mcp-k8s

You can restrict the MCP K8S server's capabilities and access scope by passing arguments in the args array of your claude_desktop_config.json.

Common use cases include:

• Restricting access to specific Kubernetes contexts.
• Enabling a read-only mode to prevent accidental cluster modifications.

Example configuration for a restricted environment (allowing only dev and prod contexts in read-only mode):

{
    "mcpServers": {
        "mcp_k8s": {
            "command": "mcp-k8s",
            "args": [
                "--allowed-contexts=dev,prod",
                "--readonly"
            ]
        }
    }
}

To automatically install MCP K8S Go for Claude Desktop using Smithery, run:

npx -y @smithery/cli install @strowk/mcp-k8s --client claude

1. Download the latest release for your platform from GitHub releases.
2. Unpack the archive containing the mcp-k8s-go binary.
3. Place the binary in your PATH.
4. Add the following to your claude_desktop_config.json:

{
  "mcpServers": {
    "mcp_k8s": {
      "command": "mcp-k8s-go",
      "args": []
    }
  }
}

The mcp-k8s server exposes the following MCP capabilities:

Tools

The server provides tools to interact with your Kubernetes cluster. Depending on whether --readonly is enabled, the following categories of tools are available:

• Inspection Tools: ListContextsTool, ListNamespacesTool, ListResourcesTool, GetResourceTool, ListNodesTool, ListEventsTool, ListPodsPrompt (via prompts), and PodLogsTool.
• Write/Action Tools (Disabled in --readonly mode): ApplyK8sResourceTool and PodExecCommandTool.

Prompts

Pre-defined prompts to help guide LLM interactions, such as:

• ListPodsPrompt
• ListNamespacesPrompt

Resources

The server provides resource providers, such as ContextsResourceProvider, which allows the LLM to discover available Kubernetes contexts.