Mkp MCP Server

If you want an AI assistant working directly with Mkp, the mkp mcp server is the bridge. MKP is a Model Context Protocol (MCP) server for Kubernetes that allows LLM-powered applications to interact with Kubernetes clusters. It provides tools for listing and applying Kubernetes resources through the MCP protocol.

What Mkp does

MKP is a Model Context Protocol (MCP) server for Kubernetes that allows LLM-powered applications to interact with Kubernetes clusters. It provides tools for listing and applying Kubernetes resources through the MCP protocol.

Key capabilities

• List resources supported by the Kubernetes API server
• List clustered resources
• List namespaced resources
• Get resources and their subresources (including status, scale, logs, etc.)
• Apply (create or update) clustered resources
• Apply (create or update) namespaced resources
• Execute commands in pods with timeout control
• Generic and pluggable implementation using API Machinery's unstructured client

Tools it exposes

Once connected, the assistant can call these 5 tools directly:

• get_resource — Example of getting logs from a specific container with parameters:
• list_resources — The list_resources tool provides powerful annotation filtering capabilities to control metadata output size and prevent truncation issues with large
• apply_resource — The apply_resource tool exposed by this server
• post_resource — Posts to a Kubernetes resource or its subresource, particularly useful for executing commands in pods
• Configuration — The Configuration tool exposed by this server

Installing the mkp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Requirements

• Go 1.24 or later - Kubernetes cluster and kubeconfig - Task for running tasks

Where it fits

Cloud and DevOps servers put infrastructure on speaking terms with your assistant, so "why is this broken?" is answered from real state rather than a generic checklist. Mkp sits in that group, and the shape of its toolset — get_resource, list_resources, apply_resource among others — tells you what it is really for. Worth comparing against the other cloud devops servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• Maintained by StacklokLabs, written in Go.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the mkp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.