Wire n8n into
every AI agent
through one socket.
n8n-mcp gives Claude, ChatGPT, Cursor and any MCP client a secure bridge to your self-hosted n8n. Agents inspect, build, validate and run workflows — through a single stable endpoint, while credentials never leave the server.
Built for teams that want AI-assisted workflow ops without handing every client direct access to n8n.
/ 01
What is n8n-mcp?
n8n-mcp is a hosted Model Context Protocol gateway for teams that run self-hosted n8n. It gives AI clients such as Claude, ChatGPT, Cursor, Windsurf, VS Code and Zed a stable MCP endpoint for workflow operations. Instead of giving every AI client direct n8n access, users connect an n8n instance once, store the n8n API key in the gateway, and authenticate clients with a platform API key. AI agents can then list workflows, inspect workflow details, create or update automations, validate workflow structure, execute workflows and review execution history. The gateway is designed for automation teams that want AI-assisted workflow operations while keeping credentials, tenant routing, rate limits and outbound request protection in one server-side boundary.
/ 02
The toolkit it exposes
A practical workflow toolkit instead of a generic HTTP prompt — each MCP call maps to a real n8n API operation.
- 01List and inspect n8n workflows
- 02Create and update automations
- 03Validate workflow structure
- 04Execute workflows from AI clients
- 05Review execution history
- 06Import workflow templates
/ 03
How it protects your n8n API keys
Authentication and outbound request controls stay server-side. AI clients use a platform API key while n8n credentials stay encrypted, scoped to the owning user, and checked before any request leaves the gateway.
Encrypted credentials
n8n API keys stay encrypted at rest and are never sent back to AI clients.
Protected outbound calls
SSRF checks block private networks and cloud metadata targets before n8n requests run.
Per-user API keys
Platform keys can be rotated and revoked without touching the n8n instance itself.
/ 04
Who it's for
Keep n8n as the automation system of record while AI clients help operators explore, generate and test workflow changes.
Workflow operations
Inspect, create, update, validate and execute workflows through MCP tools.
Faster client setup
Connect AI clients to one gateway URL instead of rebuilding custom n8n integrations.
/ 05
Frequently asked questions
What is n8n-mcp?
n8n-mcp is a hosted Model Context Protocol gateway for connecting self-hosted n8n workflows to AI clients.
Do I need to expose my n8n API key to AI clients?
No. n8n API keys are stored by the gateway and encrypted at rest; AI clients authenticate with a platform API key.
Which AI clients are supported?
Any MCP-compatible client can connect, including Claude, ChatGPT, Cursor, Windsurf, VS Code and Zed.
How is n8n-mcp different from a local MCP server?
A local MCP server runs beside one client, while n8n-mcp provides a hosted gateway URL, per-user authentication, encrypted n8n credential storage and centralized request controls.