workflow-orchestration-via-mcp-protocol, workflow-discovery-and-introspection, execution-status-polling-and-monitoring, parameter-binding-and-context-injection, error-handling-and-execution-failure-reporting, workflow-execution-history-retrieval, multi-workflow-orchestration-and-chaining, credential-and-secret-management-abstraction

n8n

MCP ServerFree

MCP server: n8n

Open Source

/ 100

8 capabilities

Capabilities8 decomposed

workflow-orchestration-via-mcp-protocol

Medium confidence

Exposes n8n's workflow execution engine through the Model Context Protocol, allowing LLM agents to trigger, monitor, and manage automation workflows as remote procedure calls. Uses MCP's standardized request/response format to abstract n8n's REST API, enabling stateless workflow invocation with parameter binding and execution state tracking without direct HTTP knowledge.

Solves for

I want my AI agent to trigger complex multi-step automations based on LLM decisionsI need to invoke n8n workflows from Claude or other MCP-compatible LLMs without writing custom API clientsI want to chain LLM reasoning with deterministic workflow execution in a single agent loop

Best for

AI agent developers building agentic workflows that need deterministic automation

teams integrating LLMs with existing n8n automation infrastructure

builders prototyping AI-driven business process automation

Requires

n8n instance running (self-hosted or cloud) with API access enabled

MCP-compatible LLM client (Claude, or custom MCP client implementation)

n8n API credentials (API key or OAuth token)

Limitations

MCP protocol adds ~100-300ms latency per workflow invocation due to serialization overhead

no built-in workflow versioning or rollback through MCP — must manage via n8n directly

workflow execution context (variables, secrets) must be pre-configured in n8n; cannot be dynamically injected via MCP

What makes it unique

Bridges n8n's low-code workflow engine with LLM agents via MCP protocol, eliminating the need for custom HTTP client code and enabling declarative workflow invocation as a first-class LLM capability. Uses MCP's resource and tool abstractions to expose workflows as callable functions with schema-based parameter validation.

vs alternatives

Unlike direct n8n API integration, MCP abstraction provides standardized tool discovery and invocation across any MCP-compatible LLM (Claude, Llama, etc.) without rewriting client code per LLM provider.

workflow-discovery-and-introspection

Medium confidence

Queries n8n's workflow registry to enumerate available workflows, retrieve workflow definitions, and expose workflow input/output schemas through MCP's resource listing and metadata endpoints. Implements schema extraction from n8n's internal workflow graph representation, allowing LLM agents to discover executable workflows and understand their expected parameters without manual documentation.

Solves for

I want my LLM agent to discover what workflows are available in our n8n instanceI need to expose workflow input schemas so the agent knows what parameters to passI want to dynamically list workflows by tag or category for conditional agent routing

Best for

multi-workflow environments where agents need dynamic workflow selection

teams with large n8n workflow libraries requiring programmatic discovery

builders implementing agent-driven workflow routing based on user intent

Requires

n8n instance with API access and authentication

sufficient API permissions to list workflows and read workflow definitions

MCP client with resource listing capability

Limitations

schema extraction only covers explicitly defined workflow inputs — computed or dynamic fields may not be discoverable

no filtering by workflow status (active/inactive) — all workflows returned regardless of deployment state

workflow descriptions must be manually maintained in n8n; no auto-generation from workflow logic

What makes it unique

Exposes n8n's workflow graph as queryable MCP resources with automatic schema extraction, enabling LLM agents to self-discover available automations and their parameter requirements without hardcoded workflow lists or manual API documentation.

vs alternatives

Provides dynamic workflow discovery that adapts to n8n instance changes in real-time, unlike static workflow registries or hardcoded agent tool definitions that require manual updates.

execution-status-polling-and-monitoring

Medium confidence

Implements polling-based execution monitoring through MCP, allowing agents to query workflow execution status, retrieve execution results, and track long-running workflows without blocking. Uses n8n's execution history API to fetch status updates, with configurable polling intervals and timeout handling to prevent agent deadlock on slow workflows.

Solves for

I want my agent to wait for a workflow to complete and retrieve its resultsI need to check if a long-running workflow is still executing or has failedI want to implement retry logic if a workflow execution fails

