k0rdent MCP Server

⚠️ Experimental Development Tool – Early stage, expect issues

🚧 Localhost Only – No TLS, admin kubeconfig required

🤖 Developed with AI-Assistance – Code quality and security not production-ready

USE AT YOUR OWN RISK

You use this experimental MCP server at your own risk. Neither Randy Bias nor Mirantis, Inc. take any responsibility for your usage. This is a proof of concept for using AI agents to control k0rdent management and child clusters through the MCP protocol. It is absolutely NOT production-ready.

What This Is

An experimental MCP server that exposes k0rdent cluster management capabilities to AI assistants through the Model Context Protocol. This is a development tool for k0rdent developers and early adopters who want to explore MCP integration, not a production-ready solution.

Key Points:

• Runs on localhost only (no TLS support)
• Requires admin kubeconfig to an existing k0rdent management cluster
• Does NOT provision a management cluster for you
• Built with AI assistance - code quality needs improvement
• Provider support varies: Azure tested, AWS minimal, GCP untested

What This Isn't

• ❌ Not production-ready
• ❌ Not a standalone tool (needs existing k0rdent cluster)
• ❌ Not secure for network exposure (localhost only)
• ❌ Not fully tested across all providers
• ❌ Not suitable for RBAC-restricted environments (requires admin access)

Prerequisites (All Required)

Before starting, you must have:

1. Existing k0rdent management cluster – This tool does NOT create one for you. You need a running k0rdent installation.
2. Admin kubeconfig – Full cluster access required. RBAC limitations not tested.
3. Go 1.24+ – To build from source.
4. MCP-compatible client – Claude Desktop recommended.
5. k0rdent knowledge – Understanding of ClusterDeployments, ServiceTemplates, credentials, etc.
6. Localhost deployment – No remote access, no TLS.

Known Limitations & Issues

Read this section carefully before using:

Provider Support

• GCP: Not tested, may not work at all
• Azure: Works but requires manual subscription ID parameter (not auto-detected)
• AWS: Minimally tested, expect issues

Authentication & Security

• Only admin kubeconfig – No OIDC support, no RBAC enforcement
• AI-assisted code – Not security-reviewed, use at your own risk
• Localhost only – No TLS, runs on 127.0.0.1 only
• No auth modes – Only kubeconfig-based access

Functionality Gaps

• Catalog operations – Synchronization may have bugs
• Concurrent operations – Race conditions possible
• Error recovery – May leave orphaned cloud resources
• Resource cleanup – Not guaranteed on failures

Deployment Warnings

• Creates real cloud resources – Costs apply to your cloud account
• May leave orphans – Failed deployments may not clean up completely
• Experimental – Expect crashes and unexpected behavior

Quick Start (Experimental)

1. Clone the repository

   git clone https://github.com/randybias/k0rdent-mcp-server.git
   cd k0rdent-mcp-server
   

2. Build the server

   go build -o server cmd/server/main.go
   

3. Set required environment variables

   # Required: Point to your k0rdent cluster kubeconfig
   export K0RDENT_MGMT_KUBECONFIG_PATH=/path/to/admin-kubeconfig
   
   # Optional: Override default (defaults to 127.0.0.1:6767 for security)
   export LISTEN_ADDR=127.0.0.1:3000
   
   # Optional: Set log level
   export LOG_LEVEL=debug
   

4. Start the server

   ./server start
   

5. Configure Claude Code (see detailed instructions below)

6. Try safe operations first

   • List namespaces (safest)
   • List cluster templates
   • List credentials

   WARNING: Cluster deployment operations will create real cloud resources and incur costs.

Claude Code Setup

Installation

1. Install Claude Code (if not alread

... View full README on GitHub