RSS 中文
⌕

Ep 23: Role Reversal — Exposing n8n Workflows as MCP Server

7 MIN READ | UPDATED: 2026-06-16
DIRECT SUMMARY // KEY TAKEAWAY

Use MCP Server Trigger to wrap n8n workflows as standard MCP Tools, enabling Claude Desktop and Cursor to remotely call your automation logic.

Why Turn n8n Into an MCP Server?

If you've built powerful workflows (RAG, CRM queries, order processing), expose them to other Agents!

graph LR
    Claude[Claude Desktop] & Cursor[Cursor IDE] -->|"MCP"| MCPTrigger[🔌 n8n MCP Server]
    MCPTrigger --> WF1[📋 Query Orders]
    MCPTrigger --> WF2[🔍 Search KB]
    MCPTrigger --> WF3[📧 Send Email]
    style MCPTrigger fill:#22c55e,stroke:#16a34a,color:#fff

1. MCP Server Trigger Config

// Tool Name: "query_order_status"
// Description: "Query order status by orderId. Returns {status, delivery, tracking}."
// Input Schema: { orderId: string (required) }

// Workflow nodes:
// 1. Extract orderId from MCP request
// 2. Query database
// 3. Format result
// 4. Respond to MCP Client

2. Claude Desktop Integration

// claude_desktop_config.json
{
  "mcpServers": {
    "n8n-tools": {
      "url": "https://your-n8n.com/mcp/sse",
      "transport": "sse"
    }
  }
}
// Claude auto-discovers n8n tools and calls them autonomously

3. Multi-Tool Server

One n8n instance can expose multiple tools — each as a separate workflow. External agents see all tools and choose autonomously.

Next Episode

Ep 24 builds an MCP service orchestration layer — managing discovery, registration, and health checks across multiple MCP Servers.