Best for

agents orchestrating multi-step workflows with dependencies

systems requiring execution result retrieval for downstream processing

builders implementing fault-tolerant automation chains

Requires

n8n instance with execution history API enabled

execution ID from a prior workflow invocation

polling timeout configuration (recommended 30-300 seconds)

Limitations

polling-based approach adds latency — no real-time execution webhooks through MCP

no built-in exponential backoff — polling interval must be manually configured

execution history retention depends on n8n configuration — old executions may be pruned

What makes it unique

Provides MCP-native execution monitoring without requiring agents to implement custom polling logic, abstracting n8n's execution API behind a simple status-check interface with built-in timeout handling.

vs alternatives

Simpler than webhook-based monitoring for MCP clients that lack persistent server infrastructure, and more reliable than fire-and-forget execution for workflows requiring result retrieval.

parameter-binding-and-context-injection

Medium confidence

Enables dynamic parameter passing to workflows through MCP tool invocation, mapping LLM-generated parameters to n8n workflow input variables. Implements type coercion and validation against workflow input schemas, allowing agents to pass structured data (JSON objects, arrays) and primitive types directly into workflow execution contexts without manual serialization.

Solves for

I want to pass data extracted by the LLM (like user input or API responses) into n8n workflowsI need to dynamically set workflow variables based on agent reasoningI want type-safe parameter passing with validation before workflow execution

Best for

agents that need to pass LLM-generated data into deterministic workflows

multi-step automation chains where LLM output feeds into workflow input

builders implementing data transformation pipelines with LLM + n8n

Requires

workflow input schema defined in n8n

parameter values matching expected types (string, number, boolean, object, array)

MCP client capable of passing structured JSON data

Limitations

parameter validation only covers schema-defined inputs — custom validation logic in n8n is not enforced through MCP

no support for file uploads or binary data — only JSON-serializable types

secrets and sensitive data passed as parameters are logged in n8n execution history — no automatic masking

What makes it unique

Abstracts n8n's workflow variable system through MCP's tool invocation interface, enabling agents to pass parameters declaratively without understanding n8n's internal variable scoping or type system.

vs alternatives

Provides type-safe parameter binding with schema validation, unlike raw API calls that require manual type coercion and error handling in agent code.

error-handling-and-execution-failure-reporting

Medium confidence

Captures workflow execution errors and exposes them through MCP as structured error objects, including error type, message, and failure context (which node failed, error code). Allows agents to distinguish between transient failures (retry-able) and permanent errors (configuration issues) based on error classification from n8n's execution logs.

Solves for

I want my agent to detect when a workflow fails and understand whyI need to implement conditional retry logic based on error typeI want to log workflow failures for debugging and monitoring

Best for

agents implementing fault-tolerant automation with retry strategies

systems requiring detailed error reporting for observability

builders debugging complex multi-workflow orchestrations

Requires

n8n instance with error logging enabled

execution ID from a failed workflow

MCP client capable of parsing structured error responses

Limitations

error classification depends on n8n node implementations — custom nodes may not provide structured error data

no stack traces or detailed debugging information — only high-level error messages

error context limited to final failure point — intermediate node failures not exposed

What makes it unique

Structures n8n execution errors as MCP-compatible error objects with classification and context, enabling agents to implement intelligent error handling without parsing unstructured error logs.

vs alternatives

Provides structured error reporting that enables programmatic error handling in agents, unlike raw API responses that require manual error parsing and classification.

workflow-execution-history-retrieval

Medium confidence

Queries n8n's execution history database through MCP to retrieve past workflow executions, including execution timestamps, status, duration, and output data. Implements pagination and filtering by date range or status, allowing agents to audit workflow behavior, retrieve historical results, or implement idempotency checks based on prior executions.

Solves for

I want to check if a workflow has already been executed with the same parameters (idempotency)I need to retrieve historical execution data for reporting or analysisI want to audit which workflows have failed in the last 24 hours

Best for

agents implementing idempotent workflow execution

systems requiring execution audit trails and compliance logging

builders analyzing workflow performance and failure patterns

Requires

n8n instance with execution history API enabled

