mcp-n8n-voice-orchestrator
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dispatch_idempotent_n8n_workflowC | Dispatches a deterministic, lock-verified webhook payload to a self-hosted n8n workflow from Vapi, Twilio, or WhatsApp Cloud API. |
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 a single tool, there is no possibility of confusing it with another; its purpose as a workflow dispatcher is unmistakable.
The lone name follows a clear snake_case verb_noun pattern (dispatch_idempotent_n8n_workflow), though with one tool there is no pattern to actually be consistent across.
A single tool is too thin for an orchestration server; dispatch is the only operation, leaving no room for status, verification, or management operations.
The surface offers fire-and-forget dispatch with no way to check workflow status, list available workflows, or handle failures, which are significant gaps for an orchestration role.