mcp-n8n-builder and mcp-n8n-workflow-builder
These are **competitors** offering similar programmatic workflow automation capabilities—both provide MCP servers for AI-assisted n8n workflow creation and management, with the key difference being that B emphasizes natural language interfaces for Claude/Cursor while A focuses on direct programmatic control through a comprehensive tool API.
About mcp-n8n-builder
spences10/mcp-n8n-builder
🪄 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 n8n's REST API.
Implements the Model Context Protocol (MCP) standard with Zod-based schema validation and node-type verification against n8n's available nodes to prevent workflow errors before creation. Provides configurable output verbosity modes and caching to optimize token consumption, critical given that n8n workflows are complex nested JSON structures that can easily exceed LLM context windows. Exposes MCP tools and resources for full CRUD operations, execution tracking, and workflow activation/deactivation across n8n instances via REST API.
About mcp-n8n-workflow-builder
salacoste/mcp-n8n-workflow-builder
AI-powered n8n workflow automation through natural language. MCP server enabling Claude AI & Cursor IDE to create, manage, and monitor workflows via Model Context Protocol. Multi-instance support, 17 tools, comprehensive docs. Build workflows conversationally without manual JSON editing.
Implements an MCP server using stdio transport that connects Claude and Cursor IDE directly to n8n instances via REST API, supporting multi-environment routing through configuration files for dev/staging/production separation. The 17 tools span complete workflow lifecycle management—creation, execution monitoring, tag organization, and credential handling—with built-in conversation patterns that translate natural language descriptions into executable n8n JSON without exposing API keys or sensitive configuration in logs.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work