← Back to Skills Marketplace
93
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install n8n-mcp
Description
Operate n8n workflow automation platform via MCP (Model Context Protocol). Use when: (1) Creating, updating, or managing n8n workflows, (2) Executing or test...
README (SKILL.md)
n8n MCP Integration
Connect to n8n's official MCP server to programmatically build, execute, and manage workflows.
Version Support
- n8n version: 2.16.1+
- MCP protocol: 2024-11-05
- Server name: n8n MCP Server v1.1.0
Configuration
MCP Server Setup
In n8n UI:
- Go to Settings → n8n API
- Create an API key for REST API access
- Create an MCP token for MCP server access
Connection Config
{
"mcpServers": {
"n8n-mcp": {
"type": "http",
"url": "http://localhost:5678/mcp-server/http",
"headers": {
"Authorization": "Bearer \x3CMCP_TOKEN>"
}
}
}
}
Environment Variables
export N8N_MCP_URL="http://localhost:5678/mcp-server/http"
export N8N_MCP_TOKEN="\x3Cyour-mcp-token>"
Available Tools
Workflow Management
| Tool | Description |
|---|---|
search_workflows |
Search workflows with filters |
get_workflow_details |
Get workflow details + trigger info |
publish_workflow |
Activate workflow for production |
unpublish_workflow |
Deactivate workflow |
archive_workflow |
Archive a workflow |
update_workflow |
Update workflow from code |
Workflow Execution
| Tool | Description |
|---|---|
execute_workflow |
Execute workflow by ID |
get_execution |
Get execution details |
test_workflow |
Test workflow with pin data |
prepare_test_pin_data |
Generate test data for workflow |
Workflow Creation (SDK)
| Tool | Description |
|---|---|
get_sdk_reference |
Get SDK docs and patterns |
search_nodes |
Search n8n nodes by service/type |
get_node_types |
Get TypeScript type definitions |
get_suggested_nodes |
Get curated node recommendations |
validate_workflow |
Validate workflow code |
create_workflow_from_code |
Create workflow from SDK code |
Data Tables
| Tool | Description |
|---|---|
search_data_tables |
Search data tables |
create_data_table |
Create new data table |
rename_data_table |
Rename data table |
add_data_table_column |
Add column to table |
delete_data_table_column |
Delete column |
rename_data_table_column |
Rename column |
add_data_table_rows |
Insert rows into table |
Projects & Folders
| Tool | Description |
|---|---|
search_projects |
Search projects |
search_folders |
Search folders |
Usage Patterns
1. Creating a Workflow
# Step 1: Get SDK reference
curl -X POST -H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_sdk_reference","arguments":{"section":"all"}}}' \
"$N8N_MCP_URL"
# Step 2: Search nodes
curl -X POST ... -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"search_nodes","arguments":{"queries":["schedule trigger","slack","set"]}}}'
# Step 3: Get node types
curl -X POST ... -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"get_node_types","arguments":{"nodeIds":["n8n-nodes-base.scheduleTrigger","n8n-nodes-base.slack"]}}}'
# Step 4: Validate code
curl -X POST ... -d '{"jsonrpc":"2.0","id":4,"method":"tools/call","params":{"name":"validate_workflow","arguments":{"code":"..."}}}'
# Step 5: Create workflow
curl -X POST ... -d '{"jsonrpc":"2.0","id":5,"method":"tools/call","params":{"name":"create_workflow_from_code","arguments":{"code":"...","name":"My Workflow","description":"..."}}}'
2. Executing a Workflow
# Execute workflow
curl -X POST ... -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"execute_workflow","arguments":{"workflowId":"xxx"}}}'
# Get execution result
curl -X POST ... -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_execution","arguments":{"workflowId":"xxx","executionId":"yyy","includeData":true}}}'
3. Testing with Pin Data
# Prepare test data
curl -X POST ... -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"prepare_test_pin_data","arguments":{"workflowId":"xxx"}}}'
# Test workflow
curl -X POST ... -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"test_workflow","arguments":{"workflowId":"xxx","pinData":{...}}}}'
SDK Workflow Example
import { workflow, trigger, node } from 'n8n-workflow-sdk';
export default workflow({
name: 'Daily Slack Notification',
description: 'Send daily summary to Slack',
nodes: [
trigger.schedule({
name: 'Schedule',
rule: { interval: [{ field: 'hours', hoursInterval: 24 }] }
}),
node.set({
name: 'Prepare Message',
values: { text: 'Daily report ready!' }
}),
node.slack({
name: 'Send to Slack',
resource: 'message',
operation: 'send',
channel: '#general',
text: '={{ $node["Prepare Message"].json.text }}'
})
],
connections: [
{ from: 'Schedule', to: 'Prepare Message' },
{ from: 'Prepare Message', to: 'Send to Slack' }
]
});
MCP Protocol Notes
- Transport: HTTP with SSE (Server-Sent Events)
- Content-Type:
application/json - Accept:
application/json, text/event-stream(required) - Auth: Bearer token in Authorization header
Common Errors
| Error | Solution |
|---|---|
| "Not Acceptable" | Add Accept: application/json, text/event-stream header |
| "Unauthorized" | Check MCP token is valid |
| "Not found" | Verify MCP server URL is correct |
References
- SDK Reference: See references/sdk-patterns.md for detailed SDK patterns
- Node Types: See references/common-nodes.md for frequently used nodes
Usage Guidance
This skill is coherent for managing n8n via MCP, but treat the MCP token like any privileged credential: only point N8N_MCP_URL to trusted n8n instances, create a scoped/rotatable MCP token, avoid using tokens reused elsewhere, and monitor n8n audit logs. Fix the example variable mismatch ($TOKEN vs N8N_MCP_TOKEN) before running examples. If you will allow the agent to call the MCP endpoint autonomously, ensure network access and token scope are tightly controlled (don't expose a production n8n to untrusted networks).
Capability Analysis
Type: OpenClaw Skill
Name: n8n-mcp
Version: 1.0.1
The n8n-mcp skill bundle provides a legitimate integration for the n8n workflow automation platform via the Model Context Protocol (MCP). The documentation in SKILL.md, references/common-nodes.md, and references/sdk-patterns.md correctly describes tools for workflow management, execution, and creation using the n8n SDK. No evidence of malicious intent, data exfiltration, or unauthorized execution was found; the high-privilege capabilities (e.g., executing workflows) are strictly aligned with the stated purpose of the integration.
Capability Tags
Capability Assessment
Purpose & Capability
Name/description (operate n8n via MCP) match the declared env vars (N8N_MCP_URL, N8N_MCP_TOKEN) and the SKILL.md examples (HTTP calls to the MCP server). No unrelated services, binaries, or credentials are requested.
Instruction Scope
SKILL.md instructs the agent to call the MCP HTTP endpoints (curl/json-rpc/SSE) and to use a Bearer token. It does not direct the agent to read arbitrary local files, other environment variables, or contact unexpected external endpoints beyond the configured N8N_MCP_URL. Minor nit: one curl example uses $TOKEN instead of the declared N8N_MCP_TOKEN environment variable (typo), which should be corrected.
Install Mechanism
No install spec or code files that would write or execute arbitrary code on disk; the skill is instruction-only which minimizes installation risk.
Credentials
Only N8N_MCP_URL and N8N_MCP_TOKEN are required — these are proportionate and expected for an MCP HTTP integration. No unrelated credentials, config paths, or broad secrets are requested.
Persistence & Privilege
always is false and there are no instructions to modify other skills or system-wide configs. The skill does not request permanent platform-level privileges.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install n8n-mcp - After installation, invoke the skill by name or use
/n8n-mcp - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
- Added a metadata block specifying required environment variables and service dependencies for OpenClaw compatibility.
- No changes to functionality or usage instructions.
v1.0.0
Initial release: Integrate n8n workflow automation with Model Context Protocol (MCP).
- Provides tools to create, update, execute, and manage n8n workflows via MCP.
- Supports searching and managing data tables, projects, and folders.
- Enables workflow construction and validation through SDK and programmatic API access.
- Includes setup instructions for connecting to n8n’s MCP server and API.
- Compatible with n8n version 2.16.1+ and MCP protocol 2024-11-05.
Metadata
Frequently Asked Questions
What is N8n Mcp?
Operate n8n workflow automation platform via MCP (Model Context Protocol). Use when: (1) Creating, updating, or managing n8n workflows, (2) Executing or test... It is an AI Agent Skill for Claude Code / OpenClaw, with 93 downloads so far.
How do I install N8n Mcp?
Run "/install n8n-mcp" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is N8n Mcp free?
Yes, N8n Mcp is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does N8n Mcp support?
N8n Mcp is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created N8n Mcp?
It is built and maintained by itian (@itian932); the current version is v1.0.1.
More Skills