Hatchet MCP
Enables running durable, traceable AI agents via LangGraph through a universal MCP interface, integrating with Hatchet for orchestration, logging, and retries. Provides tools for knowledge management (ingestion, RAG) and Kubernetes operations (diagnosis, auto-fix).
README
Personal Agentic AI - Hatchet MCP
This is my personal local AI agent setup that can run durable and fully traceable agents (with LangGraph), utilizing a universal MCP interface. The MCP directly talks to a Hatchet server, which then triggers my custom tasks/workflows, making it trivial to hook up any local LLM chat interface (LMStudio, OpenCode, Claude Code, Open WebUI, etc) and run custom AI workflows. This has the added benefit of full logging, custom loops, orchestration, retries, tracing, and all other goodies provided by Hatchet.
Quick start
uv sync # install deps (this is only required for local dev)
just docker-start # start Hatchet orchestration server in Docker (localhost:8888)
just worker # start local worker (runs LangGraph locally, no Docker)
just dev # run LangGraph Studio to visualize and debug graphs
Currently available agents
| Agent | How to trigger |
|---|---|
| Knowledge Management | ingests files, extracts text, vector embeddings, deep inspection with LLM, RAG retrieval, file indexing |
| K8s DevOps Troubleshooter | full LangGraph agent loop: check cluster, diagnose with LLM, auto-fix via kubectl, verify, self-correct |
| K8s Direct Tools | individual k8s ops (check_pods, get_logs, describe_pod, run_kubectl, etc.) routed through Hatchet |
Architecture
LLM client (opencode, claude, etc.)
│
├── MCP Server (kb_server.py) ◄── stdio
│ ├── ingest_document ──▶ event push to Worker
│ ├── search, get_document
│ ├── list_documents, search_documents
│ └── delete_document
│
└── MCP Server (k8s_server.py) ◄── stdio
├── check_pods, get_logs, describe_pod
├── get_events, debug_pod, run_kubectl
├── get_deployments, get_statefulsets, get_daemonsets
├── get_services, get_ingresses, get_configmaps
├── get_secrets, exec_in_pod
└── run_devops_agent ──▶ event push to Worker
┌──────────────────────────────┐
│ Hatchet Worker │
│ ├─ knowledge_ingestion │
│ ├─ k8s_devops │
│ └─ k8s_tool │
│ All runs visible in dashboard │
└──────────────────────────────┘
MCP config
Register the servers in your LLM client:
{
"mcpServers": {
"knowledge-base": {
"command": "uv",
"args": ["run", "python", "src/mcp/kb_server.py"]
},
"k8s-devops": {
"command": "uv",
"args": ["run", "python", "src/mcp/k8s_server.py"]
}
}
}
Adding agents and MCP tools
- Create
src/langgraph/agents/<name>.pywithStateGraph(...)and agraphvariable - Create
src/hatchet_worker/workflows/<name>.py— wraps the graph in a Hatchet task - Register it in
src/hatchet_worker/worker.pywith anon_events=[...]trigger - (Optional) Create
src/mcp/<name>_server.pywithFastMCPand@server.tool()functions
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。