Enterprise DNA
M MCP Servers Developer low

strowk/mcp-k8s-go

by Various

MCP server connecting to Kubernetes

S

MCP

strowk/mcp-k8s-go

Added 1 June 2026

#kubernetes #mcp #server

Overview

strowk/mcp-k8s-go is a Go-based server that implements the Model Context Protocol to connect AI assistants to Kubernetes clusters. It exposes cluster resources and state via the MCP standard, enabling external tools to query and interact with Kubernetes.

Best for

Best for
Developers building AI-assisted Kubernetes monitoring and management tools

Use cases

  • Query live Kubernetes cluster state from an AI assistant
  • Monitor and troubleshoot clusters through natural language interfaces
  • Integrate Kubernetes operations into MCP-compatible automation workflows

Notes

strowk/mcp-k8s-go is a Go-based server that implements the Model Context Protocol to connect AI assistants to Kubernetes clusters. It exposes cluster resources and state via the MCP standard, enabling external tools to query and interact with Kubernetes.

382 stars on GitHub. Last updated 2025-12-22. Licensed MIT.

Use cases

  • Query live Kubernetes cluster state from an AI assistant
  • Monitor and troubleshoot clusters through natural language interfaces
  • Integrate Kubernetes operations into MCP-compatible automation workflows

Pros

  • Written in Go, offering fast startup and low resource usage
  • Open source with 382 stars and active community interest
  • Follows the MCP standard, enabling interoperability with various AI clients

Cons

  • Requires running a separate server process and MCP client setup
  • Limited to Kubernetes clusters accessible via standard kubeconfig
  • Capabilities depend on the implementer’s extension of MCP resource definitions

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Written in Go, offering fast startup and low resource usage
  • Open source with 382 stars and active community interest
  • Follows the MCP standard, enabling interoperability with various AI clients

Cons

  • Requires running a separate server process and MCP client setup
  • Limited to Kubernetes clusters accessible via standard kubeconfig
  • Capabilities depend on the implementer's extension of MCP resource definitions