Does this work with self-hosted n8n instances?

Yes. You just need to provide your full n8n Base URL (e.g., https://n8n.your-company.com). Your agent will connect securely to your private instance using your n8n API Key.

Can I see exactly why an n8n execution failed through my agent?

Yes. Use the `get_execution` tool with a specific Execution ID. Your agent will retrieve the node-level trace logs, allowing you to see which specific node encountered an error and the resulting output payload for that step.

Can my agent list the automation credentials saved in my n8n account?

Absolutely. Use the `list_credentials` tool to identify all stored auth hooks. Your agent will report the credential names and system types (e.g., Slack, GitHub), helping you audit your integrations without exposing literal secure tokens.

n8n (AI Workflow Automation) MCP Server for CrewAI 7 tools — connect in under 2 minutes

Name: n8n (AI Workflow Automation)
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 7 Tools Framework

Connect your CrewAI agents to n8n (AI Workflow Automation) through the Vinkius — pass the Edge URL in the `mcps` parameter and every n8n (AI Workflow Automation) tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="n8n (AI Workflow Automation) Specialist",
    goal="Help users interact with n8n (AI Workflow Automation) effectively",
    backstory=(
        "You are an expert at leveraging n8n (AI Workflow Automation) tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in n8n (AI Workflow Automation) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 7 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About n8n (AI Workflow Automation) MCP Server

Connect your n8n instance to any AI agent and take full control of your node-based workflow automation, execution diagnostics, and project orchestration through natural conversation.

When paired with CrewAI, n8n (AI Workflow Automation) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call n8n (AI Workflow Automation) tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Workflow Orchestration — List all managed automation workflows and retrieve detailed JSON logic nodes, including link mappings and trigger configurations directly from your agent
Execution Diagnostics — Extract historical execution logs to track success/failure boundaries and retrieve absolute trace logs for rapid debugging of automation failures
Node-Level Inspection — Deep-dive into specific execution IDs to extract bounded node-level output blocks and identify exact processing errors natively
Credential Audit — List metadata mapping saved automation credentials to verify system types and IDs without exposing literal secure tokens
Collaborative Visibility — Enumerate provisioned team users and assigned roles to verify access targets across your n8n infrastructure securely
Organizational Tags — List arbitrary category tags used to group and sort complex workflow logic dimensions across your automation workspace
Metadata Inspection — Retrieve precise graph representations for specific workflows to understand the underlying logic and data transformation flows instantly

The n8n (AI Workflow Automation) MCP Server exposes 7 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect n8n (AI Workflow Automation) to CrewAI via MCP

Follow these steps to integrate the n8n (AI Workflow Automation) MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 7 tools from n8n (AI Workflow Automation)

Why Use CrewAI with the n8n (AI Workflow Automation) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with n8n (AI Workflow Automation) through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

n8n (AI Workflow Automation) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the n8n (AI Workflow Automation) MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries n8n (AI Workflow Automation) for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries n8n (AI Workflow Automation), analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain n8n (AI Workflow Automation) tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries n8n (AI Workflow Automation) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

n8n (AI Workflow Automation) MCP Tools for CrewAI (7)

These 7 tools become available when you connect n8n (AI Workflow Automation) to CrewAI via MCP:

get_execution_details

Get trace logs for a specific execution

get_workflow_details

Get details for a specific workflow

list_instance_users

List collaborators on the n8n instance

list_stored_credentials

List metadata for saved credentials

list_workflow_executions

List recent workflow executions

list_workflow_tags

List workflow organizational tags

list_workflows

List n8n automation workflows

Example Prompts for n8n (AI Workflow Automation) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with n8n (AI Workflow Automation) immediately.

"List all active workflows in my n8n instance"

"Show me the last 5 failed executions in n8n"

"List all n8n credentials associated with 'Slack'"

Troubleshooting n8n (AI Workflow Automation) MCP Server with CrewAI

Common issues when connecting n8n (AI Workflow Automation) to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

n8n (AI Workflow Automation) + CrewAI FAQ

Common questions about integrating n8n (AI Workflow Automation) MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.