sufficient API permissions to read execution history

optional: date range or status filters

Limitations

execution history retention depends on n8n configuration — old executions may be automatically purged

no full-text search of execution logs — filtering limited to metadata (status, date, workflow ID)

pagination may be slow for large execution histories (millions of records)

What makes it unique

Exposes n8n's execution history as queryable MCP resources with filtering and pagination, enabling agents to implement idempotency checks and audit workflows without direct database access.

vs alternatives

Provides agent-friendly execution history queries that abstract n8n's internal database schema, unlike raw SQL queries that require knowledge of n8n's data model.

multi-workflow-orchestration-and-chaining

Medium confidence

Enables sequential or conditional execution of multiple n8n workflows through MCP, allowing agents to chain workflow outputs as inputs to subsequent workflows. Implements execution dependency tracking and conditional branching based on prior workflow results, enabling complex multi-step automation scenarios without manual workflow composition in n8n.

Solves for

I want to execute workflow A, then pass its output to workflow BI need to conditionally execute workflow C only if workflow B succeedsI want to orchestrate a multi-step process where each step depends on the previous result

Best for

agents implementing complex multi-step business processes

systems requiring conditional workflow routing based on intermediate results

builders orchestrating data pipelines with multiple transformation stages

Requires

multiple n8n workflows with compatible input/output schemas

MCP client capable of sequential tool invocation

agent logic to manage execution order and data flow

Limitations

no built-in transaction semantics — partial failures in multi-workflow chains require manual rollback logic

execution order must be explicitly managed by agent — no automatic dependency resolution

no distributed tracing across workflows — debugging multi-workflow chains requires manual log correlation

What makes it unique

Enables agent-driven workflow orchestration through MCP, allowing LLM reasoning to determine workflow execution order and data flow, rather than hardcoding dependencies in n8n.

vs alternatives

Provides dynamic workflow chaining based on LLM decisions, unlike static n8n workflows that require manual composition and cannot adapt to runtime conditions discovered by agents.

credential-and-secret-management-abstraction

Medium confidence

Abstracts n8n's credential storage system through MCP, allowing agents to reference pre-configured credentials (API keys, database passwords, OAuth tokens) by name without exposing secrets in agent prompts or logs. Uses n8n's credential encryption and access control to ensure secrets remain secure while enabling workflows to access external services.

Solves for

I want workflows to use stored credentials without the agent knowing the actual secret valuesI need to ensure API keys and passwords are never exposed in agent logs or promptsI want to rotate credentials in n8n without updating agent code

Best for

agents executing workflows that require external API access

systems with strict security requirements (no secrets in logs)

teams managing multiple credentials across workflows

Requires

credentials pre-configured in n8n instance

credential names known to agent or discoverable through workflow introspection

n8n user with permission to use referenced credentials

Limitations

agents cannot create or rotate credentials through MCP — must be managed in n8n UI

no fine-grained credential access control — agents can reference any credential available to their n8n user

credential names must be known in advance — no discovery of available credentials through MCP

What makes it unique

Provides secure credential abstraction through MCP, ensuring agents never handle raw secrets while enabling workflows to access external services with pre-configured credentials.

vs alternatives

Eliminates the need to pass secrets through agent prompts or logs, unlike direct API integration where agents must manage credentials directly.

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with n8n, ranked by overlap. Discovered automatically through the match graph.

MCP Server21

@transcend-io/mcp-server-workflows

Transcend MCP Server — Workflows tools.

workflow execution status tracking and result streamingmcp-native workflow definition and execution

2 shared capabilities

Framework28

@mcpilotx/intentorch

Intent-Driven MCP Orchestration Toolkit - Transform natural language into executable workflows with AI-powered intent parsing and MCP tool orchestration

intent-to-mcp-workflow-orchestrationworkflow-logging-and-observability

2 shared capabilities

MCP Server26

@voltagent/mcp-server

VoltAgent MCP server implementation for exposing agents, tools, and workflows via the Model Context Protocol.

workflow orchestration and execution exposure via mcp

1 shared capability

MCP Server34

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.

workflow-execution-monitoring-and-logging

1 shared capability

MCP Server23

teste

