mcp-kubernetes

Created By
Azurea year ago
A Model Context Protocol (MCP) server that enables AI assistants to interact with Kubernetes clusters. It serves as a bridge between AI tools (like Claude, Cursor, and GitHub Copilot) and Kubernetes
Overview

What is mcp-kubernetes?

The mcp-kubernetes is a Model Context Protocol (MCP) server that enables AI assistants to interact with Kubernetes clusters, acting as a bridge between AI tools and Kubernetes by translating natural language requests into Kubernetes operations.

How to use mcp-kubernetes?

To use mcp-kubernetes, install it via Docker or locally, configure your MCP servers in supported AI clients, and then ask questions about your Kubernetes cluster in natural language.

Key features of mcp-kubernetes?

  • Query Kubernetes resources and execute kubectl commands through natural language.
  • Manage Kubernetes clusters and diagnose resource states.
  • Supports both read-only and read-write operations with various tools.

Use cases of mcp-kubernetes?

  1. Querying the status of Kubernetes clusters.
  2. Diagnosing issues with specific pods or services.
  3. Managing Kubernetes resources through AI tools.

FAQ from mcp-kubernetes?

  • Can I use mcp-kubernetes with any AI tool?

Yes, it is compatible with various AI tools like Claude, Cursor, and GitHub Copilot.

  • Is there a read-only mode?

Yes, mcp-kubernetes can be run in read-only mode to prevent write operations.

  • How do I install mcp-kubernetes?

You can install it using Docker or by setting it up locally with kubectl and helm.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Azure
Star
8
Language
Go
License
MIT license

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