MCP Server Integration¶
The PDB Management Operator includes an integrated Model Context Protocol (MCP) server that enables AI-powered cluster analysis, intelligent recommendations, and natural language interaction for availability management.
Overview¶
The MCP server exposes tools that can be consumed by AI assistants (Claude, GPT, etc.) to analyze your Kubernetes cluster’s availability posture and provide intelligent recommendations.
sequenceDiagram
autonumber
participant Claude as Claude Client
participant GPT as GPT Client
participant Custom as Custom MCP Client
box MCP Server Layer
participant Transport as HTTP Transport<br/>(JSON-RPC + AI Proxy)
participant Core as MCP Core Server<br/>(Tools/Prompts/Resources)
end
box K8s Cluster
participant APIServer as Kubernetes API Server
participant Deployments as Deployments
participant PDBs as PodDisruptionBudgets
participant Policies as AvailabilityPolicies CRD
end
%% Example: Query Availability State
rect rgb(230, 230, 250)
note over Claude,GPT: Any client can follow the same flow (Claude/GPT/Custom)
Claude->>Transport: JSON-RPC request<br/>(e.g. "Get availability for service X")
Transport->>Core: Validate + forward MCP request
Core->>Core: Resolve tool / prompt / resource
Core->>APIServer: Call K8s API<br/>(list Deployments, PDBs, AvailabilityPolicies)
APIServer->>Deployments: Get Deployments for service X
APIServer->>PDBs: Get PDBs for service X
APIServer->>Policies: Get AvailabilityPolicies for service X
Deployments-->>APIServer: Deployment status
PDBs-->>APIServer: PDB status
Policies-->>APIServer: Policy spec & status
APIServer-->>Core: Aggregated K8s state
Core->>Core: Evaluate availability / apply rules
Core-->>Transport: Structured result<br/>(e.g. "AvailableClass=Gold, issues=[]")
Transport-->>Claude: JSON-RPC response
end
%% Example: Optional mutation
rect rgb(240, 255, 240)
note over Custom,Policies: Update via a Custom MCP Client
Custom->>Transport: JSON-RPC request<br/>("Update AvailabilityPolicy for service Y")
Transport->>Core: Forward update request
Core->>APIServer: Apply change to AvailabilityPolicies
APIServer->>Policies: Update CRD spec
Policies-->>APIServer: Status updated
APIServer-->>Core: Confirmation / new status
Core-->>Transport: Result ("Policy updated")
Transport-->>Custom: JSON-RPC response
end
Configuration¶
Enable MCP Server¶
Set environment variables in the operator deployment:
env:
- name: ENABLE_MCP_SERVER
value: "true"
- name: MCP_SERVER_ADDRESS
value: ":8090" # Default port
Or via Helm values:
mcp:
enabled: true
port: 8090
Verify MCP Server is Running¶
# Check health endpoint
curl http://localhost:8090/health
# Response:
{
"status": "healthy",
"server": "pdb-management-mcp-server",
"version": "v1.0.0",
"initialized": true,
"timestamp": 1720267822
}
Available Tools¶
The MCP server provides the following tools for AI-powered analysis:
1. Analysis Tools¶
Tool |
Description |
|---|---|
|
Comprehensive cluster availability analysis |
|
Deep analysis of a specific deployment |
|
Quick summary of cluster availability status |
2. Management Tools¶
Tool |
Description |
|---|---|
|
List all PDBs with their status |
|
List deployments with availability info |
|
Get detailed PDB information |
|
Create a new PDB for a deployment |
|
Update an existing PDB configuration |
|
Remove a PDB |
3. Compliance Tools¶
Tool |
Description |
|---|---|
|
Check availability policy compliance |
|
Generate compliance report |
|
List policy violations |
4. Optimization Tools¶
Tool |
Description |
|---|---|
|
AI-powered optimization suggestions |
|
Resource utilization analysis |
|
Impact prediction for changes |
5. Monitoring Tools¶
Tool |
Description |
|---|---|
|
Overall cluster health status |
|
Recent disruption events |
|
PDB-related metrics |
6. Backup Tools¶
Tool |
Description |
|---|---|
|
Backup all PDB configurations |
|
Restore PDB configurations |
|
List available backups |
API Endpoints¶
MCP Protocol Endpoint¶
POST /mcp
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": "1",
"method": "tools/call",
"params": {
"name": "analyze_cluster_availability",
"arguments": {
"namespace": "production"
}
}
}
AI Proxy Endpoint¶
For direct AI provider integration:
POST /ai/proxy
Content-Type: application/json
{
"config": {
"provider": "claude",
"apiKey": "your-api-key",
"model": "claude-sonnet-4-20250514"
},
"request": {
"messages": [
{"role": "user", "content": "Analyze my cluster's availability"}
]
}
}
Health Endpoint¶
GET /health
Connecting AI Clients¶
Using with Claude Desktop¶
Add to your Claude Desktop MCP configuration (~/.claude/mcp.json):
{
"servers": {
"pdb-management": {
"url": "http://localhost:8090/mcp",
"transport": "http"
}
}
}
Using with Custom MCP Client¶
import requests
def call_mcp_tool(tool_name, arguments):
response = requests.post(
"http://localhost:8090/mcp",
json={
"jsonrpc": "2.0",
"id": "1",
"method": "tools/call",
"params": {
"name": tool_name,
"arguments": arguments
}
}
)
return response.json()
# Analyze cluster availability
result = call_mcp_tool("analyze_cluster_availability", {
"namespace": "production"
})
print(result)
Port Forwarding for Local Access¶
# Forward MCP server port
kubectl port-forward -n canvas svc/pdb-management-mcp 8090:8090
# Now accessible at localhost:8090
curl http://localhost:8090/health
Example Interactions¶
1. Cluster Analysis¶
Request:
{
"method": "tools/call",
"params": {
"name": "analyze_cluster_availability",
"arguments": {}
}
}
Response:
{
"result": {
"summary": {
"total_deployments": 45,
"protected_deployments": 38,
"unprotected_deployments": 7,
"coverage_percentage": 84.4
},
"by_class": {
"mission-critical": 5,
"high-availability": 18,
"standard": 15,
"non-critical": 7
},
"recommendations": [
"7 deployments have no PDB protection",
"Consider adding PDBs to: api-gateway, cache-service..."
]
}
}
2. Get Optimization Recommendations¶
Request:
{
"method": "tools/call",
"params": {
"name": "get_optimization_recommendations",
"arguments": {
"namespace": "production",
"focus": "availability"
}
}
}
Response:
{
"result": {
"recommendations": [
{
"type": "pdb",
"priority": "high",
"title": "Increase minAvailable for payment-service",
"description": "Critical service with only 50% minAvailable",
"actions": ["Update to 75% or higher"],
"expected_benefit": "Improved availability during disruptions"
}
]
}
}
3. Compliance Check¶
Request:
{
"method": "tools/call",
"params": {
"name": "check_compliance",
"arguments": {
"policy": "production-standards"
}
}
}
Metrics¶
The MCP server exposes Prometheus metrics:
# MCP request metrics
pdb_management_mcp_requests_total{method="tools/call",status="success"}
pdb_management_mcp_request_duration_seconds{method="tools/call"}
# Tool usage metrics
pdb_management_mcp_tool_calls_total{tool="analyze_cluster_availability"}
pdb_management_mcp_tool_duration_seconds{tool="analyze_cluster_availability"}
Security Considerations¶
Network Security: MCP server should only be accessible within the cluster or via authenticated ingress
API Key Management: When using AI proxy, API keys are not stored
Audit Logging: All MCP operations are logged with correlation IDs
RBAC: MCP server uses the operator’s service account permissions
Recommended Network Policy¶
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: mcp-server-policy
namespace: canvas
spec:
podSelector:
matchLabels:
app: pdb-management
ingress:
- from:
- namespaceSelector:
matchLabels:
mcp-client: "true"
ports:
- port: 8090
Troubleshooting¶
MCP Server Not Responding¶
# Check if MCP is enabled
kubectl get deployment pdb-management-controller-manager -n canvas \
-o jsonpath='{.spec.template.spec.containers[0].env}' | jq '.[] | select(.name=="ENABLE_MCP_SERVER")'
# Check logs
kubectl logs -n canvas deployment/pdb-management-controller-manager | grep mcp
Tool Call Errors¶
# Enable debug logging
kubectl set env deployment/pdb-management-controller-manager \
-n canvas LOG_LEVEL=debug
# Check for specific errors
kubectl logs -n canvas deployment/pdb-management-controller-manager | \
jq 'select(.msg | contains("MCP"))'