MCP MCP Server

🪄 MCP server for programmatic creation and management of n8n workflows. Enables AI assistants to build, modify, and manage workflows without direct

Local serverstdio

What is the MCP MCP server?

🪄 MCP server for programmatic creation and management of n8n workflows. Enables AI assistants to build, modify, and manage workflows without direct user intervention through a comprehensive set of tools and resources for interacting with. That is what the mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

  • 🔄 Workflow Management: Create, read, update, delete, activate,
  • 📊 Execution Management: List and retrieve workflow execution
  • Schema Validation: Comprehensive validation with Zod for both
  • 🔍 Node Validation: Validates node types against n8n's available
  • 🤔 Smart Suggestions: Provides suggestions for similar node
  • 🛠️ Error Handling: Detailed error messages for troubleshooting

The tools it exposes

The server publishes 2 tools. What each one is for:

  • Setup — The Setup tool exposed by this server
  • Publishing — The project uses changesets for version management. To publish:

What it needs from you

Configuration is passed through the environment: N8N_HOST, N8N_API_KEY, OUTPUT_VERBOSITY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

mcp-n8n-builder on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

How it compares

This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — Setup, Publishing — is a fair guide to whether it matches your workflow. It is maintained by spences10; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
SetupThe Setup tool exposed by this server.
PublishingThe project uses changesets for version management. To publish:

How to install the MCP MCP server

{
	"mcpServers": {
		"n8n-workflow-builder": {
			"command": "npx",
			"args": ["-y", "mcp-n8n-builder"],
			"env": {
				"N8N_HOST": "http://localhost:5678/api/v1",
				"N8N_API_KEY": "your-n8n-api-key",
				"OUTPUT_VERBOSITY": "concise" // Options: 'concise' or 'full'
			}
		}
	}
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
N8N_HOSTEndpoint or connection string the server talks to.Optional
N8N_API_KEYCredential the server authenticates with.Yes
OUTPUT_VERBOSITYConfiguration value read at startup.Optional

Example prompts to try

  • Use MCP to Setup.
  • Use MCP to Publishing.

Frequently asked questions

Set `N8N_HOST` (URL of n8n API, default `http://localhost:5678/api/v1`) and `N8N_API_KEY` in environment variables. Optionally set `OUTPUT_VERBOSITY` to `concise` (default) or `full`.