n8n + MCP Servers: Connect Any Tool to Your Agents
Use Model Context Protocol servers as n8n tools. Bring filesystems, databases, and SaaS apps to any AI agent.
Key takeaways
- Expose n8n sub-workflows as MCP tools to Claude Desktop, Cursor, and any MCP client.
- Consume external MCP servers (Filesystem, GitHub, Postgres) from your n8n Agent.
- Auth every MCP endpoint — they are tool-calling APIs in disguise.
- Version your tool schemas; clients cache them.
Model Context Protocol (MCP) is the open standard that lets AI agents call tools regardless of who built them. n8n's MCP Server Trigger and MCP Client nodes turn your n8n into both a producer and consumer of MCP tools. This unlocks a marketplace of tools your agent can use immediately.
What is MCP?
Model Context Protocol, introduced by Anthropic in late 2024, is a JSON-RPC standard for LLMs to discover and call tools across processes. Think 'OpenAPI for AI agents'. n8n adopted it in 2025 and shipped first-class nodes.
n8n as MCP server
Drop an MCP Server Trigger node. Each Tool Workflow you attach becomes a callable tool with auto-generated JSON schema. Claude Desktop, Cursor, or any MCP client connects via SSE and gets your tools.
n8n as MCP client
In an Agent workflow, add an MCP Client tool pointing at any MCP server URL. The agent now has all that server's tools available — Filesystem, GitHub, Brave Search, Postgres, and a growing list.
Security
MCP servers are unauthenticated by default. Always front them with a header-auth check or run them inside a private network. Tool calls execute real actions.
Frequently asked questions
- Is MCP an open standard?
- Yes, Anthropic open-sourced the spec and reference implementations.
- Can n8n consume an OpenAPI spec as MCP tools?
- Indirectly — wrap the OpenAPI in an MCP server, or use n8n's native HTTP tool nodes for the agent.