MCP Server Kubernetes

Created By
Flux159a year ago
MCP Server for kubernetes management commands
Overview

What is mcp-server-kubernetes?

mcp-server-kubernetes is a management server that connects to a Kubernetes cluster, enabling users to execute various management commands related to the cluster.

How to use mcp-server-kubernetes?

To use mcp-server-kubernetes, you need to install kubectl and have a valid kubeconfig file. Launch the server with the command 'npx mcp-server-kubernetes', and it will connect to your current kubectl context. Verify the connection by listing your pods or creating a test deployment.

Key features of mcp-server-kubernetes?

  • Connects to a Kubernetes cluster seamlessly
  • Lists all pods, services, and deployments
  • Enables creating and deleting pods
  • Supports namespace management and Helm chart installations

Use cases of mcp-server-kubernetes?

  1. Managing deployments in a Kubernetes cluster
  2. Troubleshooting applications by retrieving pod logs
  3. Setting up testing environments using minikube or GKE

FAQ from mcp-server-kubernetes?

  • What do I need to use mcp-server-kubernetes?

You need kubectl installed, a valid kubeconfig file, and access to a Kubernetes cluster.

  • Can I manage multiple clusters?

Not currently planned, as authentication and adding clusters to kubectx is not implemented yet.

  • What should I do if I encounter connection issues?

Check your kubectl setup by running 'kubectl get pods' in your terminal to ensure no credential issues exist.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Flux159
Star
723
Language
TypeScript
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