AutomationBridge-n8n: MCP Gateway for n8n

This component acts as an MCP server, exposing functionality residing within connected n8n installations (workflows, execution history, stored credentials, etc.) to Large Language Models (LLMs) using a defined, standardized communication interface.

Deployment Instructions

Acquiring n8n Access Token

Access your active n8n dashboard.
Navigate to the user profile menu (usually lower-left corner).
Open 'Preferences' or 'Settings'.
Locate the 'API Access' section.
Generate a new API Key and securely store the generated string, as it will not be displayed again.

Server Installation

Method A: Using npm Package (Preferred)

Execute the following command globally:

bash npm install -g @illuminaresolutions/n8n-mcp-server

Method B: Building from Source Code

Clone the repository source: bash git clone https://github.com/illuminaresolutions/n8n-mcp-server.git cd n8n-mcp-server
Install requisite packages and compile the project: bash npm install npm run build
Initiate background service execution: bash nohup npm start > n8n-mcp.log 2>&1 &

To terminate the running process: bash pkill -f "node build/index.js"

Note: Installation via npm makes the utility directly available via the system's PATH.

Configuration for Client Applications

Integration with Claude Desktop Environment

Modify the local configuration file:

~/Library/Application Support/Claude/claude_desktop_config.json

Incorporate the n8n bridge definition within the mcpServers object:

{ "mcpServers": { "n8n": { "command": "n8n-mcp-server", "env": { "N8N_HOST": "https://your-n8n-instance.com", "N8N_API_KEY": "your-api-key-here" } } } }

Integration with Cline (VS Code Extension)

Ensure the server binary is installed (refer to Installation section).
Launch VS Code.
Activate the Cline interface panel (sidebar icon).
Navigate to the 'MCP Services Registry' icon at the top.
Select 'Configure MCP Services' at the bottom of the panel.
Append the following structure to the opened configuration file:

{ "mcpServers": { "n8n": { "command": "n8n-mcp-server", "env": { "N8N_HOST": "https://your-n8n-instance.com", "N8N_API_KEY": "your-api-key-here" } } } }

Persist changes and confirm the MCP communication toggle is active (green indicator).
You can now invoke n8n operations through Cline.

Sage Environment

Future support is planned via: - The Smithery.ai application catalog. - Direct import utility from Claude Desktop settings.

For immediate use, please leverage Cline or Claude Desktop.

Operational Verification

Post-configuration steps:

Restart your consuming LLM interface.
Issue a query such as: "Enumerate my defined n8n workflows."
Successful retrieval confirms connectivity.

Troubleshooting tips if errors occur: - Confirm the n8n service endpoint is reachable. - Validate the API key possesses necessary read/write scope. - Ensure N8N_HOST omits any trailing forward slash (/).

Capabilities Overview

Standardized Functions

Discovery and manipulation of automated workflows.
Inspection of specific workflow blueprints.
Triggering workflow executions.
Management of stored access credentials.
Tag handling and tracking execution records.
Generation of security compliance reports.
Workflow tagging operations.

Enterprise Tier Functions

These advanced features necessitate an active n8n Enterprise subscription: - Project organization and isolation. - Runtime variable configuration. - Granular user access controls.

Diagnostic Guidance

Recurring Failures

Error: "Client not initialized"
Re-check environment variables N8N_HOST and N8N_API_KEY syntax.
Confirm network path to the n8n server is unobstructed.
Validate the token's authorization level.
Error: "License required"
Indicates an attempt to access proprietary (Enterprise) functionality.
Upgrade your n8n license or restrict commands to core features.
Connectivity Disruptions
Ensure the target n8n instance is active.
Verify protocol consistency (HTTP vs HTTPS).
Double-check that N8N_HOST does not end with a separator character.

Security Considerations

Token Handling
Apply the principle of least privilege to token scope.
Establish a schedule for key renewal.
Strictly avoid embedding secrets within source code repositories.
Service Exposure
Mandatory use of TLS/SSL (HTTPS) in production settings.
Enable native n8n access control mechanisms.
Maintain the n8n instance on current patch levels.

Support Channels

Problem Reporting: GitHub Issues
Reference Material: n8n Official Documentation

Licensing

Covered under the MIT License

CONTEXTUAL NOTE: The Model Context Protocol (MCP) leverages standardized interfaces, echoing the underlying asynchronous request mechanisms seen in early web technologies like XMLHttpRequest (XHR), which revolutionized browser-server interaction by decoupling page loads from data transfers, allowing dynamic updates and richer application experiences.