Single MCP client structure

Derived from n8n workflow JSON. One MCP Client (SSE) connection; all nodes use the same credential.

One MCP client. Every node uses the same MCP Client (SSE) account. SCMX Process Client (switch) routes by chat intent to one of the tools below. No separate branches—only one client with multiple tools.
Process / modulen8n nodeMCP tool
TMS
OrderMCP Client Ordercreate_orders_from_excel
PickupMCP Client Pickupcreate_pickup_from_excel
LoadMCP Client Loadcreate_load_from_excel
DispatchMCP Client Dispatchcreate_dispatch_from_excel
PODMCP Client PODcreate_pod_from_excel
SCM
BookingBookingcreate_booking_from_excel
SISIcreate_si_from_excel
CBSMCBSMcreate_cbsm_from_excel
ASNASNcreate_asn_from_excel
ConsolidationConsolidationcreate_consolidation_from_excel
DepartureDeparturecreate_departure_from_excel
CLPCLPcreate_clp_from_excel
ArrivalArrivalcreate_arrival_from_excel
UnloadingUnloadingcreate_unloading_from_excel
VGMVGMcreate_vgm_from_excel
Arrival NoticeArrival Noticecreate_arrival_notice_from_excel
InvoiceInvoicecreate_invoice_from_excel
Vendor InvoiceVendor Invoicecreate_vendor_invoice_from_excel
Invoice PaymentInvoice Paymentcreate_invoice_payment_from_excel
Vendor Invoice PaymentVendor Invoice Paymentcreate_vendor_invoice_payment_from_excel
Cargo ReleaseCargo Releasecreate_cargo_release_from_excel
Delivery OrderDelivery Ordercreate_delivery_order_from_excel
POPurchase Ordercreate_po_from_excel

Workflow diagram (top-down)

Schematic from n8n workflow JSON. Flow: Triggers → File path → Agent / Switch → TMS MCP → SCM MCP. No branches.

1. TRIGGERS
When chat message received If
2. FILE PATH
File Process SCMX Process Client
3. ALL CUBE AGENT (chat path)
SCM AI AGENT + OpenAI Chat Model + Simple Memory1 + MCP Client1
4. TMS MCP CLIENT (5 nodes only, no DB)
MCP Client Order MCP Client Pickup MCP Client Load MCP Client Dispatch MCP Client POD
5. DISPATCHER
SCMX Process Client
6. SCM MCP CLIENT (single sequence from n8n)
Booking SI CBSM ASN Consolidation Departure CLP Arrival Unloading VGM Arrival Notice Cargo Release Delivery Order Text Formate

Workflow diagram (left → right)

Same workflow as top-down, laid out left to right like the n8n canvas. From n8n JSON only. No branches.

TRIGGERS
When chat message received If
FILE PATH
File Process
ALL CUBE AGENT
SCM AI AGENT OpenAI Chat Model Simple Memory1 MCP Client1
DISPATCHER
SCMX Process Client
TMS MCP CLIENT
Order Pickup Load Dispatch POD
SCM MCP CLIENT
Booking SI CBSM ASN Consolidation Departure CLP Arrival Unloading VGM Arrival Notice Cargo Release Delivery Order
OUTPUT
Text Formate

TMS MCP Client

From n8n workflow JSON. Five execute-tool nodes only. MCP DB is not a function in this workflow—excluded.

#n8n nodeMCP tool
1MCP Client Ordercreate_orders_from_excel
2MCP Client Pickupcreate_pickup_from_excel
3MCP Client Loadcreate_load_from_excel
4MCP Client Dispatchcreate_dispatch_from_excel
5MCP Client PODcreate_pod_from_excel

Supply Chain Ops – SCM MCP Client

From n8n workflow JSON. Single list of nodes in switch order. CBSM (not CRGM). No “downstream from main” column.

#n8n nodeMCP tool
1Bookingcreate_booking_from_excel
2SIcreate_si_from_excel
3CBSMcreate_cbsm_from_excel
4ASNcreate_asn_from_excel
5Consolidationcreate_consolidation_from_excel
6Departurecreate_departure_from_excel
7CLPcreate_clp_from_excel
8Arrivalcreate_arrival_from_excel
9Unloadingcreate_unloading_from_excel
10VGMcreate_vgm_from_excel
11Arrival Noticecreate_arrival_notice_from_excel
12Invoicecreate_invoice_from_excel
13Vendor Invoicecreate_vendor_invoice_from_excel
14Invoice Paymentcreate_invoice_payment_from_excel
15Vendor Invoice Paymentcreate_vendor_invoice_payment_from_excel
16Cargo Releasecreate_cargo_release_from_excel
17Delivery Ordercreate_delivery_order_from_excel
18POcreate_po_from_excel