n8n-mcp-orchestrator

n8n MCP Orchestrator

A comprehensive skill for orchestrating AI agents and workflows using n8n's Model Context Protocol (MCP) integration. This skill enables bidirectional MCP patterns, agentic workflow automation, and production-ready AI-powered systems with Claude Code integration.

When to Use This Skill

Use this skill when:

• Building AI-powered automation workflows with n8n
• Exposing n8n workflows as tools for AI agents (Claude Code, Claude Desktop)
• Consuming external MCP servers from n8n workflows
• Orchestrating multi-agent systems and agentic workflows
• Creating tool-using AI agents with n8n backend
• Integrating Claude Code with business process automation
• Building context-aware automation with MCP resources
• Coordinating complex workflows across multiple AI agents
• Developing production-ready AI orchestration pipelines
• Implementing bidirectional MCP communication patterns
• Creating autonomous agent systems with workflow orchestration
• Building AI-first automation with 400+ service integrations

Core Concepts

Model Context Protocol (MCP)

The Model Context Protocol is an open standard for connecting AI assistants to external systems:

• Bidirectional Communication: Clients and servers can both initiate requests
• Resource Management: Expose data and context as resources
• Tool Invocation: AI agents can execute tools (functions/workflows)
• Prompt Templates: Provide structured prompts to AI systems
• Security: Built-in authentication and authorization patterns
• Scalability: Designed for production AI orchestration

MCP Architecture Components

1. MCP Servers

• Expose capabilities (tools, resources, prompts) to AI clients
• Can be standalone services or embedded in applications
• Handle authentication, rate limiting, and security
• n8n workflows can act as MCP servers

2. MCP Clients

• Connect to MCP servers and invoke their capabilities
• AI assistants like Claude Code and Claude Desktop
• n8n workflows can act as MCP clients

3. Resources

• Data sources and context exposed by MCP servers
• Examples: documents, database records, API responses
• AI agents can read resources for context

4. Tools

• Functions/workflows that AI agents can invoke
• Accept parameters and return results
• n8n workflows become AI-callable tools

5. Prompts

• Structured prompt templates for AI interactions
• Include context, instructions, and variables
• Guide AI behavior in specific scenarios

n8n's Bidirectional MCP Capability

n8n as MCP Server (Expose workflows as tools):

• MCP Server Trigger node activates workflow when called by AI
• Workflows become tools that Claude Code can invoke
• Enable AI agents to automate complex business processes
• Return structured data to AI clients

n8n as MCP Client (Call external MCP servers):

• MCP Client Tool node invokes external MCP servers
• Call tools from other MCP-compatible services
• Orchestrate multiple MCP servers in single workflow
• Build complex automation chains

Key MCP Nodes in n8n

1. MCP Server Trigger

• Workflow entry point for MCP tool invocations
• Receives parameters from AI agents
• Returns results to calling AI client
• Supports authentication and validation

2. MCP Client Tool

• Call external MCP server tools
• Pass parameters to remote tools
• Handle responses and errors
• Chain multiple MCP calls

n8n as MCP Server

Exposing Workflows as AI Agent Tools

When you create a workflow with an MCP Server Trigger, that workflow becomes a tool that AI agents can invoke.

Architecture Pattern:

┌─────────────────────────────────────────────────────────────────┐
│                    Claude Code / Claude Desktop                 │
│                                                                 │
│  Agent decides to use tool:                                     │
│  "I need to create a support ticket for this bug"              │
└─────────────────────────────────────────────────────────────────┘
                          │
                          ↓ MCP Tool Invocation
