K8s MCP Server

Created By
christian-schlichtherle10 months ago
An MCP server for comprehensive access to one or more Kubernetes clusters
Overview

What is K8s MCP Server?

K8s MCP Server is a tool designed to provide comprehensive access to one or more Kubernetes clusters, enhancing Kubernetes management with AI-friendly port-forward management and supporting headless services.

How to use K8s MCP Server?

To use K8s MCP Server, install the required dependencies, set the necessary environment variables for Kubernetes configurations, and run the server using Python.

Key features of K8s MCP Server?

  • kubectl-Inspired Output Formats: Supports multiple output formats for efficient token usage.
  • Resource Kind Discovery: Allows natural language queries to find resources by keywords.
  • URL-based Configuration: Enables sharing of port-forward configurations via GitHub Gists or local files.
  • Headless Service Support: Facilitates direct pod targeting via label selectors.
  • AI-Optimized: Features a clean service/target structure for intelligent fuzzy matching.
  • Session Management: Tracks in-memory port-forward sessions with capabilities to list and teardown.

Use cases of K8s MCP Server?

  1. Setting up port-forwarding to specific services in a Kubernetes cluster.
  2. Discovering available resources and their configurations in a cluster.
  3. Managing multiple Kubernetes clusters efficiently with AI assistance.

FAQ from K8s MCP Server?

  • Can K8s MCP Server manage multiple clusters?

Yes! It is designed to provide access to one or more Kubernetes clusters.

  • Is K8s MCP Server easy to set up?

Yes! Follow the quick start guide to install dependencies and configure the environment.

  • What programming language is K8s MCP Server written in?

K8s MCP Server is implemented in Python.

Server Config

{
  "mcpServers": {
    "k8s": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/k8s-mcp",
        "run",
        "k8s-mcp"
      ],
      "env": {
        "KUBECONFIG_ALIASES": "development=dev production=prod",
        "KUBECONFIG_URLS": "dev=file:///path/to/development/k3s/kubeconfig.yaml prod=file:///path/to/production/k3s/kubeconfig.yaml",
        "PORT_FORWARD_CONFIG_URL": "file:///path/to/k8s-mcp/port-forward-config.yaml"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
christian-schlichtherle
Star
-
Language
-
License
-
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago