The Kubernetes MCP server provides a powerful interface for AI tools to interact with Kubernetes clusters. This server connects directly to the Kubernetes API, allowing AI assistants to manage resources without relying on external command-line tools.
The fastest way to get started is using NPX if you have Node.js installed:
npx -y kubernetes-mcp-server@latest
Add the MCP server to your claude_desktop_config.json:
{
"mcpServers": {
"kubernetes": {
"command": "npx",
"args": [
"-y",
"kubernetes-mcp-server@latest"
]
}
}
}
Install using the one-click method by clicking on this link: Install in VS Code
Or manually with:
# For VS Code
code --add-mcp '{"name":"kubernetes","command":"npx","args":["kubernetes-mcp-server@latest"]}'
# For VS Code Insiders
code-insiders --add-mcp '{"name":"kubernetes","command":"npx","args":["kubernetes-mcp-server@latest"]}'
Install with: Install MCP Server
Or manually edit the mcp.json file:
{
"mcpServers": {
"kubernetes-mcp-server": {
"command": "npx",
"args": ["-y", "kubernetes-mcp-server@latest"]
}
}
}
Add to your config.yaml:
extensions:
kubernetes:
command: npx
args:
- -y
- kubernetes-mcp-server@latest
The server can be configured with command line arguments:
npx kubernetes-mcp-server@latest --help
Key configuration options include:
| Option | Description |
|---|---|
--port |
Starts the server in HTTP mode on specified port |
--log-level |
Sets logging verbosity (0-9) |
--config |
Path to main TOML configuration file |
--config-dir |
Path to drop-in configuration directory |
--kubeconfig |
Path to Kubernetes configuration file |
--list-output |
Output format for resource listings (yaml or table) |
--read-only |
Run in read-only mode (no modifications allowed) |
--disable-destructive |
Disable destructive operations like delete |
--toolsets |
Comma-separated list of toolsets to enable |
Control which features are available by enabling specific toolsets:
By default, the config, core, and helm toolsets are enabled.
The server supports both a main config file and drop-in configuration files:
kubernetes-mcp-server --config /etc/kubernetes-mcp-server/config.toml
Configuration files use TOML format and are merged in this order:
For example, to enable only specific toolsets:
# /etc/kubernetes-mcp-server/conf.d/10-toolsets.toml
toolsets = ["core", "config", "helm"]
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "kubernetes" '{"command":"npx","args":["-y","kubernetes-mcp-server@latest"]}'
See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:
{
"mcpServers": {
"kubernetes": {
"command": "npx",
"args": [
"-y",
"kubernetes-mcp-server@latest"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.json2. Add this to your configuration file:
{
"mcpServers": {
"kubernetes": {
"command": "npx",
"args": [
"-y",
"kubernetes-mcp-server@latest"
]
}
}
}
3. Restart Claude Desktop for the changes to take effect