MCP server: teste

dynamic api orchestration

1 shared capability

MCP Server43

n8n-mcp

Integration between n8n workflow automation and Model Context Protocol (MCP)

workflow execution result streaming and status tracking

1 shared capability

Best For

✓AI agent developers building agentic workflows that need deterministic automation
✓teams integrating LLMs with existing n8n automation infrastructure
✓builders prototyping AI-driven business process automation
✓multi-workflow environments where agents need dynamic workflow selection
✓teams with large n8n workflow libraries requiring programmatic discovery
✓builders implementing agent-driven workflow routing based on user intent
✓agents orchestrating multi-step workflows with dependencies
✓systems requiring execution result retrieval for downstream processing

Known Limitations

⚠MCP protocol adds ~100-300ms latency per workflow invocation due to serialization overhead
⚠no built-in workflow versioning or rollback through MCP — must manage via n8n directly
⚠workflow execution context (variables, secrets) must be pre-configured in n8n; cannot be dynamically injected via MCP
⚠no real-time streaming of workflow execution logs — only final execution status available
⚠schema extraction only covers explicitly defined workflow inputs — computed or dynamic fields may not be discoverable
⚠no filtering by workflow status (active/inactive) — all workflows returned regardless of deployment state

Requirements

n8n instance running (self-hosted or cloud) with API access enabledMCP-compatible LLM client (Claude, or custom MCP client implementation)n8n API credentials (API key or OAuth token)network connectivity between MCP client and n8n instancen8n instance with API access and authenticationsufficient API permissions to list workflows and read workflow definitionsMCP client with resource listing capabilityn8n instance with execution history API enabled

Input / Output

Accepts: workflow ID or name (string), workflow input parameters (JSON object), execution options (async/sync flag, timeout), optional filter parameters (workflow name, tag, status), execution ID (string), polling interval (milliseconds, optional), timeout duration (seconds, optional), primitive types (string, number, boolean), nested objects and arrays, workflow ID (string), date range (start/end timestamps, optional), status filter (running/success/error, optional), pagination parameters (limit, offset), workflow execution sequence (array of workflow IDs), conditional logic (if-then rules based on prior results), data transformation rules (mapping prior output to next input), credential name (string)

Produces: execution ID (string), execution status (running/success/error), workflow output data (JSON object), execution metadata (duration, timestamp), workflow list (array of workflow metadata), workflow definition (JSON schema with inputs/outputs), workflow tags and categories (string array), execution status (running/success/error/timeout), execution result data (JSON object), error details (string, if failed), execution duration (milliseconds), parameter validation result (success/error), execution ID with parameters bound, error type (string, e.g., 'network_error', 'validation_error', 'timeout'), error message (string), failing node name (string), error code (string or number), error context (JSON object with additional details), execution list (array of execution records), execution metadata (timestamp, duration, status), execution output data (JSON object), pagination info (total count, has_more), final workflow output (JSON object), execution chain metadata (all execution IDs, durations), intermediate results (optional, for debugging), credential reference (opaque token for workflow use), credential type (string, e.g., 'api_key', 'oauth2', 'database')

UnfragileRank

Adoption5%(25% weight)

Quality16%(25% weight)

Ecosystem49%(15% weight)

