Features
MCP prompt resource tool
- List Kubernetes contexts
- List Kubernetes namespaces
- List and get any Kubernetes resources
- includes custom mappings for resources like pods, services, deployments, but any resource can be listed and retrieved
- List Kubernetes nodes
- List Kubernetes pods
- Get Kubernetes events
- Get Kubernetes pod logs
- Run command in Kubernetes pod
Browse With Inspector
To use latest published version with Inspector you can run this:
Use With Claude
Following chat with Claude Desktop demonstrates how it looks when selected particular context as a resource and then asked to check pod logs for errors in kube-system namespace:
Claude Desktop
To use this MCP server with Claude Desktop (or any other client) you might need to choose which way of installation to use.
You have multiple options:
[object Object] | [object Object] | [object Object] | [object Object] | [object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] | [object Object] | [object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] | [object Object] | [object Object] | [object Object] | [object Object] |
Using Smithery
To install MCP K8S Go for Claude Desktop automatically via Smithery:
Using mcp-get
To install MCP K8S Go for Claude Desktop automatically via mcp-get:
Manually with prebuilt binaries
Prebuilt from npm
Use this if you have npm installed and want to use pre-built binaries:
Then check version by running
mcp-k8s --version and if this printed installed version, you can proceed to add configuration to claude_desktop_config.json file:, or using
npx with any client:For example for Claude:
From GitHub releases
Head to GitHub releases and download the latest release for your platform.
Unpack the archive, which would contain binary named
mcp-k8s-go, put that binary somewhere in your PATH and then add the following configuration to the claude_desktop_config.json file:Building from source
You would need Golang installed to build this project:
, and then add the following configuration to the
claude_desktop_config.json file:Using Docker
This server is built and published to Docker Hub since 0.3.1-beta.2 release with multi-arch images available for linux/amd64 and linux/arm64 architectures.
You can use latest tag f.e like this:
Windows users might need to replace
~/.kube/config with //c/Users/<username>/.kube/config at least in Git Bash.For Claude:
Environment Variables and Command-line Options
The following environment variables are used by the MCP server:
KUBECONFIG: Path to your Kubernetes configuration file (optional, defaults to ~/.kube/config)
The following command-line options are supported:
--allowed-contexts=<ctx1,ctx2,...>: Comma-separated list of allowed Kubernetes contexts that users can access. If not specified, all contexts are allowed.
--help: Display help information
--version: Display version information
Features
MCP prompt resource tool
- List Kubernetes contexts
- List Kubernetes namespaces
- List and get any Kubernetes resources
- includes custom mappings for resources like pods, services, deployments, but any resource can be listed and retrieved
- List Kubernetes nodes
- List Kubernetes pods
- Get Kubernetes events
- Get Kubernetes pod logs
- Run command in Kubernetes pod
Browse With Inspector
To use latest published version with Inspector you can run this:
Use With Claude
Following chat with Claude Desktop demonstrates how it looks when selected particular context as a resource and then asked to check pod logs for errors in kube-system namespace:
Claude Desktop
To use this MCP server with Claude Desktop (or any other client) you might need to choose which way of installation to use.
You have multiple options:
[object Object] | [object Object] | [object Object] | [object Object] | [object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] | [object Object] | [object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] | [object Object] | [object Object] | [object Object] | [object Object] |
Using Smithery
To install MCP K8S Go for Claude Desktop automatically via Smithery:
Using mcp-get
To install MCP K8S Go for Claude Desktop automatically via mcp-get:
Manually with prebuilt binaries
Prebuilt from npm
Use this if you have npm installed and want to use pre-built binaries:
Then check version by running
mcp-k8s --version and if this printed installed version, you can proceed to add configuration to claude_desktop_config.json file:, or using
npx with any client:For example for Claude:
From GitHub releases
Head to GitHub releases and download the latest release for your platform.
Unpack the archive, which would contain binary named
mcp-k8s-go, put that binary somewhere in your PATH and then add the following configuration to the claude_desktop_config.json file:Building from source
You would need Golang installed to build this project:
, and then add the following configuration to the
claude_desktop_config.json file:Using Docker
This server is built and published to Docker Hub since 0.3.1-beta.2 release with multi-arch images available for linux/amd64 and linux/arm64 architectures.
You can use latest tag f.e like this:
Windows users might need to replace
~/.kube/config with //c/Users/<username>/.kube/config at least in Git Bash.For Claude:
Environment Variables and Command-line Options
The following environment variables are used by the MCP server:
KUBECONFIG: Path to your Kubernetes configuration file (optional, defaults to ~/.kube/config)
The following command-line options are supported:
--allowed-contexts=<ctx1,ctx2,...>: Comma-separated list of allowed Kubernetes contexts that users can access. If not specified, all contexts are allowed.
--help: Display help information
--version: Display version information