Conversational Kubernetes management with GPT-4o and MCP integration
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: AI Agent v1 (old agent modes). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 27 nodes and runs when a chat message arrives (plus 2 other triggers). Along the way it connects OpenAI Chat Model, MCP Client and Mcp (community).
How it runs
Trigger: When a chat message arrives (plus 2 other triggers).
- AI Agent: runs an AI agent, with model: OpenAI Chat Model; 2 tools (Helm MCP Client, Kubernetes MCP Client); memory: Simple Memory
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- AI Agent v1 (old agent modes) in AI Agent (v1.8): replace with Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| AI Agent v1 (old agent modes) AI Agent (v1.8) | Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent. |
Nodes used (7)
- Chat Trigger
@n8n/n8n-nodes-langchain.chatTrigger - AI Agent
@n8n/n8n-nodes-langchain.agent - Mcp Client Tool
n8n-nodes-mcp.mcpClientTool - MCP Server Trigger
@n8n/n8n-nodes-langchain.mcpTrigger - Simple Memory
@n8n/n8n-nodes-langchain.memoryBufferWindow - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - MCP Client Tool
@n8n/n8n-nodes-langchain.mcpClientTool
From the author
This n8n workflow template uses community nodes and is only compatible with the self-hosted version of n8n. Conversational Kubernetes Management with GPT-4o and MCP Integration This workflow enables you to manage Kubernetes clusters conversationally using…