Two paths sit side by side: the API path for managing workflows as objects, and the webhook path for firing one by name with a payload — which is the shorter road when the workflow was designed to be triggered.
A server that talks to an n8n instance's API. Workflows and their executions become tools and resources, so an assistant can inspect the automation you already run and trigger it.
- Workflow management: `workflow_list`, `workflow_get`, `workflow_create`, `workflow_update`, `workflow_delete`, `workflow_activate` and `workflow_deactivate`
- Execution management: `execution_run` through the API, `execution_get`, `execution_list`, `execution_stop`
- `run_webhook` triggers a webhook workflow by name — pass `hello-world` and it calls your n8n URL's `/webhook/hello-world`, with Basic Authentication handled from the configured credentials
- Resources for reading rather than acting: `n8n://workflows/list`, `n8n://workflow/{id}`, `n8n://executions/{workflowId}` and `n8n://execution/{id}`
Node.js 20 or later and an n8n instance with API access enabled. Install with `npm install -g @leonardsellem/n8n-mcp-server`, or run the published Docker image. Configure `N8N_API_URL` — the full URL including `/api/v1` — and `N8N_API_KEY`, which you create under Settings > API > API Keys in n8n. Webhook execution additionally needs `N8N_WEBHOOK_USERNAME` and `N8N_WEBHOOK_PASSWORD`, matching the Basic Authentication set on the webhook node.
One command plus a key — npm install -g @leonardsellem/n8n-mcp-server, then supply credentials