Provides tools to invoke self-hosted n8n webhook workflows, exposing them as validated MCP tools for deterministic automation and voice/messaging orchestration.
Integrates with Twilio for voice and messaging pipelines, supporting missed-call recovery, outbound dispatches, and multi-channel session handoff.
Integrates with WhatsApp Cloud API for messaging workflows, including follow-up triggers and multi-channel session handoff.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-n8n-voice-orchestrator trigger the missed-call recovery workflow for +14155551234 and send a WhatsApp follow-up"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A lightweight, deterministic Model Context Protocol (MCP) bridge and reference architecture designed to connect Claude (Sonnet/Haiku/Opus) and Claude Code directly to self-hosted n8n instances, Vapi.ai voice pipelines, Twilio, and WhatsApp Cloud API.
While n8n provides general workflow nodes and Anthropic's MCP standardizes tool-calling, production voice and messaging pipelines suffer from three critical bottlenecks:
Race Conditions & Webhook Concurrency: Out-of-order webhook arrivals between Vapi end-of-call reports and WhatsApp follow-up triggers.
Sub-Second Latency Requirements: Voice agents require deterministic state lookup (<300ms) before triggering LLM tool calls.
Lack of Standardized MCP Schemas for Self-Hosted Automation: Developers repeatedly rebuild boilerplate JSON-RPC wrappers to expose n8n webhook endpoints as verified Claude MCP tools.
Related MCP server: n8n MCP Server
/mcp-server: TypeScript MCP server exposing n8n webhook workflows as strict, Zod-validated tools for Claude Desktop and Claude API.
/workflows: Production-grade n8n JSON blueprints for missed-call recovery, deterministic lead qualification, and multi-channel session handoff.
/state-machine: Supabase / PostgreSQL idempotency tables and row-level locking schemas to prevent duplicate outbound dispatches.
git clone [https://github.com/Code-With-Vishal/mcp-n8n-voice-orchestrator.git](https://github.com/Code-With-Vishal/mcp-n8n-voice-orchestrator.git)
cd mcp-n8n-voice-orchestrator
npm install
cp .env.example .env
npm run build
Dispatches a deterministic, lock-verified webhook payload to a self-hosted n8n workflow from Vapi, Twilio, or WhatsApp Cloud API.
Inputs: channel (required), payload (required), workflowId (required), idempotencyKey (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
26 pay-per-call AI agent tools for marketing, sales, content, research, verification, and integration testing. Agents pay per call via x402 micropayments (USDC on Base), raw JSON in and out. Includes delivery-acceptance receipts (ACCEPT/REJECT/REVIEW), a webhook capture/replay/conformance lab, and n8n workflow validation with bounded JSON-Patch repair.
Open-source Zapier/n8n alternative as an MCP server: agents build, run and debug your workflows.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
One MCP endpoint for Claude, GPT & Gemini: 100+ tools + no-code connectors + agent workers.