MCP Supabase agent – manage your database with AI
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 11 nodes and runs when an MCP client calls one of its tools (plus 1 other trigger). Along the way it connects Supabase, OpenAI Chat Model and MCP Client.
How it runs
Trigger: When an MCP client calls one of its tools (plus 1 other trigger).
- AI Agent: runs an AI agent, with model: Model Chat; 1 tool (MCP Supabase); 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)
- Supabase Tool
n8n-nodes-base.supabaseTool - MCP Server Trigger
@n8n/n8n-nodes-langchain.mcpTrigger - AI Agent
@n8n/n8n-nodes-langchain.agent - Chat Trigger
@n8n/n8n-nodes-langchain.chatTrigger - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Simple Memory
@n8n/n8n-nodes-langchain.memoryBufferWindow - MCP Client Tool
@n8n/n8n-nodes-langchain.mcpClientTool
From the author
Hi, I’m Amanda 🌷 This workflow was built with love to help you manage your Supabase database using natural language, powered by the MCP (Multi-Channel Protocol) AI Agent on n8n. With just a message like “update the status to active where city is New York”,…