N8n Builder MCP Server

Workflow construction starts with discovering the node types available in the connected n8n instance. mcp-n8n-builder lets an assistant assemble nodes and connections into a workflow, retrieve its full structure, and submit revisions. Updates require the complete workflow definition rather than a partial patch. Node validation checks types against the instance and suggests similar alternatives when a type is invalid. Existing workflows can be located using name, tag, or active-state filters, then activated, deactivated, or permanently deleted. Activation requires an automatic trigger; a workflow containing only manual triggers cannot be activated.

Execution histories can be filtered by workflow or status before inspecting an individual run's timing, outcome, and optional step data. These records support investigating failures and following transformations between nodes. Large workflow definitions can consume substantial model context, so output is concise by default, with fuller responses available through verbosity settings. Workflow listings retain essential fields, while error messages include relevant guidance rather than the entire composition guide. Configuration supplies the n8n API address and authentication key through the MCP client.