Claude Kubernetes MCP Server

A GitOps Model Context Protocol (MCP) Server. That is what the claude kubernetes mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

This repository contains the Claude Kubernetes MCP (Model Context Protocol) server, built in Go. The server integrates with ArgoCD, GitLab, Claude AI, and Kubernetes to enable advanced control and automation of Kubernetes environments.

This server is designed to orchestrate Kubernetes workloads using Claude AI, GitLab, ArgoCD, and Vault. It exposes a REST API that allows programmatic interaction with these systems, driven by a configured config.yaml and authenticated using an API key.

The tools it exposes

The server publishes 3 tools. What each one is for:

• General — The General tool exposed by this server
• Kubernetes — The Kubernetes tool exposed by this server
• ArgoCD — The ArgoCD tool exposed by this server

What it needs from you

Configuration is passed through the environment: ARGOCD_USERNAME, ARGOCD_PASSWORD, GITLAB_TOKEN, CLAUDE_API_KEY, VAULT_TOKEN, KUBECONFIG, AUTH_TOKEN, PROJECT_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Go 1.20+ - Docker - Kubernetes cluster & valid ~/.kube/config - EKS cluster with AWS_PROFILE set locally - ArgoCD credentials - GitLab personal access token - Claude API key (Anthropic) - Vault credentials (optional, depending on use)

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Claude Kubernetes's toolset — General, Kubernetes, ArgoCD — is a fair guide to whether it matches your workflow. It is maintained by Blankcut; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Claude Kubernetes's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.