Skip to main content
Glama
TaichiHo

k8s-interactive-mcp

by TaichiHo
README.md
# k8s-interactive-mcp

A MCP server that can run Kubernetes commands with a given kubeconfig path and provide interpretation of the commands.

<a href="https://glama.ai/mcp/servers/gwvs0s78be"><img width="380" height="200" src="https://glama.ai/mcp/servers/gwvs0s78be/badge" alt="k8s-interactive-mcp MCP server" /></a>

## Result

<img src="./demo.png" alt="k8s-interactive demo" />

## Features

- Run kubectl commands through MCP tools
- Flexible command line piping
- Automatic kubectl installation check
- Support for custom kubeconfig paths
- Error handling and helpful messages

## Usage

1. Install dependencies:
```bash
npm install
```

Build the server:
```bash
npm run build
```

For development with auto-rebuild:
```bash
npm run watch
```

## Installation

To use with Claude Desktop, add the server config:

On MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`

```json
{
  "mcpServers": {
    "k8s-interactive": {
      "command": "/path/to/k8s-interactive/build/index.js"
    }
  }
}
```

### Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script:

```bash
npm run inspector
```

The Inspector will provide a URL to access debugging tools in your browser.

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as running kubectl commands, making it impossible for an agent to confuse it with another tool.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'run_kubectl_command' follows a clear verb_noun pattern, and there are no other tools to create inconsistency.

Tool Count2/5

A single tool is too few for a Kubernetes management server, as it lacks coverage for common operations like listing resources, applying configurations, or checking cluster status. This forces agents to rely solely on raw kubectl commands, which is inefficient and error-prone for the domain.

Completeness2/5

The tool surface is severely incomplete for Kubernetes management. While 'run_kubectl_command' provides a generic entry point, it lacks dedicated tools for essential operations such as get, apply, delete, describe, or logs, leaving significant gaps that will cause agent failures in automated workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues