MCP n8n API Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROJECT_ID | No | Optional project ID for cloud instances | |
| N8N_API_KEY | Yes | Your n8n API key | |
| N8N_HOST_URL | Yes | Your n8n instance URL (e.g., https://your-n8n-instance.com) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workflowsA | Get all n8n workflows |
| list_workflow_webhooksB | Get all webhooks in a workflow |
| call_webhook_getB | Call a GET webhook |
| call_webhook_postC | Call a POST webhook |
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 4 tools
Each tool has a clearly distinct purpose: two for calling webhooks with specific HTTP methods, and two for listing workflows and their webhooks. No ambiguity.
All tool names follow the verb_noun pattern in snake_case, with modifiers for method variation. The naming is predictable and consistent.
With 4 tools, the count is well-scoped for a focused API server that covers both webhook invocation and workflow/webhook listing.
The tool set covers core operations for webhooks and workflow listing, but lacks create/update/delete workflows or webhook management, which limits full API coverage.