Kubernetes MCP Server

Created By
endo-sysa year ago
Overview

what is Kubernetes MCP Server?

Kubernetes MCP Server is a Model Context Protocol (MCP) server that enables users to interact with their Kubernetes clusters using natural language through an MCP client, leveraging the MCP Python SDK.

how to use Kubernetes MCP Server?

To use the server, clone the repository, install the dependencies, and run the server using Python. Connect through an MCP client to issue commands in natural language.

key features of Kubernetes MCP Server?

  • Comprehensive pod, deployment, service, namespace, and cluster operations.
  • Natural language interaction with Kubernetes resources.
  • Modular design for easy extension and maintenance.

use cases of Kubernetes MCP Server?

  1. Managing Kubernetes pods and deployments through simple commands.
  2. Automating cluster operations and maintenance tasks.
  3. Simplifying Kubernetes management for users unfamiliar with command-line tools.

FAQ from Kubernetes MCP Server?

  • What are the prerequisites for using the server?

You need Python 3.7+, kubectl, access to a Kubernetes cluster, and an MCP client.

  • Is the server easy to install?

Yes! Just clone the repository and install the dependencies using pip.

  • Can I contribute to the project?

Absolutely! Contributions are welcome, and you can submit a Pull Request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
endo-sys
Star
0
Language
Python
License
MIT license

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.

8 hours ago