┌─────────────────────────────────────────────────────────────────┐
│                    n8n Workflow (MCP Server)                    │
│                                                                 │
│  ┌──────────────────────────────────────────────────────────┐  │
│  │ MCP Server Trigger                                        │  │
│  │ Tool: "create_support_ticket"                             │  │
│  │ Receives: {title, description, priority}                  │  │
│  └──────────────────────────────────────────────────────────┘  │
│                          │                                      │
│                          ↓                                      │
│  ┌──────────────────────────────────────────────────────────┐  │
│  │ HTTP Request: Call Jira API                               │  │
│  └──────────────────────────────────────────────────────────┘  │
│                          │                                      │
│                          ↓                                      │
│  ┌──────────────────────────────────────────────────────────┐  │
│  │ Slack Notification: Notify team                           │  │
│  └──────────────────────────────────────────────────────────┘  │
│                          │                                      │
│                          ↓                                      │
│  ┌──────────────────────────────────────────────────────────┐  │
│  │ Respond to MCP: Return ticket ID                          │  │
│  └──────────────────────────────────────────────────────────┘  │
└─────────────────────────────────────────────────────────────────┘
                          │
                          ↓ MCP Response
┌─────────────────────────────────────────────────────────────────┐
│                    Claude Code                                  │
│                                                                 │
│  Receives: {ticketId: "JIRA-12345", status: "created"}        │
│  Continues conversation with user                              │
└─────────────────────────────────────────────────────────────────┘

MCP Server Trigger Configuration

Basic Setup:

1. Create New Workflow in n8n

2. Add MCP Server Trigger node as entry point

3. Configure Tool Definition:

   • Tool Name: Unique identifier (e.g., "create_support_ticket")
   • Description: Clear description for AI to understand when to use
   • Parameters: Define input schema (JSON Schema format)
   • Authentication: Optional authentication settings

4. Build Workflow Logic: Add nodes to process the request

5. Return Response: Last node output becomes MCP response

MCP Server Trigger Parameters:

{
  "toolName": "create_support_ticket",
  "description": "Create a support ticket in Jira with automatic team notification",
  "parameters": {
    "type": "object",
    "properties": {
      "title": {
        "type": "string",
        "description": "Brief ticket title"
      },
      "description": {
        "type": "string",
        "description": "Detailed problem description"
      },
      "priority": {
        "type": "string",
        "enum": ["low", "medium", "high", "critical"],
        "description": "Ticket priority level"
      },
      "component": {
        "type": "string",
        "description": "System component affected"
      }
    },
    "required": ["title", "description"]
  }
}

Response Format

The final node output in your workflow is returned to the AI agent:

{
  "success": true,
  "ticketId": "JIRA-12345",
  "url": "https://company.atlassian.net/browse/JIRA-12345",
  "assignee": "[email protected]",
  "createdAt": "2025-10-20T10:30:00Z"
}

Authentication Patterns

1. API Key Authentication

{
  "authenticationType": "apiKey",
  "apiKeyHeader": "X-API-Key",
  "requiredScopes": ["workflows:execute"]
}

2. OAuth 2.0

{
  "authenticationType": "oauth2",
  "authorizationUrl": "https://auth.company.com/oauth/authorize",
  "tokenUrl": "https://auth.company.com/oauth/token",
  "scopes": ["workflows:read", "workflows:execute"]
}

3. No Authentication (internal use only)

{
  "authenticationType": "none"
}

n8n as MCP Client

Consuming External MCP Servers

The MCP Client Tool node allows n8n workflows to call external MCP servers and use their tools.

Architecture Pattern:

┌─────────────────────────────────────────────────────────────────┐
│                    n8n Workflow                                 │
│                                                                 │
│  ┌──────────────────────────────────────────────────────────┐  │
│  │ Schedule Trigger: Every day at 9am                        │  │
│  └──────────────────────────────────────────────────────────┘  │
│                          │                                      │
│                          ↓                                      │
│  ┌──────────────────────────────────────────────────────────┐  │
│  │ MCP Client Tool                                           │  │
│  │ Server: "analytics-mcp-server"                            │  │
│  │ Tool: "generate_daily_report"                             │  │
│  │ Params: {date: "today"}                                   │  │
│  └──────────────────────────────────────────────────────────┘  │
└─────────────────────────────────────────────────────────────────┘
                          │
                          ↓ MCP Request
┌─────────────────────────────────────────────────────────────────┐
│                    External MCP Server                          │
│                    (Analytics Service)                          │
│                                                                 │
│  Processes request, generates report, returns data             │
└────────────────────────────────────────────────────────────

---

*Content truncated.*