Skip to main content
Glama

Cursor n8n MCP Server

License: MIT Node.js Version

A Model Context Protocol (MCP) server that enables AI assistants in Cursor IDE to manage n8n workflows through the n8n REST API.

Features

  • Workflow Management: Create, update, delete, and list workflows

  • Workflow Activation: Activate and deactivate workflows

  • Execution Management: View execution history and details

  • Webhook Triggering: Trigger workflows via webhook URLs

  • Self-Documentation: Built-in help system for AI assistants

  • Node Information: Common n8n node types and configurations

  • Error Handling: Automatic retry with exponential backoff

Related MCP server: n8n MCP Server

Quick Start

Installation

git clone https://github.com/alicankiraz1/cursor-n8n-mcp.git
cd cursor-n8n-mcp

npm install
npm run build

node dist/index.js setup

Or use the install script:

./install.sh

Manual Configuration

Create or edit ~/.cursor/mcp.json for global configuration:

{
  "mcpServers": {
    "cursor-n8n-mcp": {
      "command": "node",
      "args": ["/path/to/cursor-n8n-mcp/dist/index.js"],
      "env": {
        "MCP_MODE": "stdio",
        "LOG_LEVEL": "error",
        "N8N_API_URL": "https://your-n8n-instance.com",
        "N8N_API_KEY": "your-api-key"
      }
    }
  }
}

Getting n8n API Key

  1. Log in to your n8n instance

  2. Go to Settings > API

  3. Click Create API Key

  4. Copy the generated key

Available Tools

Documentation & Help

Tool

Description

n8n_tools_help

Get usage guide and documentation

n8n_get_node_info

Get information about common n8n nodes

Workflow Management

Tool

Description

n8n_list_workflows

List all workflows

n8n_get_workflow

Get workflow details by ID

n8n_create_workflow

Create a new workflow

n8n_update_workflow

Update an existing workflow

n8n_delete_workflow

Delete a workflow

n8n_activate_workflow

Activate a workflow

n8n_deactivate_workflow

Deactivate a workflow

Execution Management

Tool

Description

n8n_list_executions

List execution history

n8n_get_execution

Get execution details

n8n_delete_execution

Delete an execution record

n8n_trigger_webhook

Trigger a workflow via webhook

System

Tool

Description

n8n_health_check

Check n8n API connectivity

Usage Examples

Check Connection

"Check the n8n connection"

List Workflows

"List all workflows in n8n"

Create a Workflow

"Create a webhook workflow that responds with the received data"

Get Node Information

"Show me how to configure a webhook node"

CLI Commands

node dist/index.js --help       # Show help
node dist/index.js setup        # Interactive setup
node dist/index.js config       # Show configuration template

Project Structure

cursor-n8n-mcp/
├── src/
│   ├── index.ts              # Entry point with CLI
│   ├── server.ts             # MCP Server implementation
│   ├── tools/
│   │   ├── index.ts          # Tool exports
│   │   ├── workflow-tools.ts # Workflow CRUD operations
│   │   ├── execution-tools.ts# Execution management
│   │   └── documentation-tools.ts # Help and node info
│   ├── services/
│   │   └── n8n-api-client.ts # n8n REST API client
│   ├── types/
│   │   └── index.ts          # TypeScript definitions
│   └── utils/
│       ├── logger.ts         # Logging utility
│       └── errors.ts         # Error handling
├── package.json
├── tsconfig.json
├── LICENSE
└── README.md

Supported Node Types

The n8n_get_node_info tool provides information about these common nodes:

  • Triggers: webhook, scheduleTrigger, manualTrigger

  • Actions: httpRequest, code, set, if, merge

  • Utilities: splitInBatches, respondToWebhook

Error Handling

The server includes robust error handling:

  • Automatic Retry: Failed requests are retried up to 3 times

  • Exponential Backoff: Delays increase between retries

  • Detailed Errors: Error messages include hints for resolution

  • Timeout Management: 30-second timeout for API requests

Environment Variables

Variable

Description

Required

N8N_API_URL

Your n8n instance URL

Yes

N8N_API_KEY

n8n API key

Yes

LOG_LEVEL

Log level (debug, info, warn, error)

No

MCP_MODE

MCP transport mode (stdio)

No

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

  1. Fork the repository

  2. Create your feature branch (git checkout -b feature/amazing-feature)

  3. Commit your changes (git commit -m 'Add some amazing feature')

  4. Push to the branch (git push origin feature/amazing-feature)

  5. Open a Pull Request

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgments

  • n8n - Workflow automation platform

  • Anthropic - Model Context Protocol

  • Cursor - AI-powered IDE

Available Tools

14 tools
n8n_activate_workflowB

Activate a workflow so it can be triggered. The workflow must have a valid trigger node.

Inputs: id (required).

n8n_create_workflowC

Create a new workflow with nodes and connections. The workflow will be created in inactive state.

Inputs: name (required), nodes (required), connections (required), settings.

n8n_deactivate_workflowC

Deactivate a workflow to stop it from being triggered.

Inputs: id (required).

n8n_delete_executionC

Delete an execution record.

Inputs: id (required).

n8n_delete_workflowA

Permanently delete a workflow. This action cannot be undone.

Inputs: id (required).

n8n_get_executionC

Get detailed information about a specific execution including input/output data.

Inputs: id (required), includeData.

n8n_get_node_infoC

Get information about common n8n node types and their configurations.

Inputs: nodeType (required).

n8n_get_workflowB

Get detailed information about a specific workflow including all nodes and connections.

Inputs: id (required).

n8n_health_checkA

Check the connection to the n8n instance and verify API credentials.

Inputs: no named parameters.

n8n_list_executionsC

List workflow executions. Can filter by workflow ID and status.

Inputs: workflowId, status, limit, includeData.

n8n_list_workflowsA

List all workflows in the n8n instance. Returns workflow IDs, names, and active status.

Inputs: limit, active.

n8n_tools_helpA

Get documentation and usage guide for n8n MCP tools. Call this first to understand available capabilities.

Inputs: topic.

n8n_trigger_webhookA

Trigger a workflow via its webhook URL. The workflow must be active and have a Webhook trigger node.

Inputs: webhookUrl (required), method, data, headers.

n8n_update_workflowC

Update an existing workflow. You can update name, nodes, connections, or settings.

Inputs: id (required), name, nodes, connections, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 14 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific resources and actions in the n8n domain. There is no overlap between workflow management tools (create, get, update, delete, activate, deactivate), execution tools (list, get, delete), and utility tools (health check, node info, tools help, trigger webhook). The descriptions reinforce these distinctions, making misselection unlikely.

    Naming Consistency5/5

    All tool names follow a perfect and consistent 'n8n_verb_noun' pattern throughout the set. The verb-noun structure is uniform (e.g., n8n_create_workflow, n8n_get_execution, n8n_health_check), with no deviations in style or convention. This predictability makes the tool set easy to navigate and understand.

    Tool Count5/5

    With 14 tools, the count is well-scoped for managing n8n workflows and executions. Each tool earns its place by covering essential operations like CRUD for workflows, execution lifecycle management, and necessary utilities. This provides comprehensive coverage without being overwhelming or sparse for the domain.

    Completeness5/5

    The tool surface offers complete CRUD and lifecycle coverage for workflows (create, get, update, delete, activate, deactivate, list) and executions (list, get, delete), along with utilities for health checks, node information, documentation, and triggering. There are no obvious gaps, and agents can perform all core n8n management tasks without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers