K8s Mcp Server

Created By
Danlioa year ago
k8s-mcp-server is a Kubernetes and Helm management tool based on Model Context Protocol (MCP), designed specifically for n8n workflow automation platform. Core Features: Kubernetes Management: Provides 11 kubectl tools supporting 19 resource types for querying, monitoring, and management Helm Integration: Complete set of 5 Helm tools including release management, status queries, and configuration management n8n Compatibility: Supports SSE (Server-Sent Events) connections for direct integration into n8n workflows Project Status: Version: 2.2.0 Completion: 89.5% (34/38 features) Architecture: Node.js + Express + MCP SDK Deployment: Docker containerized, supports Kubernetes cluster deployment Main Tools: Resource Query: kubectl_get (with label selector support) Resource Monitoring: Top series tools (nodes/pods/containers) Deployment Management: Scaling, restart, HPA editing Helm Management: Release status, configuration values, deployment history Security Features: Strict input validation and character filtering Only supports safe read and controlled management operations Runs as non-root user with principle of least privilege
Overview

Features:

  • Supports 19 Kubernetes resource types management
  • Complete Helm Release lifecycle management
  • Secure input validation and permission control
  • Docker containerized deployment
  • Native n8n integration

Version: 2.2.0 | Completion: 89.5% (34/38 features)

Ideal for DevOps environments requiring Kubernetes cluster management within automated workflows.

Server Config

{
  "mcpServers": {
    "k8s-mcp-server": {
      "command": "node",
      "args": [
        "/path/to/your/k8s-mcp/k8s-mcp-server/src/index.js"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Danlio
Star
-
Language
-
License
-
Category

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
Crevio

2 days ago