Skip to main content
Glama
Sign In
enesjakozh
k8s-interactive-mcp

k8s-interactive-mcp

by TaichiHo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

k8s-interactive-mcp

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

Result

Related MCP server: kubernetes-mcp-server

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:

npm install

Build the server:

npm run build

For development with auto-rebuild:

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

{
  "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, which is available as a package script:

npm run inspector

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

Available Tools

1 tool
run_kubectl_commandC

Run a kubectl command against the cluster pointed to by the current kubeconfig

Inputs: command (required), kubeconfig (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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.

    Resources

    Related MCP Connectors

    Related MCP Servers

    Appeared in Searches