Skip to main content

Quick Start with npx

The fastest way to get started with n8n-MCP is using npx - no installation required!
1

Run n8n-MCP

Open your terminal and run:
npx n8n-mcp
This will:
  • Download the package (~70MB)
  • Extract the pre-built database with all n8n node information
  • Initialize the SQLite adapter
First run takes 10-15 seconds. Subsequent runs start in <1 second.
2

Configure Claude Desktop

Add n8n-MCP to your Claude Desktop configuration file:
Open ~/Library/Application Support/Claude/claude_desktop_config.json
Add this configuration:
{
  "mcpServers": {
    "n8n-mcp": {
      "command": "npx",
      "args": ["n8n-mcp"],
      "env": {
        "MCP_MODE": "stdio",
        "LOG_LEVEL": "error",
        "DISABLE_CONSOLE_OUTPUT": "true"
      }
    }
  }
}
The MCP_MODE: "stdio" environment variable is required for Claude Desktop. Without it, you’ll see JSON parsing errors.
3

Restart Claude Desktop

Completely quit and restart Claude Desktop for the changes to take effect.
On macOS, use Cmd+Q to fully quit. On Windows, right-click the system tray icon and select “Quit”.
4

Verify Installation

In a new Claude Desktop conversation, try one of these prompts:
Search for n8n nodes related to Slack
Claude should now have access to all n8n-MCP tools and respond with detailed n8n information.

Optional: Add n8n API Integration

To enable workflow management features (create, update, test workflows), add your n8n API credentials:
1

Get n8n API Key

In your n8n instance:
  1. Go to SettingsAPI
  2. Click Create API Key
  3. Copy the generated key
2

Update Configuration

Add the API credentials to your Claude Desktop config:
{
  "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-here"
      }
    }
  }
}
Running n8n locally? Use http://host.docker.internal:5678 for Docker deployments or http://localhost:5678 for local installations.
3

Configure Local Webhook Security (if needed)

If using a local n8n instance, add this environment variable to allow webhooks:
"WEBHOOK_SECURITY_MODE": "moderate"
This is safe for local development while still blocking private networks and cloud metadata.
4

Restart and Test

Restart Claude Desktop and try creating a workflow:
Create a simple webhook workflow that responds with "Hello World"

What You Can Do Now

Search 1,084 Nodes

Find n8n nodes by functionality with full-text search

Get Node Details

View comprehensive node documentation and examples

Browse 2,709 Templates

Discover pre-built workflows from the n8n community

Validate Configurations

Check node configs before deployment

Next Steps

1

Learn Core Concepts

Understand how n8n-MCP works: MCP Tools, Node Search, Validation
2

Explore Examples

See real workflow examples: Basic Workflow, Webhook Integration, AI Agent
3

Build Workflows

Follow our comprehensive guide: Building Workflows
4

Deploy to Production

Choose your deployment method: Docker, Railway, Local

Troubleshooting

  1. Verify the configuration file is valid JSON
  2. Check the file location matches your operating system
  3. Completely quit and restart Claude Desktop (not just close the window)
  4. Check Claude Desktop logs for errors
This means MCP_MODE: "stdio" is missing or incorrect. Add it to the env section of your configuration.
The first npx n8n-mcp run downloads the package and initializes the database. This is normal and only happens once. Subsequent runs are instant.
If you configured n8n API credentials, verify:
  • The N8N_API_URL is correct and accessible
  • The N8N_API_KEY is valid
  • Your n8n instance is running

Alternative Installation Methods

Docker

Isolated container deployment with zero dependencies

Railway

One-click cloud deployment with free tier

Local Development

Clone and run for development and contributions

IDE Integration

Connect with VS Code, Cursor, Windsurf, and more

Build docs developers (and LLMs) love