MCP Client Tool – When to Use It Instead of Native Tools in n8n
If you’ve read our overview of how MCP works in n8n, you know there are four ways n8n interacts with MCP. The MCP Client Tool is the one that [...]
When is an AI Agent Internal or External to n8n?
The Distinction n8n Doesn’t Name (But You Need to Know) Understanding how AI agents relate to n8n changes which tools you reach for. n8n doesn’t use the terms [...]
MCP Client Node – Deterministic MCP Without AI Agents in n8n
The MCP Client node — n8n recently renamed it from the “MCP node” — is the missing piece that completes the pattern. While the MCP Server Trigger receives incoming [...]
MCP Server Trigger – Workflow-Level MCP Endpoints in n8n
The MCP Server Trigger is a workflow-level entry point. You create a dedicated workflow, drop in the MCP Server Trigger node, and attach tool nodes to it. Each trigger [...]
Instance-Level MCP – The Agent Gateway for Viewing, Triggering, and Building Workflows in n8n
Instance-Level MCP — the feature formerly labeled “MCP Access” — is n8n’s instance-wide gateway. It turns your entire n8n deployment into a single MCP server that external AI clients [...]
How MCP Works in n8n: Instance-Level MCP, Server Trigger, Client, and Client Tool Explained
MCP — Model Context Protocol — gives n8n three distinct ways to connect AI agents to external tools. Here's how MCP Access, MCP Server Trigger, and MCP Client Tool work, when to use each, and how they fit together.