n8n工作流自动化MCP服务

n8n-mcp

Lets an AI assistant build, run and fix n8n automations for you.

Connect it to Claude, Cursor or VS Code and describe the automation you want. The assistant gets 29 typed tools: it checks a workflow against a catalogue of 300+ n8n nodes before creating it, runs it, reads the failure when a step breaks, and gets back concrete fix suggestions it can apply. The checking happens before anything touches your n8n instance.

Built on the MCP TypeScript SDK and the n8n public API. Runs over Streamable HTTP (for remote clients like Claude, Cursor, VS Code) or stdio (for local desktop clients).

Features

• 29 typed tools spanning workflow management, execution, diagnostics, node intelligence, templates, and validation.
• Pre-creation validation - validate_workflow checks node types, required parameters, connection integrity, duplicate names, orphan nodes, credentials, and typeVersion mismatches before anything hits n8n.
• Self-healing loop - self_heal_workflow executes a workflow, diagnoses failures, and returns concrete fix suggestions the agent can apply via update_workflow.
• Node catalogue kept in sync with n8n nodes-base v2.14.0, including current typeVersion values for HTTP Request, Postgres, Slack, Gmail, OpenAI, and the newer AI nodes (AI Transform, Data Table, Guardrails, Evaluation, MCP Server Trigger).
• Golden-path examples - annotated workflow templates for common patterns (webhook-transform-respond, schedule-fetch-filter-notify, error handling, batch loops).
• HTTP server hardening - CORS allow-listing, rate limiting, security headers, structured logging via pino, and graceful shutdown.
• Cloud client - a tiny CLI that talks to a remote MCP endpoint over curl, for environments where claude mcp add is unavailable.

Quick start

git clone https://github.com/aidvgg/n8n-mcp.git
cd n8n-mcp
npm install
npm run build

Create a .env file:

N8N_API_URL=https://your-n8n-instance.example.com/api/v1
N8N_API_KEY=your-api-key-here
PORT=3000
NODE_ENV=development
ALLOWED_ORIGINS=https://claude.ai,https://cursor.sh

Run it:

npm start           # HTTP server on PORT (default 3000)
npm run start:stdio # stdio mode for local desktop clients
npm run dev         # watch mode (bun)

Health check:

curl http://localhost:3000/health

Connecting an MCP client

Claude Code, Cursor, VS Code (Streamable HTTP)

Point your client at http://localhost:3000/mcp (or your deployed URL). For Claude Code:

claude mcp add n8n https://your-deployment.example.com/mcp

Claude Desktop (stdio)

In claude_desktop_config.json:

{
  "mcpServers": {
    "n8n": {
      "command": "node",
      "args": ["/absolute/path/to/n8n-mcp/dist/server.js", "--stdio"],
      "env": {
        "N8N_API_URL": "https://your-n8n.example.com/api/v1",
        "N8N_API_KEY": "your-api-key"
      }
    }
  }
}

Cloud sessions (no mcp add available)

Use the bundled cloud client to call tools directly:

node dist/cloud-client.js https://your-deployment.example.com/mcp list-tools
node dist/cloud-client.js https://your-deployment.example.com/mcp call list_workflows '{}'
node dist/cloud-client.js https://your-deployment.example.com/mcp call execute_workflow '{"workflowId":"123"}'

The default URL can be overridden with the MCP_SERVER_URL environment variable.

Available tools

Workflow management

Execution

Diagnostics and self-healing

Node intelligence

Templates and examples

Validation

Metadata

Recommended workflow development cycle

1. list_workflow_examples - find a similar pattern
2. get_node_schema - confirm parameters for each node
3. validate_workflow - verify the definition before creation
4. create_workflow - deploy it
5. self_heal_workflow - execute and collect fix suggestions
6. update_workflow - apply the fixes
7. Repeat 5–6 until every node passes

Configuration

HTTP endpoints

Development

npm run dev         # watch mode via bun
npm run build       # compile TypeScript to dist/
npm run typecheck   # type-check without emitting
bun test            # run the test suite
bun test --coverage # with coverage report
npm run inspector   # launch the MCP Inspector against this server

The codebase is laid out as:

src/
  server.ts        # HTTP + stdio entry point, transport wiring
  tools.ts         # Tool registration and validation logic
  resources.ts     # MCP resource handlers (workflows, executions)
  n8n-client.ts    # n8n REST API client with retries and timeouts
  node-catalog.ts  # Node schemas, categories, search
  examples.ts      # Golden-path workflow examples
  expressions/    # n8n expression reference
  templates/      # Built-in workflow templates
  nodes/          # Per-integration node definitions
  cloud-client.ts  # Standalone CLI for remote MCP calls
  logger.ts        # pino setup

License

MIT.