Match Graph25%(30% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

8 capabilities

Visit n8n→

About

MCP server: n8n

Alternatives to n8n

Supabase69Platform

Search the Supabase docs for up-to-date guidance and troubleshoot errors quickly. Manage organizations, projects, databases, and Edge Functions, including migrations, SQL, logs, advisors, keys, and type generation, in one flow. Create and manage development branches to iterate safely, confirm costs

Compare →

Tavily MCP Server62MCP Server

AI-optimized web search and content extraction via Tavily MCP.

Compare →

MongoDB MCP Server62MCP Server

Query and manage MongoDB databases and collections via MCP.

Compare →

Firecrawl MCP Server62MCP Server

Scrape websites and extract structured data via Firecrawl MCP.

Compare →

Are you the builder of n8n?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

smithery

Looking for something else?

Search →

Capabilities8 decomposed

workflow-orchestration-via-mcp-protocol

Medium confidence

Solves for

Best for

AI agent developers building agentic workflows that need deterministic automation

teams integrating LLMs with existing n8n automation infrastructure

builders prototyping AI-driven business process automation

Requires

n8n instance running (self-hosted or cloud) with API access enabled

MCP-compatible LLM client (Claude, or custom MCP client implementation)

n8n API credentials (API key or OAuth token)

Limitations

MCP protocol adds ~100-300ms latency per workflow invocation due to serialization overhead

no built-in workflow versioning or rollback through MCP — must manage via n8n directly

workflow execution context (variables, secrets) must be pre-configured in n8n; cannot be dynamically injected via MCP

What makes it unique

vs alternatives

workflow-discovery-and-introspection

Medium confidence

Solves for

Best for

multi-workflow environments where agents need dynamic workflow selection

teams with large n8n workflow libraries requiring programmatic discovery

builders implementing agent-driven workflow routing based on user intent

Requires

n8n instance with API access and authentication

sufficient API permissions to list workflows and read workflow definitions

MCP client with resource listing capability

Limitations

schema extraction only covers explicitly defined workflow inputs — computed or dynamic fields may not be discoverable

no filtering by workflow status (active/inactive) — all workflows returned regardless of deployment state

workflow descriptions must be manually maintained in n8n; no auto-generation from workflow logic

What makes it unique

vs alternatives

Provides dynamic workflow discovery that adapts to n8n instance changes in real-time, unlike static workflow registries or hardcoded agent tool definitions that require manual updates.

execution-status-polling-and-monitoring

Medium confidence

Solves for

Best for

agents orchestrating multi-step workflows with dependencies

systems requiring execution result retrieval for downstream processing

builders implementing fault-tolerant automation chains

Requires

n8n instance with execution history API enabled

execution ID from a prior workflow invocation

polling timeout configuration (recommended 30-300 seconds)

Limitations

polling-based approach adds latency — no real-time execution webhooks through MCP

no built-in exponential backoff — polling interval must be manually configured

execution history retention depends on n8n configuration — old executions may be pruned

What makes it unique

vs alternatives

Simpler than webhook-based monitoring for MCP clients that lack persistent server infrastructure, and more reliable than fire-and-forget execution for workflows requiring result retrieval.

parameter-binding-and-context-injection

Medium confidence

Solves for

Best for

agents that need to pass LLM-generated data into deterministic workflows

multi-step automation chains where LLM output feeds into workflow input

builders implementing data transformation pipelines with LLM + n8n

Requires

workflow input schema defined in n8n

parameter values matching expected types (string, number, boolean, object, array)

MCP client capable of passing structured JSON data

Limitations

parameter validation only covers schema-defined inputs — custom validation logic in n8n is not enforced through MCP

no support for file uploads or binary data — only JSON-serializable types

secrets and sensitive data passed as parameters are logged in n8n execution history — no automatic masking

What makes it unique

vs alternatives

Provides type-safe parameter binding with schema validation, unlike raw API calls that require manual type coercion and error handling in agent code.

error-handling-and-execution-failure-reporting

Medium confidence

Solves for

I want my agent to detect when a workflow fails and understand whyI need to implement conditional retry logic based on error typeI want to log workflow failures for debugging and monitoring

Best for

agents implementing fault-tolerant automation with retry strategies

systems requiring detailed error reporting for observability

builders debugging complex multi-workflow orchestrations

Requires

n8n instance with error logging enabled

execution ID from a failed workflow

MCP client capable of parsing structured error responses

Limitations

error classification depends on n8n node implementations — custom nodes may not provide structured error data

no stack traces or detailed debugging information — only high-level error messages

error context limited to final failure point — intermediate node failures not exposed

What makes it unique

Structures n8n execution errors as MCP-compatible error objects with classification and context, enabling agents to implement intelligent error handling without parsing unstructured error logs.

vs alternatives

Provides structured error reporting that enables programmatic error handling in agents, unlike raw API responses that require manual error parsing and classification.

workflow-execution-history-retrieval

Medium confidence

Solves for

Best for

agents implementing idempotent workflow execution

systems requiring execution audit trails and compliance logging

builders analyzing workflow performance and failure patterns

Requires

n8n instance with execution history API enabled

sufficient API permissions to read execution history

optional: date range or status filters

Limitations

execution history retention depends on n8n configuration — old executions may be automatically purged

no full-text search of execution logs — filtering limited to metadata (status, date, workflow ID)

pagination may be slow for large execution histories (millions of records)

What makes it unique

Exposes n8n's execution history as queryable MCP resources with filtering and pagination, enabling agents to implement idempotency checks and audit workflows without direct database access.

vs alternatives

Provides agent-friendly execution history queries that abstract n8n's internal database schema, unlike raw SQL queries that require knowledge of n8n's data model.

multi-workflow-orchestration-and-chaining

Medium confidence

Solves for

Best for

agents implementing complex multi-step business processes

systems requiring conditional workflow routing based on intermediate results

builders orchestrating data pipelines with multiple transformation stages

Requires

multiple n8n workflows with compatible input/output schemas

MCP client capable of sequential tool invocation

agent logic to manage execution order and data flow

Limitations

no built-in transaction semantics — partial failures in multi-workflow chains require manual rollback logic

execution order must be explicitly managed by agent — no automatic dependency resolution

no distributed tracing across workflows — debugging multi-workflow chains requires manual log correlation

What makes it unique

Enables agent-driven workflow orchestration through MCP, allowing LLM reasoning to determine workflow execution order and data flow, rather than hardcoding dependencies in n8n.

vs alternatives

Provides dynamic workflow chaining based on LLM decisions, unlike static n8n workflows that require manual composition and cannot adapt to runtime conditions discovered by agents.

credential-and-secret-management-abstraction

Medium confidence

Solves for

Best for

agents executing workflows that require external API access

systems with strict security requirements (no secrets in logs)

teams managing multiple credentials across workflows

Requires

credentials pre-configured in n8n instance

credential names known to agent or discoverable through workflow introspection

n8n user with permission to use referenced credentials

Limitations

agents cannot create or rotate credentials through MCP — must be managed in n8n UI

no fine-grained credential access control — agents can reference any credential available to their n8n user

credential names must be known in advance — no discovery of available credentials through MCP

What makes it unique

Provides secure credential abstraction through MCP, ensuring agents never handle raw secrets while enabling workflows to access external services with pre-configured credentials.

vs alternatives

Eliminates the need to pass secrets through agent prompts or logs, unlike direct API integration where agents must manage credentials directly.

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to n8n

Supabase69Platform

Compare →

Tavily MCP Server62MCP Server

AI-optimized web search and content extraction via Tavily MCP.

Compare →

MongoDB MCP Server62MCP Server

Query and manage MongoDB databases and collections via MCP.

Compare →

Firecrawl MCP Server62MCP Server

Scrape websites and extract structured data via Firecrawl MCP.

Compare →

n8n

Capabilities8 decomposed

workflow-orchestration-via-mcp-protocol

workflow-discovery-and-introspection

execution-status-polling-and-monitoring

parameter-binding-and-context-injection

error-handling-and-execution-failure-reporting

workflow-execution-history-retrieval

multi-workflow-orchestration-and-chaining

credential-and-secret-management-abstraction

Related Artifactssharing capabilities

@transcend-io/mcp-server-workflows

@mcpilotx/intentorch

@voltagent/mcp-server

mcp-n8n-workflow-builder

teste

n8n-mcp

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

About

Categories

Alternatives to n8n

Are you the builder of n8n?

Get the weekly brief

Data Sources

n8n

Capabilities8 decomposed

workflow-orchestration-via-mcp-protocol

workflow-discovery-and-introspection

execution-status-polling-and-monitoring

parameter-binding-and-context-injection

error-handling-and-execution-failure-reporting

workflow-execution-history-retrieval

multi-workflow-orchestration-and-chaining

credential-and-secret-management-abstraction

Related Artifactssharing capabilities

@transcend-io/mcp-server-workflows

@mcpilotx/intentorch

@voltagent/mcp-server

mcp-n8n-workflow-builder

teste

n8n-mcp

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

About

Categories

Alternatives to n8n

Are you the builder of n8n?

Get the weekly brief

Data Sources