K8s Mcp Server

Created By
chinnareddy578a year ago
K8s MCP Server
Overview

what is K8s MCP Server?

K8s MCP Server is a Model Control Protocol (MCP) server designed for managing Kubernetes operations, including deployments, pods, and services.

how to use K8s MCP Server?

To use K8s MCP Server, you can either run it using Docker or directly with Python. For Docker, pull the image and run the container. For Python, set up a virtual environment, install dependencies, and run the server.

key features of K8s MCP Server?

  • Management of Kubernetes deployments, pods, and services.
  • Compatibility with various MCP clients like GitHub Copilot and Claude Desktop.
  • Easy setup using Docker or Python.

use cases of K8s MCP Server?

  1. Managing Kubernetes resources efficiently.
  2. Integrating with development tools for enhanced code suggestions.
  3. Facilitating automated deployments and service management.

FAQ from K8s MCP Server?

  • What are the prerequisites for using K8s MCP Server?

You need Docker, Python 3.12 or higher, and the uv package manager.

  • Can I run K8s MCP Server without Docker?

Yes, you can run it directly using Python by setting up a virtual environment.

  • How do I configure MCP clients to use the server?

Set the MCP server URL to http://localhost:8080 in your client settings.

Server Config

{
  "mcpServers": {
    "k8s-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "http://localhost:8081/mcp"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
chinnareddy578
Star
0
Language
Python
License
-
Category

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago