MCP Server Guide

n8n MCP Server: Connect AI Agents to Workflows Safely

Use n8n’s built-in MCP features in both directions: publish selected workflows as agent tools and let n8n agents call external MCP servers.

The short answer

n8n officially documents MCP support, including an instance-level MCP server, the MCP Server Trigger, and the MCP Client Tool. These solve different connection patterns.

What is the n8n MCP server?

When n8n acts as an MCP server, an external agent can discover and run workflows that you intentionally expose. This is useful for wrapping multi-step automations—CRM updates, approvals, notifications, and data transforms—behind a small, typed tool interface.

In the opposite direction, n8n’s MCP Client Tool lets an AI Agent node call tools offered by an external MCP server. Choose the direction based on who orchestrates the task: your chat agent, or an n8n workflow.

What you should know before connecting it

Instance-level server

n8n documents an instance-level MCP server with setup instructions and a tools reference. It is the centralized option for exposing eligible n8n capabilities to compatible clients.

MCP Server Trigger

The trigger is the workflow-level pattern: define the workflow interface and expose a deliberate automation as an MCP tool instead of publishing generic n8n access.

MCP Client Tool

Use this cluster tool under an n8n AI Agent when the workflow itself needs to discover and call tools from another MCP server.

Setup plan

Choose the connection direction — Decide whether an external agent should invoke n8n or an n8n agent should invoke an external server.
Design a narrow workflow contract — Use typed, validated inputs and return concise structured outputs; do not expose an open-ended execute-anything workflow.
Store credentials in n8n — Keep service secrets in n8n credentials, not in tool descriptions, prompts, or client configuration.
Add approval and idempotency — Pause before high-impact actions and give retried tool calls an idempotency key so they do not duplicate work.
Activate and observe — Test with sample calls, inspect executions, run n8n’s security audit, and alert on repeated failures or unusual volume.

Useful agent workflows

Approved business actions

Turn “prepare and send this campaign” into a workflow that validates fields, requests approval, sends once, and reports the execution URL.

Cross-app orchestration

Expose one tool that coordinates several n8n integrations while keeping each vendor credential inside n8n.

External tool enrichment

Let an n8n AI Agent call a research or database MCP server, then continue through deterministic workflow nodes.

Security checklist

Expose specific workflows, never unrestricted workflow or credential administration.
Validate every input and reject unexpected fields or oversized payloads.
Use n8n credentials and restrict which projects can access them.
Require approval for messages, payments, deletes, publishing, and account changes.
Make workflows idempotent because clients can retry tool calls.
Run the n8n security audit and review execution history regularly.

Treat every MCP tool as an API capability, not as a harmless chat feature. Start read-only, test in a non-production account, and require human approval for changes.

Frequently asked questions

Does n8n have an official MCP server?

Yes. n8n documents an instance-level MCP server and workflow-level MCP Server Trigger functionality.

What is the MCP Client Tool for?

It lets an n8n AI Agent connect to and call tools from an external MCP server.

Should I expose every workflow?

No. Publish only workflows designed as stable, validated tools, with approvals and idempotency for consequential actions.

Primary documentation

Verify current endpoints, permissions, and preview limitations in the official n8n MCP server documentation before production rollout. Vendor capabilities can change faster than third-party guides.

Run an MCP-ready AI agent without server maintenance

OpenClaw Launch handles the agent host, updates, and uptime so you can focus on safe tool design.

Configure your agent