Cursor n8n Builder
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_MODE | No | MCP transport mode (stdio) | |
| LOG_LEVEL | No | Log level (debug, info, warn, error) | |
| N8N_API_KEY | Yes | n8n API key | |
| N8N_API_URL | Yes | Your n8n instance URL |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| n8n_tools_helpA | Get documentation and usage guide for n8n MCP tools. Call this first to understand available capabilities. |
| n8n_get_node_infoC | Get information about common n8n node types and their configurations. |
| n8n_list_workflowsA | List all workflows in the n8n instance. Returns workflow IDs, names, and active status. |
| n8n_get_workflowB | Get detailed information about a specific workflow including all nodes and connections. |
| n8n_create_workflowC | Create a new workflow with nodes and connections. The workflow will be created in inactive state. |
| n8n_update_workflowC | Update an existing workflow. You can update name, nodes, connections, or settings. |
| n8n_delete_workflowA | Permanently delete a workflow. This action cannot be undone. |
| n8n_activate_workflowB | Activate a workflow so it can be triggered. The workflow must have a valid trigger node. |
| n8n_deactivate_workflowC | Deactivate a workflow to stop it from being triggered. |
| n8n_list_executionsC | List workflow executions. Can filter by workflow ID and status. |
| n8n_get_executionC | Get detailed information about a specific execution including input/output data. |
| n8n_delete_executionC | Delete an execution record. |
| n8n_trigger_webhookA | Trigger a workflow via its webhook URL. The workflow must be active and have a Webhook trigger node. |
| n8n_health_checkA | Check the connection to the n8n instance and verify API credentials. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Every tool has a clearly distinct purpose targeting specific resources and actions in the n8n domain. There is no overlap between workflow management tools (create, get, update, delete, activate, deactivate), execution tools (list, get, delete), and utility tools (health check, node info, tools help, trigger webhook). The descriptions reinforce these distinctions, making misselection unlikely.
All tool names follow a perfect and consistent 'n8n_verb_noun' pattern throughout the set. The verb-noun structure is uniform (e.g., n8n_create_workflow, n8n_get_execution, n8n_health_check), with no deviations in style or convention. This predictability makes the tool set easy to navigate and understand.
With 14 tools, the count is well-scoped for managing n8n workflows and executions. Each tool earns its place by covering essential operations like CRUD for workflows, execution lifecycle management, and necessary utilities. This provides comprehensive coverage without being overwhelming or sparse for the domain.
The tool surface offers complete CRUD and lifecycle coverage for workflows (create, get, update, delete, activate, deactivate, list) and executions (list, get, delete), along with utilities for health checks, node information, documentation, and triggering. There are no obvious gaps, and agents can perform all core n8n management tasks without dead ends.