n8n Workflow Builder MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| create_workflowC | Create and configure n8n workflows programmatically |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'create_workflow' has a clear, distinct purpose that cannot be confused with any other tool in this set.
The naming pattern is perfectly consistent as there is only one tool. It follows a clear verb_noun convention ('create_workflow'), which would be easy to maintain if more tools were added.
A single tool is insufficient for a 'Workflow Builder' server, which implies capabilities like listing, updating, executing, or deleting workflows. This feels thin and under-scoped for the apparent domain of workflow management.
The tool surface is severely incomplete for workflow building. It only offers creation, with no ability to read, update, delete, execute, or manage existing workflows. This creates significant dead ends for agents trying to perform basic lifecycle operations.