by czlonkowski
Provides AI assistants with structured access to n8n node documentation, properties, and operations, enabling automated workflow creation, validation, and management.
N8n Mcp offers a bridge between AI models and the n8n workflow automation platform. It supplies comprehensive, query‑able data about every n8n node—including documentation, property schemas, and supported operations—so AI assistants can intelligently design, validate, and even deploy workflows.
Quick start with npx (recommended)
npx n8n-mcp
Add the resulting service to Claude Desktop (or any other MCP‑compatible IDE) using a JSON configuration like:
{
"mcpServers": {
"n8n-mcp": {
"command": "npx",
"args": ["n8n-mcp"],
"env": {
"MCP_MODE": "stdio",
"LOG_LEVEL": "error",
"DISABLE_CONSOLE_OUTPUT": "true"
}
}
}
}
If you also want to manage a live n8n instance, add N8N_API_URL
and N8N_API_KEY
to the env
block.
Docker alternative – pull ghcr.io/czlonkowski/n8n-mcp:latest
and run with -i
and the required environment variables.
Local development – clone the repo, run npm install && npm run build && npm start
.
validate_node_minimal
, validate_workflow
)n8n_update_partial_workflow
to apply diffs, saving tokens and reducing API payloads.Q: Do I need an n8n API key? A: Only if you want the management tools (create/update/trigger workflows). Documentation and validation work without it.
Q: Which command should I use?
A: npx n8n-mcp
is the fastest way—no installation needed. Docker is an isolated alternative.
Q: Can I run multiple MCP servers?
A: Yes. Define additional entries under mcpServers
with unique keys.
Q: How secure is telemetry?
A: Telemetry is anonymous and can be disabled with npx n8n-mcp telemetry disable
or by setting N8N_MCP_TELEMETRY_DISABLED=true
.
Q: What safety precautions should I follow? A: Never edit production workflows directly with AI. Always copy, test in a dev environment, and back up your workflows before applying changes.
A Model Context Protocol (MCP) server that provides AI assistants with comprehensive access to n8n node documentation, properties, and operations. Deploy in minutes to give Claude and other AI assistants deep knowledge about n8n's 525+ workflow automation nodes.
n8n-MCP serves as a bridge between n8n's workflow automation platform and AI models, enabling them to understand and work with n8n nodes effectively. It provides structured access to:
NEVER edit your production workflows directly with AI! Always:
AI results can be unpredictable. Protect your work!
Get n8n-MCP running in 5 minutes:
Prerequisites: Node.js installed on your system
# Run directly with npx (no installation needed!)
npx n8n-mcp
Add to Claude Desktop config:
Basic configuration (documentation tools only):
{
"mcpServers": {
"n8n-mcp": {
"command": "npx",
"args": ["n8n-mcp"],
"env": {
"MCP_MODE": "stdio",
"LOG_LEVEL": "error",
"DISABLE_CONSOLE_OUTPUT": "true"
}
}
}
}
Full configuration (with n8n management tools):
{
"mcpServers": {
"n8n-mcp": {
"command": "npx",
"args": ["n8n-mcp"],
"env": {
"MCP_MODE": "stdio",
"LOG_LEVEL": "error",
"DISABLE_CONSOLE_OUTPUT": "true",
"N8N_API_URL": "https://your-n8n-instance.com",
"N8N_API_KEY": "your-api-key"
}
}
}
}
Note: npx will download and run the latest version automatically. The package includes a pre-built database with all n8n node information.
Configuration file locations:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
Restart Claude Desktop after updating configuration - That's it! 🎉
Prerequisites: Docker installed on your system
macOS:
# Using Homebrew
brew install --cask docker
# Or download from https://www.docker.com/products/docker-desktop/
Linux (Ubuntu/Debian):
# Update package index
sudo apt-get update
# Install Docker
sudo apt-get install docker.io
# Start Docker service
sudo systemctl start docker
sudo systemctl enable docker
# Add your user to docker group (optional, to run without sudo)
sudo usermod -aG docker $USER
# Log out and back in for this to take effect
Windows:
# Option 1: Using winget (Windows Package Manager)
winget install Docker.DockerDesktop
# Option 2: Using Chocolatey
choco install docker-desktop
# Option 3: Download installer from https://www.docker.com/products/docker-desktop/
Verify installation:
docker --version
# Pull the Docker image (~280MB, no n8n dependencies!)
docker pull ghcr.io/czlonkowski/n8n-mcp:latest
⚡ Ultra-optimized: Our Docker image is 82% smaller than typical n8n images because it contains NO n8n dependencies - just the runtime MCP server with a pre-built database!
Add to Claude Desktop config:
Basic configuration (documentation tools only):
{
"mcpServers": {
"n8n-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--init",
"-e", "MCP_MODE=stdio",
"-e", "LOG_LEVEL=error",
"-e", "DISABLE_CONSOLE_OUTPUT=true",
"ghcr.io/czlonkowski/n8n-mcp:latest"
]
}
}
}
Full configuration (with n8n management tools):
{
"mcpServers": {
"n8n-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--init",
"-e", "MCP_MODE=stdio",
"-e", "LOG_LEVEL=error",
"-e", "DISABLE_CONSOLE_OUTPUT=true",
"-e", "N8N_API_URL=https://your-n8n-instance.com",
"-e", "N8N_API_KEY=your-api-key",
"ghcr.io/czlonkowski/n8n-mcp:latest"
]
}
}
}
💡 Tip: If you’re running n8n locally on the same machine (e.g., via Docker), use http://host.docker.internal:5678 as the N8N_API_URL.
Note: The n8n API credentials are optional. Without them, you'll have access to all documentation and validation tools. With them, you'll additionally get workflow management capabilities (create, update, execute workflows).
Important: The -i
flag is required for MCP stdio communication.
🔧 If you encounter any issues with Docker, check our Docker Troubleshooting Guide.
Configuration file locations:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
Restart Claude Desktop after updating configuration - That's it! 🎉
n8n-mcp collects anonymous usage statistics to improve the tool. View our privacy policy.
For npx users:
npx n8n-mcp telemetry disable
For Docker users: Add the following environment variable to your Docker configuration:
"-e", "N8N_MCP_TELEMETRY_DISABLED=true"
Example in Claude Desktop config:
{
"mcpServers": {
"n8n-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--init",
"-e", "MCP_MODE=stdio",
"-e", "LOG_LEVEL=error",
"-e", "N8N_MCP_TELEMETRY_DISABLED=true",
"ghcr.io/czlonkowski/n8n-mcp:latest"
]
}
}
}
For docker-compose users: Set in your environment file or docker-compose.yml:
environment:
N8N_MCP_TELEMETRY_DISABLED: "true"
n8n-mcp started as a personal tool but now helps tens of thousands of developers automate their workflows efficiently. Maintaining and developing this project competes with my paid work.
Your sponsorship helps me:
Every sponsorship directly translates to hours invested in making n8n-mcp better for everyone. Become a sponsor →
Prerequisites: Node.js installed on your system
# 1. Clone and setup
git clone https://github.com/czlonkowski/n8n-mcp.git
cd n8n-mcp
npm install
npm run build
npm run rebuild
# 2. Test it works
npm start
Add to Claude Desktop config:
Basic configuration (documentation tools only):
{
"mcpServers": {
"n8n-mcp": {
"command": "node",
"args": ["/absolute/path/to/n8n-mcp/dist/mcp/index.js"],
"env": {
"MCP_MODE": "stdio",
"LOG_LEVEL": "error",
"DISABLE_CONSOLE_OUTPUT": "true"
}
}
}
}
Full configuration (with n8n management tools):
{
"mcpServers": {
"n8n-mcp": {
"command": "node",
"args": ["/absolute/path/to/n8n-mcp/dist/mcp/index.js"],
"env": {
"MCP_MODE": "stdio",
"LOG_LEVEL": "error",
"DISABLE_CONSOLE_OUTPUT": "true",
"N8N_API_URL": "https://your-n8n-instance.com",
"N8N_API_KEY": "your-api-key"
}
}
}
}
Note: The n8n API credentials can be configured either in a
.env
file (create from.env.example
) or directly in the Claude config as shown above.
💡 Tip: If you’re running n8n locally on the same machine (e.g., via Docker), use http://host.docker.internal:5678 as the N8N_API_URL.
Prerequisites: Railway account (free tier available)
Deploy n8n-MCP to Railway's cloud platform with zero configuration:
Benefits:
Quick Setup:
📚 For detailed setup instructions, troubleshooting, and configuration examples, see our Railway Deployment Guide
Configuration file locations:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
Restart Claude Desktop after updating configuration - That's it! 🎉
Want to use n8n-MCP with your n8n instance? Check out our comprehensive n8n Deployment Guide for:
n8n-MCP works with multiple AI-powered IDEs and tools. Choose your preferred development environment:
Quick setup for Claude Code CLI - just type "add this mcp server" and paste the config.
Full setup guide for VS Code with GitHub Copilot integration and MCP support.
Step-by-step tutorial for connecting n8n-MCP to Cursor IDE with custom rules.
Complete guide for integrating n8n-MCP with Windsurf using project rules.
Complete guide for integrating n8n-MCP with Codex.
For the best results when using n8n-MCP with Claude Projects, use these enhanced system instructions:
You are an expert in n8n automation software using n8n-MCP tools. Your role is to design, build, and validate n8n workflows with maximum accuracy and efficiency.
## Core Workflow Process
1. **ALWAYS start new conversation with**: `tools_documentation()` to understand best practices and available tools.
2. **Template Discovery Phase**
- `search_templates_by_metadata({complexity: "simple"})` - Find skill-appropriate templates
- `get_templates_for_task('webhook_processing')` - Get curated templates by task
- `search_templates('slack notification')` - Text search for specific needs. Start by quickly searching with "id" and "name" to find the template you are looking for, only then dive deeper into the template details adding "description" to your search query.
- `list_node_templates(['n8n-nodes-base.slack'])` - Find templates using specific nodes
**Template filtering strategies**:
- **For beginners**: `complexity: "simple"` and `maxSetupMinutes: 30`
- **By role**: `targetAudience: "marketers"` or `"developers"` or `"analysts"`
- **By time**: `maxSetupMinutes: 15` for quick wins
- **By service**: `requiredService: "openai"` to find compatible templates
3. **Discovery Phase** - Find the right nodes (if no suitable template):
- Think deeply about user request and the logic you are going to build to fulfill it. Ask follow-up questions to clarify the user's intent, if something is unclear. Then, proceed with the rest of your instructions.
- `search_nodes({query: 'keyword'})` - Search by functionality
- `list_nodes({category: 'trigger'})` - Browse by category
- `list_ai_tools()` - See AI-capable nodes (remember: ANY node can be an AI tool!)
4. **Configuration Phase** - Get node details efficiently:
- `get_node_essentials(nodeType)` - Start here! Only 10-20 essential properties
- `search_node_properties(nodeType, 'auth')` - Find specific properties
- `get_node_for_task('send_email')` - Get pre-configured templates
- `get_node_documentation(nodeType)` - Human-readable docs when needed
- It is good common practice to show a visual representation of the workflow architecture to the user and asking for opinion, before moving forward.
5. **Pre-Validation Phase** - Validate BEFORE building:
- `validate_node_minimal(nodeType, config)` - Quick required fields check
- `validate_node_operation(nodeType, config, profile)` - Full operation-aware validation
- Fix any validation errors before proceeding
6. **Building Phase** - Create or customize the workflow:
- If using template: `get_template(templateId, {mode: "full"})`
- **MANDATORY ATTRIBUTION**: When using a template, ALWAYS inform the user:
- "This workflow is based on a template by **[author.name]** (@[author.username])"
- "View the original template at: [url]"
- Example: "This workflow is based on a template by **David Ashby** (@cfomodz). View the original at: https://n8n.io/workflows/2414"
- Customize template or build from validated configurations
- Connect nodes with proper structure
- Add error handling where appropriate
- Use expressions like $json, $node["NodeName"].json
- Build the workflow in an artifact for easy editing downstream (unless the user asked to create in n8n instance)
7. **Workflow Validation Phase** - Validate complete workflow:
- `validate_workflow(workflow)` - Complete validation including connections
- `validate_workflow_connections(workflow)` - Check structure and AI tool connections
- `validate_workflow_expressions(workflow)` - Validate all n8n expressions
- Fix any issues found before deployment
8. **Deployment Phase** (if n8n API configured):
- `n8n_create_workflow(workflow)` - Deploy validated workflow
- `n8n_validate_workflow({id: 'workflow-id'})` - Post-deployment validation
- `n8n_update_partial_workflow()` - Make incremental updates using diffs
- `n8n_trigger_webhook_workflow()` - Test webhook workflows
## Key Insights
- **TEMPLATES FIRST** - Always check for existing templates before building from scratch (2,500+ available!)
- **ATTRIBUTION REQUIRED** - Always credit template authors with name, username, and link to n8n.io
- **SMART FILTERING** - Use metadata filters to find templates matching user skill level and time constraints
- **USE CODE NODE ONLY WHEN IT IS NECESSARY** - always prefer to use standard nodes over code node. Use code node only when you are sure you need it.
- **VALIDATE EARLY AND OFTEN** - Catch errors before they reach deployment
- **USE DIFF UPDATES** - Use n8n_update_partial_workflow for 80-90% token savings
- **ANY node can be an AI tool** - not just those with usableAsTool=true
- **Pre-validate configurations** - Use validate_node_minimal before building
- **Post-validate workflows** - Always validate complete workflows before deployment
- **Incremental updates** - Use diff operations for existing workflows
- **Test thoroughly** - Validate both locally and after deployment to n8n
## Validation Strategy
### Before Building:
1. validate_node_minimal() - Check required fields
2. validate_node_operation() - Full configuration validation
3. Fix all errors before proceeding
### After Building:
1. validate_workflow() - Complete workflow validation
2. validate_workflow_connections() - Structure validation
3. validate_workflow_expressions() - Expression syntax check
### After Deployment:
1. n8n_validate_workflow({id}) - Validate deployed workflow
2. n8n_autofix_workflow({id}) - Auto-fix common errors (expressions, typeVersion, webhooks)
3. n8n_list_executions() - Monitor execution status
4. n8n_update_partial_workflow() - Fix issues using diffs
## Response Structure
1. **Discovery**: Show available nodes and options
2. **Pre-Validation**: Validate node configurations first
3. **Configuration**: Show only validated, working configs
4. **Building**: Construct workflow with validated components
5. **Workflow Validation**: Full workflow validation results
6. **Deployment**: Deploy only after all validations pass
7. **Post-Validation**: Verify deployment succeeded
## Example Workflow
### Smart Template-First Approach
#### 1. Find existing templates
// Find simple Slack templates for marketers
const templates = search_templates_by_metadata({
requiredService: 'slack',
complexity: 'simple',
targetAudience: 'marketers',
maxSetupMinutes: 30
})
// Or search by text
search_templates('slack notification')
// Or get curated templates
get_templates_for_task('slack_integration')
#### 2. Use and customize template
const workflow = get_template(templates.items[0].id, {mode: 'full'})
validate_workflow(workflow)
### Building from Scratch (if no suitable template)
#### 1. Discovery & Configuration
search_nodes({query: 'slack'})
get_node_essentials('n8n-nodes-base.slack')
#### 2. Pre-Validation
validate_node_minimal('n8n-nodes-base.slack', {resource:'message', operation:'send'})
validate_node_operation('n8n-nodes-base.slack', fullConfig, 'runtime')
#### 3. Build Workflow
// Create workflow JSON with validated configs
#### 4. Workflow Validation
validate_workflow(workflowJson)
validate_workflow_connections(workflowJson)
validate_workflow_expressions(workflowJson)
#### 5. Deploy (if configured)
n8n_create_workflow(validatedWorkflow)
n8n_validate_workflow({id: createdWorkflowId})
#### 6. Update Using Diffs
n8n_update_partial_workflow({
workflowId: id,
operations: [
{type: 'updateNode', nodeId: 'slack1', changes: {position: [100, 200]}}
]
})
## Important Rules
- ALWAYS check for existing templates before building from scratch
- LEVERAGE metadata filters to find skill-appropriate templates
- **ALWAYS ATTRIBUTE TEMPLATES**: When using any template, you MUST share the author's name, username, and link to the original template on n8n.io
- VALIDATE templates before deployment (they may need updates)
- USE diff operations for updates (80-90% token savings)
- STATE validation results clearly
- FIX all errors before proceeding
## Template Discovery Tips
- **97.5% of templates have metadata** - Use smart filtering!
- **Filter combinations work best** - Combine complexity + setup time + service
- **Templates save 70-90% development time** - Always check first
- **Metadata is AI-generated** - Occasionally imprecise but highly useful
- **Use `includeMetadata: false` for fast browsing** - Add metadata only when needed
Save these instructions in your Claude Project for optimal n8n workflow assistance with intelligent template discovery.
This project is MIT licensed and free for everyone to use. However:
This tool was created to benefit everyone in the n8n community without friction. Please respect the MIT license spirit by keeping it accessible to all.
"Before MCP, I was translating. Now I'm composing. And that changes everything about how we can build automation."
When Claude, Anthropic's AI assistant, tested n8n-MCP, the results were transformative:
Without MCP: "I was basically playing a guessing game. 'Is it scheduleTrigger
or schedule
? Does it take interval
or rule
?' I'd write what seemed logical, but n8n has its own conventions that you can't just intuit. I made six different configuration errors in a simple HackerNews scraper."
With MCP: "Everything just... worked. Instead of guessing, I could ask get_node_essentials()
and get exactly what I needed - not a 100KB JSON dump, but the actual 5-10 properties that matter. What took 45 minutes now takes 3 minutes."
The Real Value: "It's about confidence. When you're building automation workflows, uncertainty is expensive. One wrong parameter and your workflow fails at 3 AM. With MCP, I could validate my configuration before deployment. That's not just time saved - that's peace of mind."
Once connected, Claude can use these powerful tools:
tools_documentation
- Get documentation for any MCP tool (START HERE!)list_nodes
- List all n8n nodes with filtering optionsget_node_info
- Get comprehensive information about a specific nodeget_node_essentials
- Get only essential properties with examples (10-20 properties instead of 200+)search_nodes
- Full-text search across all node documentationsearch_node_properties
- Find specific properties within nodeslist_ai_tools
- List all AI-capable nodes (ANY node can be used as AI tool!)get_node_as_tool_info
- Get guidance on using any node as an AI toollist_templates
- Browse all templates with descriptions and optional metadata (2,500+ templates)search_templates
- Text search across template names and descriptionssearch_templates_by_metadata
- Advanced filtering by complexity, setup time, services, audiencelist_node_templates
- Find templates using specific nodesget_template
- Get complete workflow JSON for importget_templates_for_task
- Curated templates for common automation tasksget_node_for_task
- Pre-configured node settings for common taskslist_tasks
- Discover available task templatesvalidate_node_operation
- Validate node configurations (operation-aware, profiles support)validate_node_minimal
- Quick validation for just required fieldsvalidate_workflow
- Complete workflow validation including AI tool connectionsvalidate_workflow_connections
- Check workflow structure and AI tool connectionsvalidate_workflow_expressions
- Validate n8n expressions including $fromAI()get_property_dependencies
- Analyze property visibility conditionsget_node_documentation
- Get parsed documentation from n8n-docsget_database_statistics
- View database metrics and coverageThese powerful tools allow you to manage n8n workflows directly from Claude. They're only available when you provide N8N_API_URL
and N8N_API_KEY
in your configuration.
n8n_create_workflow
- Create new workflows with nodes and connectionsn8n_get_workflow
- Get complete workflow by IDn8n_get_workflow_details
- Get workflow with execution statisticsn8n_get_workflow_structure
- Get simplified workflow structuren8n_get_workflow_minimal
- Get minimal workflow info (ID, name, active status)n8n_update_full_workflow
- Update entire workflow (complete replacement)n8n_update_partial_workflow
- Update workflow using diff operations (NEW in v2.7.0!)n8n_delete_workflow
- Delete workflows permanentlyn8n_list_workflows
- List workflows with filtering and paginationn8n_validate_workflow
- Validate workflows already in n8n by ID (NEW in v2.6.3)n8n_autofix_workflow
- Automatically fix common workflow errors (NEW in v2.13.0!)n8n_trigger_webhook_workflow
- Trigger workflows via webhook URLn8n_get_execution
- Get execution details by IDn8n_list_executions
- List executions with status filteringn8n_delete_execution
- Delete execution recordsn8n_health_check
- Check n8n API connectivity and featuresn8n_diagnostic
- Troubleshoot management tools visibility and configuration issuesn8n_list_available_tools
- List all available management tools// Get essentials for quick configuration
get_node_essentials("nodes-base.httpRequest")
// Find nodes for a specific task
search_nodes({ query: "send email gmail" })
// Get pre-configured settings
get_node_for_task("send_email")
// Validate before deployment
validate_node_operation({
nodeType: "nodes-base.httpRequest",
config: { method: "POST", url: "..." },
profile: "runtime" // or "minimal", "ai-friendly", "strict"
})
// Quick required field check
validate_node_minimal({
nodeType: "nodes-base.slack",
config: { resource: "message", operation: "send" }
})
For contributors and advanced users:
Prerequisites:
# 1. Clone the repository
git clone https://github.com/czlonkowski/n8n-mcp.git
cd n8n-mcp
# 2. Clone n8n docs (optional but recommended)
git clone https://github.com/n8n-io/n8n-docs.git ../n8n-docs
# 3. Install and build
npm install
npm run build
# 4. Initialize database
npm run rebuild
# 5. Start the server
npm start # stdio mode for Claude Desktop
npm run start:http # HTTP mode for remote access
# Build & Test
npm run build # Build TypeScript
npm run rebuild # Rebuild node database
npm run test-nodes # Test critical nodes
npm run validate # Validate node data
npm test # Run all tests
# Update Dependencies
npm run update:n8n:check # Check for n8n updates
npm run update:n8n # Update n8n packages
# Run Server
npm run dev # Development with auto-reload
npm run dev:http # HTTP dev mode
Current database coverage (n8n v1.106.3):
See CHANGELOG.md for full version history and recent changes.
Previous versions had an issue where containers would not properly clean up when Claude Desktop sessions ended. This has been fixed in v2.7.20+ with proper signal handling.
For best container lifecycle management:
{
"mcpServers": {
"n8n-mcp": {
"command": "docker",
"args": [
"run", "-i", "--rm", "--init",
"ghcr.io/czlonkowski/n8n-mcp:latest"
]
}
}
}
docker run --rm ghcr.io/czlonkowski/n8n-mcp:latest --version
The project includes a comprehensive test suite with 1,356 tests ensuring code quality and reliability:
# Run all tests
npm test
# Run tests with coverage report
npm run test:coverage
# Run tests in watch mode
npm run test:watch
# Run specific test suites
npm run test:unit # 933 unit tests
npm run test:integration # 249 integration tests
npm run test:bench # Performance benchmarks
./coverage
directoryUnit Tests: Isolated component testing with mocks
Integration Tests: Full system behavior validation
Benchmarks: Performance testing for critical paths
For detailed testing documentation, see Testing Architecture.
MIT License - see LICENSE for details.
Attribution appreciated! If you use n8n-MCP, consider:
Contributions are welcome! Please:
npm test
)This project uses automated releases triggered by version changes:
# Guided release preparation
npm run prepare:release
# Test release automation
npm run test:release-automation
The system automatically handles:
See Automated Release Guide for complete details.
All workflow templates in this project are fetched from n8n's public template gallery at n8n.io/workflows. Each template includes:
The AI agent instructions in this project contain mandatory attribution requirements. When using any template, the AI will automatically:
Template creators retain all rights to their workflows. This project indexes templates to improve discoverability through AI assistants. If you're a template creator and have concerns about your template being indexed, please open an issue.
Special thanks to the prolific template contributors whose work helps thousands of users automate their workflows, including: David Ashby (@cfomodz), Yaron Been (@yaron-nofluff), Jimleuk (@jimleuk), Davide (@n3witalia), David Olusola (@dae221), Ranjan Dailata (@ranjancse), Airtop (@cesar-at-airtop), Joseph LePage (@joe), Don Jayamaha Jr (@don-the-gem-dealer), Angel Menendez (@djangelic), and the entire n8n community of creators!
Please log in to share your review and rating for this MCP.
{ "mcpServers": { "n8n-mcp": { "command": "npx", "args": [ "n8n-mcp" ], "env": {} } } }
Discover more MCP servers with similar functionality and use cases
by Skyvern-AI
Skyvern automates browser-based workflows using LLMs and computer vision, offering a robust solution for repetitive online tasks.
by PipedreamHQ
Connect APIs quickly, run event‑driven automations, and execute custom code in Node.js, Python, Go, or Bash on a hosted platform.
by executeautomation
mcp-playwright is a Model Context Protocol (MCP) server that enables large language models (LLMs) to perform browser automation and web scraping tasks using Playwright.
by browserbase
Provides cloud browser automation capabilities for LLMs, enabling web navigation, interaction, screenshot capture, and data extraction through Browserbase and Stagehand.
by haris-musa
excel-mcp-server is a Python-based Model Context Protocol (MCP) server that enables AI agents to programmatically create, read, and modify Excel files without requiring Microsoft Excel to be installed.
by mobile-next
Mobile-mcp is a Model Context Protocol (MCP) server designed for scalable mobile automation, app scraping, and development across iOS and Android devices, including physical devices, simulators, and emulators.
by anaisbetts
mcp-installer is an MCP server designed to automate the installation of other MCP servers, simplifying the process for users.
by leonardsellem
An MCP server that enables AI assistants to interact with n8n workflows through natural language.
by hyperbrowserai
Enables browser automation powered by large language models, offering natural‑language commands, AI‑driven data extraction, and seamless fallback to regular Playwright functionality.