Hatchet MCP
Local K8s DevOps Agent
This is my local AI agent setup that can run durable and fully traceable devOps agent workflows to help troubleshoot and manage my K8S clusters, using a MCP server as the control plane. Compared to using an LLM or agent harness to execute pure bash commands in the terminal, this approach has the added benefit of full audit trails and explicit approvals, by using an orchestration layer provided by Hatchet. Also onboarding is much faster, compared to traditional dashboards like Flowise or Dify, as the MCP interface hides all the complexity behind natural language interactions.
Features
Full K8s agent self-correcting loop — check cluster, diagnose, execute fixes, verify, retry until exhausted
Human-in-the-loop approval — agent pauses before every fix (unless for safe read-only checks) and waits for approval
Direct K8s tools — individual MCP tools for checking pods, logs, deployments, events, kubectl, and more through chat interface
Scheduled daily runs — daily checks at 10 AM local (UTC+8) with optional push notifications when issues are found
Durable execution — runs survive crashes, retry from last checkpoint, stop and resume at any point
Traceability — full logging from every agent run, every LLM call and bash command is recorded in Hatchet
Agent Graph Overview

check_cluster — scans pods, deployments, nodes, events for problems
diagnose — LLM analyzes cluster state and proposes a kubectl command
approve_fix — pauses for human approval (skips if command is read-only)
execute_fix — runs the approved kubectl command
verify_fix — polls cluster until healthy or timeout
decide — done (END), or retry (back to START > check_cluster)
Quick Start
Prerequisites: Python 3.12+, Docker, Just
git clone <repo>
cd hatchet-mcp
cp .env.example .env # fill in all required env vars
just start # Hatchet server - http://localhost:8888
just worker # start the Hatchet workerMCP Configuration
Tool | What it does |
| List pods, describe, logs, events, exec, problem pods |
| Run the autonomous devops agent with a task prompt |
| Approve/reject fixes, list/check/cleanup HITL threads |
| Raw kubectl commands if needed |
Add this to your LLM client's MCP config:
{
"mcpServers": {
"k8s-devops": {
"command": "uv",
"args": ["run", "python", "/ABSOLUTE/PATH/TO/src/mcp/k8s_server.py"]
}
}
}Local Development
just lint # ruff check + basedpyright
just test # run tests
just dev # LangGraph Studio (visual graph debugger)Acknowledgments
Built with LangGraph for agent orchestration, Hatchet for durable execution, and the Model Context Protocol for the tool interface. Kubernetes cluster interactions use the Kubernetes Python client.
License
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/swang62/hatchet-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server