MCP Client Tool – When to Use It Instead of Native Tools in n8n
Pardon our dust, this blog post is a work in progress. If you've read our overview of how MCP works in n8n, you know there are four ways [...]
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 Node – Deterministic MCP Without AI Agents in n8n
The MCP Node is the missing piece that completes the pattern. While the MCP Server Trigger receives incoming calls from external AIs, the MCP Node lets you call [...]
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 [...]
Instance‑Level MCP Access – The agent gateway for triggering and viewing workflows in n8n
MCP Access is n8n's instance-level MCP gateway. It turns your entire n8n deployment into a single MCP server that external AI clients can connect to via OAuth. Instead [...]
How MCP Works in n8n: Access, Trigger, Node, and 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.