Enables management of n8n workflows through the n8n REST API, including workflow creation, updates, deletion, activation/deactivation, execution history viewing, and webhook triggering.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Cursor n8n BuilderList all my active workflows"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Cursor n8n MCP Server
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
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 setupOr use the install script:
./install.shManual 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
Log in to your n8n instance
Go to Settings > API
Click Create API Key
Copy the generated key
Available Tools
Documentation & Help
Tool | Description |
| Get usage guide and documentation |
| Get information about common n8n nodes |
Workflow Management
Tool | Description |
| List all workflows |
| Get workflow details by ID |
| Create a new workflow |
| Update an existing workflow |
| Delete a workflow |
| Activate a workflow |
| Deactivate a workflow |
Execution Management
Tool | Description |
| List execution history |
| Get execution details |
| Delete an execution record |
| Trigger a workflow via webhook |
System
Tool | Description |
| 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 templateProject 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.mdSupported 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 |
| Your n8n instance URL | Yes |
| n8n API key | Yes |
| Log level (debug, info, warn, error) | No |
| MCP transport mode (stdio) | No |
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Fork the repository
Create your feature branch (
git checkout -b feature/amazing-feature)Commit your changes (
git commit -m 'Add some amazing feature')Push to the branch (
git push origin feature/amazing-feature)Open a Pull Request
License
This project is licensed under the MIT License - see the LICENSE file for details.
Acknowledgments
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.